A new practice was introduced during our last retro:
- In each ticket, QAs should provide a brief assessment towards Regression Risk if this new feature / fix is implemented.
My question is:
- It is hard to assess Regression Risk without looking at the source code; our sprint is three-week long, even we could look at the source code, 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