4 ms·
What is this for? For manual testers to run through the list and execute the tests? As a spec for automated test authoring? I'm curious why you need this. Don't
by ajeet_dhaliwal 9y ago
What is this for? For manual testers to run through the list and execute the tests? As a spec for automated test authoring? I'm curious why you need this. Don't have a solution to suggest right now but we're considering adding tools for manual testers to Tesults in the future and I'd be interested in understanding what this is useful for.
- muzani 9y agoMainly as a spec for the whole program. It saves time on designing code, when management can communicate what exactly they need done rather than just give a vague story. There's usually a lot of this back and forth going on about what the app really intends to do. It helps a lot in clarifying contracts too. For example, if there is no internet access, the contractor might just want to let it show a vague error pop up, but the client might want it to show a cached version. Making testing easier and reducing bugs is just a nice side effect.