-
Notifications
You must be signed in to change notification settings - Fork 303
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
End-to-end test coverage #3606
Comments
I'll add the rest of the dev team as assignees once #3611 is done. |
@kschiffer I assume that |
Yes indeed. Linking can be removed, though |
What is the status here? What can we improve on the short term still? |
@asmulko made a lot of progress with this recently and I think the coverage is pretty good already. The most important thing short-term is traffic simulation, which will enable us putting a whole range of critical end-to-end tests in place. This is also tracked in #3611. Then we need to start looking into performance optimizations #3480. |
OK. Should we track end-to-end testing in this issue or in #3611, or is there a reason to keep both? |
I'd prefer keeping and maintaining this overview here as well. We can update this issue with a lot more test cases and onboard more of the team to write end-to-end tests after #3611 is done. |
I think we an close this now. The rest of the missing coverage is either tracked by individual issues or not planned currently. |
Summary
This umbrella issue keeps track of our end-to-end test coverage.
/oauth/code
)storybook
Add functional tests tostorybook
#3478Also note the complementary umbrella issue for enterprise features:
https://github.com/TheThingsIndustries/lorawan-stack/issues/2575
Everyone please keep this up to date and add test-cases that you think are important, or split up cases into more detailed sub-cases.
For everyone that wants to dive into writing end-to-end tests, please see the guide: https://github.com/TheThingsNetwork/lorawan-stack/blob/v3.10/DEVELOPMENT.md#end-to-end-tests
The text was updated successfully, but these errors were encountered: