TL;DR: Having SpecFlow steps to do the same thing in two different web application solutions needs to be refactored to avoid duplication and the potential problems that will result in.
I have specflow tests to build against a particular web application but some steps involve switching between web apps. For example, performing a basic operation like listing the properties of a user's account will require going via the login application and back to the profile application.
I am writing specflow tests for the profile application and I don't have a problem writing steps to perform the login journey, but how should I structure tests (like the login steps) which span multiple apps - the problem is that they will be duplicated into both solutions and I'd really like to avoid that.
Aucun commentaire:
Enregistrer un commentaire