Discussion: Test Strategies

[simon_tomes]

Questions answered

• What’s the goal of a test strategy and what does it enable?
• When you are about to create a test strategy for a new feature/project, do you use a checklist, template or any kind of re-usable artefacts to make sure you didn’t forget anything?
• What would a bad test strategy look like? As I find using a bad example and avoiding that, helps me do a good one.
• What would you say are the main differences between a test plan and a test strategy?
• How to motivate product teams or project teams to create a test strategy?
• What are some of the questions which you ask while thinking about a strategy and what are examples of strategies that you have chosen and why?
• You have a perfect (if there is such a thing) strategy, then the project changes, then the scope changes, then you discover things. How do you cope, how do you manage? How do you react when you realise you didn’t consider something impactful e.g. security, accessibility, performance?
• I don’t have a lot of experience in software testing and now I’m at the totally new project where software development on the stage of making different schemes. What can I do for a team as a manual tester in the paradigm of test strategy? Where should I start?
• Could you post the links to the visual test strategies mentioned? @jesper to kindly add this
• In a scale agile setting: how to establish aligned autonomy with test policy / test strategy on scrum team vs. Program / release train level?

Items shared during the discussion

http://goodbadstrategy.com/

Bloggers Club August 2021 – Implementing Change

I experienced a profound difference in how I change things after reading this article on short meetings. It wasn’t so much to do with better use of meeting time but more so with my approach to exploring ideas and seeking consensus for change. Instead of waiting for a meeting to share an idea with everyone, I experimented with lightly socialising ideas on a 1-2-1 basis. The conversations were much easier and creative when we met as a group to make a decision that led to some form of change. I be…

Unanswered questions

1. How valid is it to change the test strategy during a project? Is that normal and valid in agile methodology?
2. Do you often end up not doing the actual testing in the end 100% based on the initial strategy and will deviate quite a bit from that? If so, do you go back to also modify the strategy as well based on what you ended up doing or is it more of a throw-away document in the end?
3. So I am working on a project that is 3 layered…I am only testing tbe backend which is Salesforce.The web and middleware are looked after by another team.If I want to write a test strategy,would I include things for the web and middleware even though I am not responsible for the testing.
4. What is the strategy to manage test cases that already noted while exploring testing? should I use test cases management tools or microsoft excell? is there any test case management tool that recomended?