-
Notifications
You must be signed in to change notification settings - Fork 2
QA Responsibilities
-
Test to ensure that the new feature added meets the appropriate standards and requirements
-
Branch test every task before the code is reviewed and merged into master branch
-
Biweekly Smoke Test the complete product using the smoke test Test Plan maintained on the TestLink Tool
-
Test every story/bug ticket merged into master code
-
Regression Test each module of the product by executing test cases from Test Plans maintained for all the modules on TestLink
-
Create bug tickets for new issues found following a specific format to ensure that all details are included and ensuring that there is no existing bug ticket for it already to avoid duplicate tickets
-
Do performance testing using large test data to find product limitations and possibilities for future improvements
-
Test bug tickets reported by clients to reproduce the bug
-
Retest and close any old bug tickets reported regularly
-
Create improvement tickets for adding/improving validation messages or UI design in the product
-
Add/update test data for various functionalities of the product
-
Add test cases for new features added in a Sprint cycle to the TestLink Tool
-
Review and update any existing test cases if needed
-
Raise blocker/important bugs immediately to the team
-
Follow the release process for testing when a client release is scheduled
-
Sanity testing the product on IE, Chrome and Firefox
Breeding Management System Documentation