Skip to content
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

Remove Identity Tests for Default Testing #131

Merged
merged 4 commits into from
Apr 30, 2024
Merged

Conversation

jeremytwfortune
Copy link
Collaborator

Description of Changes

Testing the Identity API for every PR has become untenable. The small instance that we have allocated for this purpose just can't handle the volume of mostly-duplicate identifiers, resulting in a ton of spurious workflow errors.

This PR categorizes tests into default and e2e. There is now also an issue template for releasing a new tag and a checklist on that template to be sure that you have run the e2e tests prior to tagging.

Security

REMINDER: All file contents are public.

  • I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc. Of particular note: No temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.
  • My changes do not introduce any security risks, or any such risks have been properly mitigated.

While it would be nice to test against the Identity API for all changes, no code should be released with these changes prior to going through e2e.

Reviewers

  • I have assigned the appropriate reviewer(s).

Migrates the exceedingly slow testing for Identity into an e2e test set
so that we don't have to wait on very slow ci/cd. This should be used
before any release.
@jeremytwfortune jeremytwfortune added enhancement New feature or request python Pull requests that update Python code javascript Pull requests that update Javascript code labels Apr 30, 2024
@jeremytwfortune jeremytwfortune requested a review from kneumei April 30, 2024 15:14
@@ -4,5 +4,6 @@ export default defineConfig({
test: {
testTimeout: 300000,
hookTimeout: 300000,
Copy link
Contributor

Choose a reason for hiding this comment

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

do you need these long timeouts on unit tests?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Probably not. They could be reduced a bit.

@jeremytwfortune jeremytwfortune merged commit 72f2014 into main Apr 30, 2024
6 checks passed
@jeremytwfortune jeremytwfortune deleted the faster-tests branch April 30, 2024 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request javascript Pull requests that update Javascript code python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants