Tag Info

New answers tagged

2

To start with, I'd suggest browsing the answers of the questions showing as related, particularly Test Automation in Agile? and Agile Tester vs Traditional Tester...........? As far as test case writing, it doesn't really matter how you handle that, as long as someone who is moderately familiar with the application can follow your test cases. The main ...


1

Obviously automating everything is impossible... How do you think teams that practice continuous delivery are working? Being Agile means that you optimize the feedback cycle on all levels, for long running projects a rule of thumb should be to automate everything. This means the whole pipeline up-to deployment in production. I would rather say: ...


2

I had the exact same questions as you when I started the "testing" compartment in my current Agile project. It is indeed not feasible to write and maintain test cases in the tradition format. User stories are delivered every few weeks, and change rapidly afterwards. Test cases would become obsolete faster than you can write them. One approach that I found ...


1

You are on the right track. I used to do the granular test plans until relatively recently. I have gone the direction of making a Test Plan mostly consisting of User Stories. You need to remember your audience when writing anything. My Test Plans are part of the deliverable to clients so it makes the most sense that anyone can read it and use it. That means ...



Top 50 recent answers are included