Norton QA test process starts from inception of the project level.
The team picks up the requirements (or User stories) and creates
documents such as Test Plan, Test Cases, Test scripts.
Once Test cases are written, they are sent to Business Analyst(s)
and Tech team for approval.
Once Test cases are approved, they are distributed among test team
members for execution.
As part of the software delivery lifecycle (SDLC), QA team receives builds, execute the Test
suites, report bugs.
After completion of first round, QA automation team starts putting together the automation stories on JIRA board.
Once the stories are approved by QA project leads, automation Engineers start writing scripts to cover Regression scenarios.
Upon completion of each end-to-end scenarios, automation scripts are run to support regression testing.
Before signing off the release, QA team puts together “Risk Analysis” meeting making sure all risks have been mitigated.
If release version risks any performance issue, QA automation team prepares load scripts to measure the performance level by comparing the results with baseline.
Once all executions are done, other test methods are completed, all bugs are closed, and code coverage testing done 100%, the project is signed-off and certified by QA Project lead.
QA project leads always perform audits on executions, coverage, methods and results before any final certification.