4 ms·

Why would I want to link tests to bugs? Or track the history of tests? Or assign someone to a failing test? I've found they either fail or they pass, and you fi

• ajeet_dhaliwal 7y ago
  If you don’t see it as something you need, you probably don’t ... at least not yet. Ive been an Engineering Manager and Head of Quality Engineering and when you end up with hundreds or thousands of test cases, either in one product or service or across many, managing the output of testing becomes a challenge. There may be low priority regressions that you want to fix later and create bugs for and link to failing tests so you know you’re waiting on those fixes before you expect the tests to pass. If there is a problem with a test itself then assigning it to a team member to fix is useful. Tracking history helps identify flaky test cases - they’re automatically highlighted as being flaky. Consolidating tests from several sources helps understand the overall health of a project. If you’re maintaining a product or service that goes through a lot of change and there’s say 10 people or more on a team managing all of this becomes increasingly difficult. With respect to pricing it’s free to try and $25/month per target so not particularly expensive.