Skip to content

New Feature or Bug Ticket Testing Process

Jump to bottom
rachitasharma edited this page May 23, 2016 · 5 revisions

We have a RapidBoard setup for tracking the progress of current sprint tickets.

  • In the Story Rapid Board Workflow, story/bug tickets are first lined up under the "To Do" Status. From here, a developer would assign a ticket to himself and place it under "Development". Once the developer is done with writing the code and unit Tests, a QA would do branch testing for that specific piece of work done. This is done by deploying the branch code on one of the available servers and testing the requirements of the ticket and also doing regression testing around that functionality.

  • A ticket moves from "Development" to "Code Review" when branch testing for the ticket is complete and no issues have been raised. If there are any concerns, then the developer needs to fix them and the QA needs to branch test that code again.

  • Once the code has been reviewed for quality and merged to master, the ticket moves from "Code Review" to "Waiting in QA". QA picks up story/bug tickets in "Waiting for QA" and move them to "In QA" and tests them on the latest master code.

  • Once the testing is complete and all requirements on the ticket are met as expected, the ticket is moved from "In QA" to "Resolved".

The idea is to let the testing seamlessly blend into a parallel development/testing phase where continuous code check-in, build and testing is done.

QA Checklist for testing new feature tickets

  • Test to confirm if all requirements on the ticket have been met
  • Check for any Field Level or User Interface Validations that should be in place
  • Test all possible scenarios for confirmation/success message
  • Test with Boundary values and invalid values
  • Check for any error/exceptions messages during the testing
  • If a UI related feature, then test the ticket in all browsers
  • Add test cases for this feature to this ticket
  • Test the module using that feature to check for any regression
  • Have all communication with the developer documented on the ticket as comments

QA Checklist for testing bug tickets

  • Add test scenarios covered on the ticket
  • Verify if all the issues specified on the ticket are met
  • If testing a UI related fix then test it in all browsers
  • Have all communication with the developer documented on the ticket as comments

Breeding Management System Documentation

Clone this wiki locally