Skip to main content

QA Process for a scenario testing

QA Process for a Scenario Testing

Road Map to QA:

Early planning and commitment
Acquiring test materials
Day-to-day QA operations

QA Communication:

The main channel of communication for QA process is via Email.

Test Management Tools: Test Management Tools to prepare Test Requirements, Test Plan, Test Cases, and to log Defects.

Test Management Tools Example: Quality Center, JIRA, qTest, Bugzilla, IBM Rational Quality Manager, Microsoft TFS.
Note: Other testing tools may be used as per client requirements.

QA Processes:

Preliminary Testing: Run test cases, prior to deployment to Test or Stage environment, to have a clear understanding of Scenarios and to get clarification before testing in Test or Stage environment.(Test, Stage Environments are Testing purpose Environments)

Test Environment:

Execute test cases in test environment and report results.
Test-End Activities:

1. Send Project Status Report to all stakeholders.

2. Communicate Query/clarification/observations via mail.
Test Environment: Execute test cases in test environment and report results.

3. Send Project Status Report to all stakeholders.

4. Communicate Query/clarification/observations via mail.

Build/Stage Environment:

Execute test cases in stage environment and report results.

Test-End Activities:

1. Send Project Status Report to all stakeholders.

2. Communicate Query/clarification/observations via mail.

3. In case testing is complete and no issues found, send a mail to the User Acceptance Tester for UAT Approval. (cc to all stakeholders)

4. After UAT approval, prepare Testing Sign-Off Document and attach it to the related to Release item and

5. Send an Email to Release Management notifying them that scenario# is ready for upload.

Deployment to Production:
Test-Start Activities:

1. When we see an email from deployment person stating that “deployment ABC# is complete/done.”, respond to all immediately stating the following: QA validation has begun for ABC#.

2. Validate the ABC#.

3. Report the defects if any found.

Test-End Activities:
1. If any issues are found, then only email to the stake holders (developer, PM, User Acceptance Tester …) and Release Manager.

2. Else, if no issues are found, respond back “to all” to the email from deployment person and say “QA validation is complete for ABC#. No issues found.”

Project Status Report:
• The Project Status Report should be send to all stake holders on daily basis.• “Accomplishments” should contain all the steps that have taken place in that Scenario till date.• If we encounter a critical issue and mention it in project status report, ensure that we bold the text and highlight it in red so that the viewer can find out that the issue is critical and needs to be looked at immediately.• Naming Convention example: Status Report – Scenario Number.

Testing Sign-Off Report:

Testing Signoff Report needs to be attached to the Release item after testing is complete and UAT approved.UAT Approval email’s screen shot should be attached in it.Naming Convention Example: TSO for ABC#