-
Notifications
You must be signed in to change notification settings - Fork 133
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
Swap names of 'integration' and 'e2e' tests #359
Labels
good first issue
Good for newcomers
scope: testing
Code review, testing, making sure the code is following the specification.
type: refactoring
Code refactoring
type: tech-debt
Slows down development in the long run
Comments
danwt
added
good first issue
Good for newcomers
scope: testing
Code review, testing, making sure the code is following the specification.
type: tech-debt
Slows down development in the long run
type: refactoring
Code refactoring
labels
Sep 20, 2022
Bikeshedding, and will confuse everyone for a while after the switch |
🤷 |
I suggest we reopen this. It's confusing people! I've just spoken with @ivan-gavran and heard it! I don't think it would take long to fix. |
Requirements:
|
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
scope: testing
Code review, testing, making sure the code is following the specification.
type: refactoring
Code refactoring
type: tech-debt
Slows down development in the long run
Problem
Currently our 'integration tests' are really more like e2e tests and our 'e2e tests' are really more like integration tests.
Closing criteria
Swap the names of these two things
The text was updated successfully, but these errors were encountered: