6

Data: Use each of the following payment methods: X, Y, Z, ... Procedure: .... .... .... I don't see how any professional tester won't understand that you want to validate with each payment method. If for any reason the tester to whom you are writing this documentation gets confused, a 30-seconds conversation with you probably will solve any ...


2

I don't think there's any real benefit from being thorough when writing test cases. For two main reasons: you want other testers to use their imagination as well, which rarely happens when people follow written instructions it would take you so much time that you could spend better, e.g. exploring the system Sure, there might be some exceptions, but I ...


2

Testers in the Agile world are not the only ones doing the actual testing. They should be looked at as testing coaches for the whole team, improving testing in various ways, like proposing good testing practices, making acceptance criteria more testable, etc. Since it is difficult for you to be an effective tester because of the "this software works&...


2

My answer is going to be very opinion-based (as is your question) but, that is the approach we use. We manage our test via Excel (which completely sucks) and, if test steps are shared between tests we basically say "repeat these steps...". We use this same approach for both manual and automated test cases.


1

I think you have more than two roles. That might work if the project is small enough, but if it grows, it will scale badly, if at all. I don't think one couldn't do various jobs, but on the other hand, your capacity and time are limited, so if the workload grows, you will probably start cutting corners somewhere to simply cope with it. And that's where ...


Only top voted, non community-wiki answers of a minimum length are eligible