Thursday, September 1, 2011

QA Planning



Prepared by Shahana Shafiuddin

Quality Assurance Plan
Before Starting Testing we should check project information's
Standard testing
       Requirement:
      Test server: same configuration as client’s server.
      Documents:
       User manual
       Use case
       Client’s requirement doc
       Gui requirement doc
       Quality Assurance Plan
      Issue reporting software:
       Plan how the process will run. Like new, assigned, in progress, resolved, close
      Tester, developer or client will report bug with default assigned person.
      Authenticated person (project manager, scrum master, project owner, tech lead) will re-assign who will check and solve this issue
      Authenticate person will set the priority, sometimes after discussion with the client.
      Developer will resolved the issue after fixing and deploying in the test server.
      Bug reporter will check and if fixed will close and if not then will re-open the issue.
      If reopened
       developer will fix it again.
      Select the authenticated person who will be responsible to check issues and give answer of query of the testers.
      Sit in the developer’s room (preferred)
       Quality Assurance Plan
       Test script:
      Create check list on every function, button etc.
      Create test script on basis of check list.
      May not required when time is limited
      May not required when requirement is changing very frequently.
       Quality Assurance Plan
       Testing (may not need all, can be added in check list):
      Coding standard
      Installation from installation doc.
      Functionality
      Validation
      Gui
      Browser
      OS
      Usability
      performance
      Load testing
      Coding standard
      Resolved issue testing
      Quality Assurance Plan
       Work schedule:
      How long it will take or if parallel had to do other testing then ever day how many hours will be expended. Can use Gantt chart.
      After completion of every sprint may need to test.
       SQA audit:
      At the beginning how much bug found, resolved curve, after fixing how many left.
      Quality reporting. Report on plan based on audit if anything likes to add or edit in plan can recommend.
       Target to deliver:
      With the help of customer or project owner QA can identify major problems after fixing those project can be deliverable with minor problems.
      Quality Assurance Plan
Quick testing
       Requirement:
      Test server: same configuration as client’s server.
      Software documents:
       User manual
       Use case
       Client’s requirement doc
       Quality Assurance Plan
When we don’t have enough time to follow Standard way we should do a quick testing plan…..
       Quality Assurance Plan
Quick testing
       Requirement:
      Issue reporting software:
       Plan how the process will run. Like new, assigned, in progress, resolved, close
      Tester, developer or client will report bug with default assigned person.
      Authenticated person (project manager, scrum master, project owner, tech lead) will re-assign who will check and solve this issue
      Authenticate person will set the priority, sometimes after discussion with the client.
      Developer will resolved the issue after fixing and deploying in the test server.
      Bug reporter will check and if fixed will close and if not then will re-open the issue.
      If reopened developer will fix it again.
       Quality Assurance Plan
Quick testing
      person who will be responsible to check issues and give answer of query of the testers.
      Sit with the developer (preferred)
      May not required when requirement is changing very frequently.
       Quality Assurance Plan
Quick testing
       Testing (may not need all):
      Functionality
      Validation
      Gui
       Need design specification to compare.
      Browser
      Resolved issue testing
       Quality Assurance Plan
Thank you

Post a Comment