Scribd
Upload
38 views2 pages

QA Strategy For Testers: Manual System Testing

The QA strategy involves manual testing of all UI screens and requirements, maintaining test cases in written documents. Regression testing will rerun all tests on each commit and nightly to catch regressions. Load, stress and capacity testing will use tools to simulate heavy usage and ensure the system performs correctly under different loads. Beta testing will involve current customers, developers and the public to test specific features and report any issues.

Uploaded by

rajeshanandk
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
38 views2 pages

QA Strategy For Testers: Manual System Testing

The QA strategy involves manual testing of all UI screens and requirements, maintaining test cases in written documents. Regression testing will rerun all tests on each commit and nightly to catch regressions. Load, stress and capacity testing will use tools to simulate heavy usage and ensure the system performs correctly under different loads. Beta testing will involve current customers, developers and the public to test specific features and report any issues.

Uploaded by

rajeshanandk
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

QA Strategy for Testers

Manual system testing

• 100% of UI screens and fields


• 100% of specified requirements

The QA team will author and maintain a detailed written suite of manual tests to test
the entire system through the user interface. This plan will be detailed enough that a
person could repeatable carry out the tests from the test suite document and other
associated documents.

Regression testing

• Run all unit tests before each commit


• Run all unit tests nightly
• Add new unit test when verifying fixes

We will adopt a policy of frequently re-running all Manual/Automated tests, including


those that have previously been successful. This will help catch regressions (bugs
that we thought were fixed, but that appear again).

Load, stress, and capacity testing

• Simple load testing


• Detailed analysis of each scalability parameter

We can use a load testing tool and/or custom scripts to simulate heavy usage of the
system. Load will be defined by scalability parameters such as number of concurrent
users, number of transactions per second, or number/size of data items
stored/processed. We will verify that the system can handle loads within its capacity
without crashing, producing incorrect results, mixing up results for distinct users, or
corrupting the data. We will verify that when capacity limits are exceeded, the system
safely rejects, ignores, or defers requests that it cannot handle.
Beta testing Policy

• 4 current customers
• 40 members of our developers network
• 1000 members of the public

We must involve outsiders in a beta test, or early access, program. We must redirect
beta testers directions to focus on specific features of the system. We must actively
follow up with beta testers to encourage them to report issues.

You might also like