My application requires my users to go through a series of forms so that I can collect data and eventually action all the data from the series of forms at the end (picture an insurance application or something similar). There are requirements that exist all along the way that aren't easily unit-tested, and I'm wondering what good practices I can employ to test my API to keep my test suite DRY and to facilitate as easy a process as possible for test-writing going forward.
As an example of a requirement that I would test: A user enters some personal metadata about themselves in one stage of the application (address, dob, etc.). The user has a dashboard they can always visit to see a basic overview of their account. I need to make sure that while in the process of filling out the application form, they can move to their dashboard and see the values surfaced.
What are some testing patterns that I can employ to be DRY? I think that if I were to just isolate every feature test and re-write the entire test setup to get a user to the stage of filling out an application, things would be simple, but that's certainly going to slow down the testing process.
Aucun commentaire:
Enregistrer un commentaire