3

Few days ago, I have checked the tests of my node project. There are a lot of tests, but I ask myself which tests are necessary and which are not. I searched google and found very interesting strategy of "risk based testing". Now I'm looking for a good checklist for risk based testing.

3

The idea of risk based testing is that your context defines what the risks might be. What is important to me is not necessarily important to you. So there won't be a checklist that will work for everybody. Having said that: you might find this HTSM explanation useful. To guide your thinking about what could be risky in your situation and what area would warrant some better investigation/testing. But don't rely on lists only!

For more reading look here for James Bach and Michael Bolton and here. Another great source is Cem Kaner with his BBST series on Test Design.

| improve this answer | |
  • "So there won't be a checklist that will work for everybody." The risks and the software are different between projects. But the steps to identify and weight the risks are the same. I'm not experienced on risk base testing and looking for people who practice this longer time and know the important points (THE checklist :-) – Gerd Oct 10 '17 at 9:48
  • i.e. one point on this checklist is, "validate the potential damage of a failed test case ==> NO damage NO test" – Gerd Oct 10 '17 at 9:54
  • 1
    I think the HTSM is a good practical checklist. It makes you think about what might be worth looking into, depending on your specific context. To cite Cem Kaner: "Risk-based testing starts from an idea of how the program could fail. Then design tests that try to expose problems of that type." – Ray Oei Oct 10 '17 at 23:45
  • HTSM is a possible startpoint. But it is like you look for a travle guide for swiss but take a travle guide for europa :-( I think the checklist can only be created by people with experience in risk base testing. – Gerd Oct 11 '17 at 8:00
  • Believe me: the guys I am pointing you too do have a lot of experience. The point of having Europe is that it gives you an idea of where Switzerland is and how it is connected to it's neighbors. Maybe you thought you needed to be there but is actually Austria you are looking for. Anyway... to give a sense of testing without a map. And the general point being: you know the best what might be a risk to you. your product or your company. Go from there. What, if X fails, would happen? Would that be bad? If so: how to find it? – Ray Oei Oct 11 '17 at 13:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.