Skip to content

adding unit tests #7581

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
May 21, 2024
Merged

adding unit tests #7581

merged 9 commits into from
May 21, 2024

Conversation

katieklein
Copy link
Contributor

Description of changes:

Related GitHub issue #, if available:

Instructions

If this PR should not be merged upon approval for any reason, please submit as a DRAFT

Which product(s) are affected by this PR (if applicable)?

  • amplify-cli
  • amplify-ui
  • amplify-studio
  • amplify-hosting
  • amplify-libraries

Which platform(s) are affected by this PR (if applicable)?

  • JS
  • Swift
  • Android
  • Flutter
  • React Native

Please add the product(s)/platform(s) affected to the PR title

Checks

  • Does this PR conform to the styleguide?

  • Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.

  • Are any files being deleted with this PR? If so, have the needed redirects been created?

  • Are all links in MDX files using the MDX link syntax rather than HTML link syntax?

    ref: MDX: [link](https://docs.amplify.aws/)
    HTML: <a href="https://docs.amplify.aws/">link</a>

When this PR is ready to merge, please check the box below

  • Ready to merge

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@katieklein katieklein requested a review from a team as a code owner May 13, 2024 21:34
@katieklein katieklein marked this pull request as draft May 13, 2024 21:35
@katieklein katieklein changed the title Unit tests 2 adding unit tests May 20, 2024
@katieklein katieklein marked this pull request as ready for review May 20, 2024 17:30
Copy link
Contributor

@hbuchel hbuchel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, left a non-blocking comment. Also this bumps statements to over 80% now, thanks! 🎉

it('should render the FeatureList component', async () => {
render(featureListComponent);

const heading = await screen.findByRole('heading', { name: 'Deploy' });
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not blocking, but you can combine the H2 expect in this findByRole with:

await screen.findByRole('heading', { name: 'Deploy', level: 2 });


const component = (
<FeatureFlagSummary
key={`feature-flag-summary-${1}`}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Can we remove this key prop? I'm not seeing why we need it here.


const component = (
<FeatureFlagSummary
key={`feature-flag-summary-${1}`}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above, key seems unnecessary here.

@katieklein katieklein merged commit 7217eea into main May 21, 2024
10 checks passed
@katieklein katieklein deleted the unit-tests-2 branch May 21, 2024 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants