Hi!

Here's a presentation I and Jessica had for our internal development meetings. Feel free to read and give feedback.

Olle

Is risk-based testing already part of LS4?

Risk-based testing - risks in LimeSurvey
1.Catastrophic: Data loss or security issues
2.Critical: Blocking issues, e.g. “Next” button doesn’t work
3.Marginal: Some rarely used option won’t save
4.Negligible: Cosmetic issues, spelling etc

The "next button" is an interesting example.

An update rendering a next button nonworking can be any severity.
When you think about running surveys, a nonworking button can be catastrophic. It can mean dataloss, when you think of a survey during an event.

Another spin: Can a ComfortUpdate bug be marignal? Any how can QA tackle ComfortUpdate?

Sure, the severity levels can be discussed.

I wouldn't call CU bugs marginal. We have scripts to setup ComfortUpdate upgrades etc. Don't know how often they are used at the moment.

Tests should be coupled to the behavior of code and decoupled from the structure of code. Seeing tests that fail on both counts.

medium.com/@kentbeck_7670/test-desiderata-94150638a4b3

jelo wrote:

Tests should be coupled to the behavior of code and decoupled from the structure of code. Seeing tests that fail on both counts.

medium.com/@kentbeck_7670/test-desiderata-94150638a4b3

Yeah, that's what someone who promotes blackbox testing would say. There are many opinions about testing, for sure. Both blackbox and whitebox testing have pros and cons.

I promote "skin in the game". If developers use there own created stuff, they feel the bugs