Too often, we hear testers complaining about bugs stuck in the backlog because they found them when running other tests than those specifically created for the acceptance criteria of a feature. It may sound familiar to you, too. You think that some of them may be critical bugs, but the feature is marked done, so team members will avoid dedicating effort to fix them sprint after sprint. How do you advocate for them to get adequate attention?
If you are a test automation developer, you might find bugs when creating the test automation scripts. If fixing the bugs is delayed from one sprint to the next, some tests will predictably fail during each run due to bugs that you know about and reported. Will you skip or ignore the tests that fail? Is there something else you can do to increase the chances of getting them fixed and have relevant test results dashboards?
Join our online session to discuss these challenges and others. We’ll show you how you can tackle them through examples from our work.