Testing PLAN

Testing Plan :
1. Introduction
Before any test activity occurs, it’s important to define the scope of testing for your
release. This means defining the features or functions that need to be included in the
release, considering any constraints and dependencies that can affect the release, and
determining what type of release it is.
Examples of questions to ask when defining the release scope include:
● Are there new features being released in this version?

● What are the risk areas?
● Are there any particularly sticky areas where you’ve seen regressions in the
past?
● What type of release is it? Is this a maintenance release that includes bug fixes?
Is this a minor feature release? Is this a major feature release?
● What does being “done” actually look like for your team?
2. Testing Resources
● Raja Srinivas (Testing Manager)
● Chandravathi (Tester)
● Rajeev (Tester)
● Suneela (Tester)
3. Testing approaches
•Testing approach and methodology
•Types of testing to be performed (e.g., functional, smoke, performance, usability,
Regression)
4. Test Schedule
•Timeline for each testing phase
5. Risks & Issues

•Risks associated with the testing process
•Mitigation strategies for identified risks
Types of Testing with Flow :
Step 1: Functional testing: Verify that all functionalities and features of website are
working as expected
● Unit test : Developers will perform this testing

● Integration test: Suresh will perform this testing
● System test: Raja will perform this testing
Resources:
Step 2: Usability testing: Evaluate the website's user interface for ease of use.
● Navigation testing:
● Compatibility testing:
● Content testing:
Resources:
1. Usability testing tools : Screen recording softwares OBS Studio, Camtasia, or
QuickTime Player, Shortcut for windows machines( Windows + Alt + R)
2. Usability testing platforms: UserTesting, TryMyUI, or UserZoom
Step 3: Performance testing: Assess the website's speed, scalability, and stability under
various load conditions.
● Load test
● Stress test
● Scalability test
Resources:
1. Performance testing tools: (Apache J meter, Gatling, Locust, Load runner)
Note: Except LoadRunner remaining 3 Open source tools
2. Monitoring tools: ‘top’ (Linux), Task Manager(Windows), Nagios, Zabbix, or
Prometheus
Step 4: Compatibility testing: Ensure the website is compatible with different browsers,
devices, and operating systems
● Browser compatibility test

● Device compatibility test
Resources:
1. Test devices and browsers
2. Compatibility testing tools
● Responsive testing : Responsinator, Am I Responsive?, or Screenfly.
● Cross-Browser testing: BrowserStack, Sauce Labs,
CrossBrowserTesting, or LambdaTest.
● Mobile compatibility testing: Appium, Selendroid, or TestComplete Mobile
Step 5: Regression testing: Ensure that recent code changes have not adversely
affected existing features
Resource:
1. Test plan: A detailed document outlining the scope, approach, resources,
and schedule of regression testing
2. Test Suite: A set of test cases specifically designed to cover critical
functionalities of the system.
Testing Flow :
1. Requirement (SRS review / Analysis)

2. Test plan creation
3. Test cases creation
4. Test cases Execution
5. Defect Logging (Bug report)
6. Defect fixes & reverification
Steps for Test cases Preparation
Step 1 – Test Case ID:

In this step, the tester will assign a unique identifier to the test case. This allows the
tester to recall and identify the test case in the future easily.
Example: TC-01: Verify Login Functionality for a User
Step 2 – Test Case Description:

The tester will describe the test case, outlining what it is designed to do. The tester may
also provide a brief overview of the expected behavior. An Example: Test Case
Description: Test for Logging Into the application Given: A valid username and
password for the web application When: User enters the username and password in the
login page Then: the user should be able to log in to the application successfully. The
Home page for the application should be displayed.
Step 3 – Pre-Conditions:
The tester will document any pre-conditions that need to be in place for the test case to
run properly. It may include initial configuration settings or manually executing some
previous tests. A Precondition example in testing could be that the test environment
must be set up to be very similar to the production environment, including the same
hardware, operating system, and software.
Step 4 – Test Steps:

The tester will document the detailed steps necessary to execute the test case. This
includes deciding which actions should be taken to perform the test and also possible
data inputs.
Example steps for our login test:
1. Launch the login application under test.
2. Enter a valid username and password in the appropriate fields.
3. Click the ‘Login’ button.
4. Verify that the user has been successfully logged in.
5. Log out and check if the user is logged out of the system.
Step 5 – Test Data:

The tester will define any necessary test data. For example, if the test case needs to
test that login fails for incorrect credentials, then test data would be a set of incorrect
usernames/passwords.
Step 6 – Expected Result:

The tester will provide the expected result of the test. This is the result the tester is
looking to verify. Examples of how to define expected results:
1. A user should be able to enter a valid username and password and click the login
button.
2. The application should authenticate the user’s credentials and grant access to the
application.
3. The invalid user should not be able to enter the valid username and password; click
the login button.
4. The application should reject the user’s credentials and display an appropriate error
message.
Step 7 – Post Cleanup

The tester will provide any cleanup that needs to be done after running the test case.
This includes reverting settings or cleaning up files created during the test case.
Example: 1. The user can successfully log in after providing valid credentials. 2. After
providing invalid credentials, The user is shown the appropriate error message. 3. The
user’s credentials are securely stored for future logins. 4. The user is taken to the
correct page after successful login. 5. The user cannot access the page without logging
in. 6. No unauthorized access to the user’s data.
Step 8 – Actual Result:

The tester will document the actual result of the test. This is the result the tester
observed when running the test. Example: After entering the correct username and
password, the user is successfully logged in and is presented with the welcome page.
Step 9 – Status:
The tester will report the status of the test. If the expected and actual results match, the
test is said to have passed. If they do not match, the test is said to have failed.
Example: Tested the valid login functionality. Result: The user is able to log in with valid
credentials. Overall Test Result: All the test steps were successfully executed, and the
expected results were achieved. The login application is functioning as expected.
Tested for Invalid Login functionality. Result: The user is unable to log in with invalid
credentials. Overall Test Result: The invalid login functionality has been tested and
verified to be working as expected

3.

Testing PLAN

Uploaded by

Copyright:

Available Formats

Testing PLAN

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Testing PLAN

Uploaded by

Copyright:

Available Formats

Testing Plan :

Examples of questions to ask when defining the release scope include:

● Are there new features being released in this version?

5. Risks & Issues

● Unit test : Developers will perform this testing

● Browser compatibility test

1. Requirement (SRS review / Analysis)

Steps for Test cases Preparation

Step 1 – Test Case ID:

Example: TC-01: Verify Login Functionality for a User

Step 2 – Test Case Description:

Home page for the application should be displayed.

hardware, operating system, and software.

Step 4 – Test Steps:

Example steps for our login test:

1. Launch the login application under test.

2. Enter a valid username and password in the appropriate fields.

3. Click the ‘Login’ button.

4. Verify that the user has been successfully logged in.

Step 5 – Test Data:

Step 6 – Expected Result:

looking to verify. Examples of how to define expected results:

the login button.

Step 7 – Post Cleanup

in. 6. No unauthorized access to the user’s data.

Step 8 – Actual Result:

expected results were achieved. The login application is functioning as expected.

verified to be working as expected

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.