A new practice was introduced during our last retro:

  • In each ticket, QAs should provide a brief assessment towards if this new feature / fix is implemented.

My question is:

  • It is hard to Regression Risk without looking at the ; our sprint is three-week long, even we could look at the source , there is not enough time to do so. Are there any good rules of thumbs when providing Regression Risk assessment without looking at its source code?



Source link https://sqa.stackexchange.com/questions/34739/how-to-assess-regression-risk-without-looking-at-the-source-code

LEAVE A REPLY

Please enter your comment!
Please enter your name here