Contact Us

Contact Us

Quality Assurance Process

The Process Followed By Technosoft:

Quality Assurance Test Planning

  1.   SDM appoints QATL and QA Engineer at the start of the project. QA TL receives the requirements from the client or PM.
  2.   QA TL creates FS document according to received requirements and shares that document with all stakeholders.
  3.   Client reviews the document and gives feedback.
  4.   All queries of stakeholders are discussed and resolved by continuous scrums and meetings.
  5.   Requirements are updated in FS according to the client’s comments after reviewing documents.
  6.   After the approval of requirements from the client, Project is moved to the development phase.
  7.   QA lead prepares Test plan which is sent to PM for review. QA team creates test scenarios and traceability matrix according to the requirements.
  8.   The client is asked about the module he needs to be implemented in the first iteration
  9.   During implementation phase Manager, Dev Team, And QA lead is completely involved in tracking the progress of software to make sure it meets client requirements.
  10.   Once it is decided that what is to be delivered to the client in iteration 1, tasks are added in JIRA according to iterations defined.
  11.   QA TL determines the scope of system testing along with acceptance criteria.
  12.   QA TL appoints a QA Engineer for the testing of the desired iteration.

Quality Assurance Testing Estimation

  1.   After having a clear picture of requirements, QA Engineer decides estimates for testing.
  2.   Estimates decided by QA Engineer are reviewed by QA TL.
  3.   QATL updates the estimates (if needed)
  4.   After approving Estimates, QATL sends those estimates to PM.

Quality Assurance Test Designing

  1.   QA Engineer starts identifying and documenting test scenarios as per the task division
  2.   QA Engineer prepares detailed test cases
  3.   QA TL reviews the test cases created by QA Engineer
  4.   QA Engineer updates test cases to accommodate QATL review comments (if required)
  5.   QA TL ensures the readiness of test bed with respect to hardware and software (software includes supporting software e.g. operating system, web browsers, etc. and setup of     application and database server)

Testing and Defect Resolution

  1.   Dev Team sends the release to QA Team
  2.   QA team starts Application Acceptance Testing by applying smoke test cases to make sure there is no blocker/show-stopper in the application.
  3.   If the application does not meet acceptance criteria (no blocker issues), QA team reports defects and build is sent back to Dev team.
  4.   Once the application is passed through acceptance criteria, detailed testing of application is started by the QA Team.

During the systems testing cycle, QA Team executes test cases from test specification as per the sequence defined in the test plan.

  1.   QA Team logs the identified defects in Test Management Tool (JIRA or Yodiz) assigning the status and severity
  2.   DevTL reviews the logged defects and assigns to the concerned developer for fixing
  3.   Assigned developers fix the defects and update the defect status.
  4.   DevTL reviews the fixes and updates the status of defects needs to be sent in the build against defects
  5.   DevTL sends the build to QA Team with fixation of logged issues.
  6.   QA Team verifies all fixed defects with the appropriate status included in the current build.
  7.   After fixes verification, QA Team assigns appropriate statuses to the defects.
  8.   QA Team performs localize regression against defect fixes if required.
  9.   QA team reports issues to DEV team if any (In this case new testing cycles occur), or otherwise declares the closure of build if all issues are fixed and verified.
  10.   During all testing cycles, QA Team/QATL sends testing status to the relevant stakeholders.

Deployment to Client Environment

  1.   Once build is passed by the QA team, it is deployed to the Client environment where he/she performs his testing.
  2.   Client reviews the build and updates with the Feedback.
  3.   If the client is okay with what he has received, build is moved to the production environment and QA team performs a smoke test on production.
  4.   If the client needs any changes, the dev team starts working on client feedback and again testing process takes place as mentioned above.