To be successful a test leader needs to master skills within 10 different knowledge areas. In this section we consolidate our experience and formulate ‘no nonsense’ answers to frequently asked questions. We refer to our highly visual testing intelligenceTM framework.
|
|
"From theory to reality in 30 minutes." |
Because we believe the core of software testing is about managing risks, we started gathering our experience and answering frequently asked questions in the RISK knowledge area.
|
|
NEW - Question 7: When we perform a patch or maintenance activities, we may introduce new issues. How can we avoid this? Answer: You must accept that a patch is of the same nature than any other project and thus should follow the same type of treatment although lighter as the scope is by nature smaller than a project. |
|
NEW - Question 6: How sure are we about the quality, when all defined test cases are executed and passed? Answer: In order to feel confident about the quality level during and at the end of the test process: |
|
|
Question 5: We develop agile, can we still use a risk based test approach? Answer: A risk-based testing approach can be applied within an agile project but has to be adapted to this specific context. Step 1: Identify and analyze the risks of the project. This step remains ‘standard’ and will be applied to an agile project the same way it would be to a classic project. Identify your risks! Risk identification is an ... |
|
|
|
Question 4: How are risks mitigated when you implement a package (COTS)? Answer: To help you manage your risks during a package implementation, we propose you the below 3-step approach: Step 1: Start from YOUR processes and YOUR requirements! When implementing a package or commercial tool people often forget to think seriously about their own requirements. What do I want to achieve... |
|
|
Question 3: How do I know where I can cut a corner? Answer: In the testing world we know that we rarely get what we ask for. This is why we always prepare ourselves, so when we are being asked: “Can you do something to help reduce time/budget of the testing activities because we are running late/over budget on the project and we have to deliver?” We can answer: “Of course we can!” ... |
|
|
Question 2: What added value does testing bring me? Answer: Probably you have asked yourself this type of question multiple times. Why do I need to test my solution so badly? Can’t every developer just try a little harder not to make stupid mistakes? Can’t we all be a little more critical of ourselves? Testing costs a lot of money and it doesn’t seem to bring me any tangible benefits. With testing we only try to avoid costs by preventing failure. Testing is time consuming, we could launch much faster if we just could skip this phase. ... |
|
|
Question 1: When is testing still profitable for me? When does it stop to bring me benefits? Answer: You have made software testing an integrated part of your project life cycle. You want to deliver quality and you certainly want to offer value for money solutions to your end-users or customers! Of course you make sure your solution doesn’t bring damage or loss to yourself or others. Regulators might even impose you to a certain degree of testing... |
