Join the DZone community and get the full member experience.Join For Free
User stories are popular because they offer a simple workflow, each story adds new tests to the story test suite. However story tests often lead to problems. Regularly adding story tests leads to a large body of tests, often with significant duplication between them. When behavior needs to change in later iterations of the project, duplication in tests can take a painful amount of time to update. Furthermore broad-stack story tests take a long time to execute, which is why having a lot of them violates the TestPyramid. As a result many people recommend using just a few UserJourneyTests together with business-facing ComponentTests.
Published at DZone with permission of Martin Fowler, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Guide To Selecting the Right GitOps Tool - Argo CD or Flux CD
A Complete Guide to AWS File Handling and How It Is Revolutionizing Cloud Storage
How To Backup and Restore a PostgreSQL Database
Harnessing the Power of Integration Testing