-
Notifications
You must be signed in to change notification settings - Fork 310
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
Extend end-to-end test framework to integrate traffic simulation #3611
Comments
Specifically, what I wonder is whether these functionalities will suffice for our end-to-end tests:
|
@kschiffer do you still need input from others to proceed with this? |
@KrishnaIyer can you book a few days to get this going? |
I'm handling this already with https://github.com/TheThingsIndustries/lorawan-stack/issues/2742 |
This includes:
|
Summary
To extend our end-to-end tests with test-cases that comprise network data, we need to extend our framework there to be able to simulate network traffic easily.
Why do we need this?
What is already there? What do you see now?
Cypress-based end-to-end test framework, which we currently use to write test cases centered around the frontend.
What is missing? What do you want to see?
Some plugins or added cypress commands to inject network traffic into the stack. E.g. to be able to test join procedures, uplinks/downlinks, message en/decoding, mac commands, etc.
How do you propose to implement this?
Our CLI already allows simulating network traffic. We can use this to inject network traffic from within tests and subsequently check on expected behavior in the console (
via cy.exec()
). Since Cypress wraps an assertion library, we can also test CLI commands and their output directly.Can you do this yourself and submit a Pull Request?
@bafonins or me to set up the groundwork.
It would be good to know from everybody which example test cases you'd like to add and whether CLI based traffic simulation and asserting on CLI command output and/or frontend behavior are sufficient to achieve these. cc @rvolosatovs @KrishnaIyer
The text was updated successfully, but these errors were encountered: