Test Plan:: Google Website
Test Plan:: Google Website
Test Plan:: Google Website
Google Website
Version: 1.0
Created: 02/05/2014
Last Updated: 02/05/2014
Status: DRAFT
Tester: Priti Gupta
Revision history
1. Introduction………………………………………...4
2. Test Strategy………………………………………..5
3. Execution Strategy………………………………….8
4. Appendix A………………………………………….9
1. Introduction
The Test Plan document documents and tracks the necessary information required to effectively
define the approach to be used in the testing of the Google Website. Its intended audience is
the project manager, project team, and testing team. Some portions of this document may on
occasion be shared with the client/user and other stakeholder whose input/approval into the
testing process is needed.
1.1 Scope
Testing some main requirements and the most used services of the website. Some
Functionalities and services that will be tested are:
1) Functionality Testing
The following testing must be carried out while doing Website
Functionality testing:
A) Validation testing
B) Links/URL Testing
C) Required field and optional field validation
2) Usability testing
The Usability Testing is comes under a Black Box Testing Technique where
testing is to be carried out with users point of view. It is a technique
implemented in user-centred interaction design to evaluate a product or
service by testing it with representative users.
A) Accessibility
B) Identity
C) Navigation
D) Content
3) Compatibility testing
In Website Testing Checklist, the Compatibility Testing make sure that the
web pages are properly rendering different browsers like IE8, IE9, IE10, IE11,
Chrome, Firefox, Safari, Opera etc. Also verify if it is working properly on
different Operating systems like Windows, Linux, and Mac on different
hardware configurations.
4) Performance testing
Performance testing can be applied to understand the website’s scalability,
any loopholes in the load balancing and to test the response time between a
request (from the client) and the reply (from the server) and the amount of
load/stress the site is able to sustain.
1.2. Audience
Project team members perform tasks specified in this document, and provide
input and recommendations on this document.
The stakeholders’ representatives and participants (individuals as identified
by the PMO Leads) may take part in the UAT test to ensure the business is aligned
with the results of the test.
Technical Team ensures that the test plan and deliverables are in line with the
design, provides the environment for testing and follows the procedures related to the
fixes of defects.
2. TEST STRATEGY
The objective of the test is to verify that the functionality of Google Website works according
to the specifications.
The test will execute and verify the test scripts, identify, fix and retest all high and medium
severity defects per the entrance criteria, prioritize lower severity defects for future fixing
The final product of the test is twofold:
• A production-ready website.1
• A set of stable test cases that can be reused for Functional and UAT test execution.
General
Exploratory Testing would be carried out once the build is ready for testing.
The Test Team will be provided with access to Test environment via VPN connectivity
The Test Team assumes all necessary inputs required during Test design and execution
will be supported by Development/BUSINESS ANALYSTs appropriately.
Test case design activities will be performed by QA Group
The project will provide test planning, test design and test execution support
Test team will manage the testing effort with close coordination with Project
PM/BUSINESS ANALYST
Project team has the knowledge and experience necessary, or has received adequate
training in the system, the project and the testing processes.
Functional Testing
During Functional testing, testing team will use preloaded data which is available on the
system at the time of execution
The Test Team will be perform Functional testing only on www.google.com
UAT
UAT test execution will be performed by end users (L1, L2 and L3) and QA Group will
provide their support on creating UAT script.
Client Environment Personal computer workstations used during system testing must have
the following configuration:
Operating systems (OS): Browsers:
Windows 10 Internet Explorer (IE) 5.50 and
Windows XP higher
MAC Google Chrome
Ubuntu Safari
Test Data Test data will be created in the test scenarios documented or as needed
in test scenarios not document in detail.
Test Tools Chrome DevTools
Internet Connection: 50kbps or higher
MILESTONE LIST
The milestone list is tentative and may change due to below reasons
a) Any issues in the System environment readiness
b) Any change/addition in scope
c) Any other dependency that impacts efforts and timeline
Scope: The below excel sheet details about the scope of Functional test. The
scope is high level due to changes in the requirement.
TEST DELIVERABLES
2.5.4 UAT
PURPOSE: this test focuses on validating the business logic. It allows the end users
to complete one final review of the system prior to deployment.
TESTERS: the UAT is performed by the end users (L1, L2 and L3).
METHOD: Since the business users are the most indicated to provide input around
business needs and how the system adapts to them, it may happen that the users do
some validation not contained in the scripts. Test team write the UAT test cases
based on the inputs from End user (L1, L2 and L3 users) and Business Analyst’s.
TIMING: After all other levels of testing (Functional and Performance) are done.
Only after this test is completed the product can be released to production.
3. EXECUTION STRATEGY
3.1. Entry and Exit Criteria
Test Technical
Exit Criteria Notes
Team Team
100% Test Scripts executed Done