Tag Info

New answers tagged

0

It is unusual, but then so is the composition of your team. You didn't say how much detail you are expected to include in your test cases. It may be enough to write each test case as a single, declarative sentence, and then leave it up to your QA team to execute. That way, you give your QA team a sense for what to test but you don't spend too much of ...


2

As Agile teams need to be cross-functional, its handy if the team members itself are also cross-functional in their Agile skills including testing. One thing you want to prevent is having a mini-waterfall within a sprint. This leads to all the testing to be pushed into the end of the sprint, which could in turn bring your sprint commitments in danger. ...


2

I don't have time to do all the documentation, test cases, strategy, test plan, etc. I almost always recommend producing the minimum necessary documentation. Call it lean documentation, minimum viable documentation, whatever. You want just enough that helps plan and guide the testing you need to do. Anything more starts to lose value very quickly. ...



Top 50 recent answers are included