Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
If you have a very long form process that is not to be changed (business logic wide), you can try to set up steps for it. Set up the tests to load a desired state for each test and clean up at the end. This way you test a specific part only, rather than go through everything. Whether this is a good practice or not, I do not know.
Related Rants
Two unit tests, no integration tests.
Oops!
how do I test long scenarios? I have an app with 10 screens to complete. I have a dropdown on the first screen which creates a table row element on the last screen. should I do selenium or unit test or both? selenium will have to click through the whole app and call every API just for 1 assertion. unit test will only check the dropdown has the right options which are subject to change and not really worth testing. I run into this problem every time I want to write a test. i always miss something in my manual testing and introduce defects. what should I do?
question
testing