Regression Testing - slander36/IssueTrackerTraining GitHub Wiki

You think you've fixed the bug

But that's not always the case. Regression testing is when a tester/issue creator must verify if the bug fixer did their job. While this is usually the case (who wants to spend all that time and not fix the issue) there are times where things go wrong.

Reproduce the bug

Those reproduction steps from earlier will come in real handy now, as you must use them to verify the fix. Use the reproducibility to figure out how much testing the bug needs before you can sign off on it. There's nothing worse than having to reopen a closed bug.

It's fixed!

Nothing really to say here. Close it out and call it a day.

It's not fixed!

See Bug Creation for a full guide for (re)creating the bug. The basics here are to update and add to the original bug's information, especially the steps to reproduce and the reproduction rate.

Is that it?

Yes, that's it. Regression testing is a simple task, and it feels good to spend the morning/evening closing out bugs.