Test Plan

Website session- "https://meet.jit.si/testClass1"

Version: 1.0
Created: 03/02/2022
Last Updated: 05/02/2022
Status: DRAFT
Revision and Signoff Sheet

Revision History Name Org/Group Role Email Date

Prepared by Trupti ABC org Test team lead zuretrupti@gmail.com 03/02/2022

Zure
Peer reviewer:
Table of Contents

1. Introduction............................................................................................................................4
1.1. Purpose.......................................................................................................................4
1.2. Project Overview.........................................................................................................4
2. Test Environment....................................................................................................................5
2.1. Hardware Requirements.............................................................................................5
2.2. Software Test Requirements.......................................................................................5
2.3. Test Environments Access Requirements....................................................................5
3. Testing Approach and Scope...................................................................................................6
3.1. In- Scope requirements...............................................................................................6
3.2. Out-of-Scope requirements.........................................................................................6
3.3. Testing Approach.........................................................................................................6
3.3.1. Test Phases.....................................................................................................6
3.4. Test Deliverable...........................................................................................................7
3.5. Detailed Schedule........................................................................................................7
3.6. Resources Management..............................................................................................7
3.6.1. Roles and Responsibilities for Conducting Tests.............................................7
3.7. Entry and Exit Criteria..................................................................................................8
3.7.1. Entry criteria...................................................................................................8
3.7.2. Exit Criteria.....................................................................................................8
3.8. Defect Process.............................................................................................................8
3.9. Test Metrics.................................................................................................................9
4. Assumption and Risks...........................................................................................................10
4.1. Assumptions..............................................................................................................10
4.2. Risks...........................................................................................................................10
5. Test Preparation and Execution............................................................................................11
5.1. Test Objectives..........................................................................................................11
5.2. Test Execution...........................................................................................................11
5.3. Supporting Links and Attachments............................................................................11
 6. TEST MANAGEMENT PROCESS.............................................................................................12
6.1. Test Management Tool..............................................................................................12
6.2. Test Cases Design Process.........................................................................................12
6.3. Test Execution Process..............................................................................................13
7. Approvals..............................................................................................................................15

1. Introduction

1.1. Purpose

This test plan describes the testing approach and overall framework that will drive the
testing of the "https://meet.jit.si/testClass1" session.

1.2. Project Overview

Jitsi meet is video conferencing solution. Jitsi Meet lets you stay in touch with all your
teams, family and friends.

The functionality of this website spans through the entire system, making audio and
video, screen sharing is available so you can share your desktop, presentation and more.
User can invite many members to a conference via a simple, custom URL. Trade messages
and emoji while your video conference, with integrated chat. No downloads are required
of your friends to join the conversation. Jitsi Meet works directly within their browsers as
well.
2. Test Environment

2.1. Hardware Requirements

The following hardware is required for testing:

- Application hardware infrastructure.

- Laptop/desktop for each tester.

2.2. Software Test Requirements

The following software will be required:

- HP ALM
- JIRA
- Standard browsers
- Microsoft Office

2.3. Test Environments Access Requirements

Testers will require access to the following URL:

- Jitsi Meet- https://meet.jit.si/testClass1

3. Testing Approach and Scope

3.1. In- Scope requirements

- User will have to give mic and cameras access. If any of the access is not given,
then an error message should be displayed to the user in the session.
- User’s mic/cameras will be ON by default and toggle option will be available to
turn ON/OFF mic and camera.
- Every user can see all the other user present in the same session and not in
different session.
- Share screen option will be available.
- Raise/Lower hand option will be available for each user.
- Users can send massages in group chat. Notification should be displayed to other
users.
- Users can toggle between 2 layouts.
- Connection statics of each user will be displayed to every user present in the
same session.
- Other settings will be available in 3 dots.

3.2. Out-of-Scope requirements

- Modules which are not affected as part of the release is not included in testing.
- Stress/Performance Testing are out of scope.

3.3. Testing Approach

Testing team will go with below approach to test this project

3.3.1. Test Phases

Test Phase Definition Comments

User Acceptance testing
Functional Testing
End users perform UAT test execution will be
acceptance tests to assess performed by end users
the overall functionality of
and QA Group will provide
and application. their support on creating
UAT script.
Functional testing will be Covered by testing team.
performed to check the
functions of website.

3.4. Test Deliverable

Sr.No. Deliverable Name Author Reviewer

1. Test Plan Test Lead Project Manager/ Business Analyst’s
2. Functional Test Cases Test Team Business Analyst’s Sign off
3. Logging Defects in HP ALM Test Team Test Lead/ Programming Lead
4. Daily/weekly status report Test Team/ Test Test Lead/ Project Manager
Lead
5. Test Closure report Test Lead Project Manager

3.5. Detailed Schedule

Deliverables Start date End date

Test Plan 03/02/20222 05/02/2022
Test Plan Review 06/02/2022 06/02/2022
Test Scripts Development 07/02/2022 14/02/2022
Test Scripts Review 15/02/2022 16/02/2022
Testing 20/02/2022 01/03/2022
Release to Production 10/03/2022

3.6. Resources Management

3.6.1. Roles and Responsibilities for Conducting Tests

Business Analysts

- Provide clarifications on requirements.

- Primary contact between business and QA team.

Project Manager

- Reviews the content of the Test Plan, Test Strategy and Test Estimates signs off
on it.

Test Lead

- Primary contact between QA team and project team for testing.

- Responsible for reviewing testing scripts.
- Works with testing team to assign defects to appropriate dev teams.
- Manages testing schedule and QA resources.

QA tester

- Responsible for logging defects in ALM QC, communicating defects and testing
status with test lead.
- Responsible for creating test scripts.

Roles Activities Recourse

Name
Project  Reviews the content of the Test Plan, Test
Manager Strategy and Test Estimates signs off on it.
Test Lead  Understand the requirement and scope
 Create test plan
 Manage the resources.
 Review test cases
 Creation of status reports/test closure reports.
Testing  Create test cases
 Team  Test cases execution
Members  Logging defects

3.7. Entry and Exit Criteria

3.7.1. Entry criteria

 All the requirements and design documents have been completed, reviewed and
sign off.
 The test plan document has been completed, reviewed and sign off.
 The test cases have been completed, reviewed and sign off.
 The test environment has been configured.
 Unit tests has been completed by the development team.

3.7.2. Exit Criteria

 All planned tests have been executed.

 All critical and high priority defects have been fixed, validated and closed.
 Desired and sufficient test coverage of the requirements and functionalities
under the test.
 All remaining defects are either cancelled/Deferred or documented as Change
Requests for a future release.
 Test Closure completed and signed off

3.8. Defect Process

Defects found during the Testing will be categorized according to the bug-reporting tool
“HP ALM” and the categories are:

Severity Testing Severity definition

1 (Critical)  A defect that completely hampers or blocks testing of the
product/ feature is a critical defect.
2 (High)  Any Major feature implemented that is not meeting its
requirements/use case(s) and behaves differently than
expected, it can be classified under Major Severity.
3 (Medium)  Any feature implemented that is not meeting its
requirements/use case(s) and behaves differently than
expected but the impact is negligible to some extent or it
doesn’t have a major impact on the application, can be
classified under Medium Severity.
4 (Low)  Any cosmetic defects including spelling mistakes or
alignment issues or font casing can be classified under Low
Severity.
 3.9. Test Metrics

Report Description Frequency

Test
To report on % Execution, % Pass, % Fail
preparation
Defects severity wise Status – Open, closed, Weekly / Daily
& Execution
any other Status
Status
Daily
To report on Pass, Fail, Total defects,
execution Daily
highlight Showstopper/ Critical defects
status
Weekly – If project team
Project
needs weekly update apart
Weekly Project driven reporting (As requested by
from daily and there is
Status PM)
template available with
report
project team to use.
4. Assumption and Risks

4.1. Assumptions

 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.
 Test environment and preparation activities will be owned by Dev Team
 BUSINESS ANALYST will review and sign-off all Test cases prepared by Test Team prior
to start of Test execution
 The defects will be tracked through HP ALM/JIRA. Any defect fixes planned will be
shared with Test Team prior to applying the fixes on the Test environment
 Project Manager/BUSINESS ANALYST will review and sign-off all test deliverables
 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.
 There is no environment downtime during test due to outages or defect fixes.
 The system will be treated as a black box.

4.2. Risks

Sr. Risk Probability Impact Description Mitigation Plan

No
1 Changes in requirement after High Test Plan/Test cases Requirements should
execution begins will need to be be finalized before
modified in middle execution window.
of execution.
2 Addition/Changes to the High Defects would be Share the updated
requirement if not shared with raised even though requirements to the
the testing team the changes are testing team before
implemented as part the code fix takes
of the requirement. place.
3 All the functionalities High Test execution gets Dev team to provide
/Environment not available on impacted for first a signed-off release
the Day 1. few days of the plan for the changes.
 week.
4 Unavailability of team members Medium Test execution may Movements of
be affected . resources from other
projects.

5. Test Preparation and Execution

5.1. Test Objectives

The objective of the test is to verify that the functionality of Jitsi Meet session 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 via CR.

The final product of the test is twofold:

 A production-ready website.
 A set of stable test scripts that can be reused for Functional and UAT test execution.

5.2. Test Execution

Testing team will go with below approach to test this website.

5.3. Supporting Links and Attachments

Sr no. Document Name Location

1 Test plan location
2 Project Trackers
3 MLQC path for test
cases
4 Test cases location
6. TEST MANAGEMENT PROCESS

6.1. Test Management Tool

HP Application Lifecycle Management is the tool used for Test Management. All
testing artifacts such as Test cases, test results are updated in the HP Application
Lifecycle Management (ALM) tool.
 Project specific folder structure will be created in HP ALM to manage the status
of this project.
 Each resource in the Testing team will be provided with Read/Write access to
add/modify Test cases in HP ALM.
 During the Test Design phase, all test cases are written uploaded into HP ALM.
 Each Tester will directly access their respective assigned test cases and update
the status of each executed step in HP ALM directly.
 Any defect encountered will be raised in HP ALM linking to the particular Test
case/test step.
 During Defect fix testing, defects are re-assigned back to the tester to verify the
defect fix. The tester verifies the defect fix and updates the status directly in HP
ALM.
 Various reports can be generated from HP ALM to provide status of Test
execution. For example, Status report of Test cases executed, Passed, Failed, No.
of open defects, Severity wise defects etc.

6.2. Test Cases Design Process

Analysing and Establishing Incorporating

SME /Peer
Understandin Traceability Preparation Review
Review of
g Matrix in HP of Test cases comments in
Test cases
Requirments ALM test cases

 The tester will understand each requirement and prepare corresponding

test case to ensure all requirements are covered.
 Each Test case will be mapped to Use cases to Requirements as part of
Traceability matrix.
 Each of the Test cases will undergo review by the BUSINESS ANALYST and
the review defects are captured and shared to the Test team. The testers
will rework on the review defects and finally obtain approval and sign-off.
  During the preparation phase, tester will use the use case and functional
specification to write step by step test cases.
 Sign-off for the test cases would be communicates through mail by Business
Analyst’s.
 Any subsequent changes to the test case if any will be directly updated in
Test cases bed.

6.3. Test Execution Process

Participate in
Execute each of Mark Status as Raise defects for Send the daily Complete the
Defect Triage
the test step in Pass/Fail in HP the failed test status report to test execution of
cycle and explain
test case ALM cases in HP ALM Test Lead all the test cases
the defects

 Once all Test cases are approved and the test environment is ready for
testing, tester will start testing of the website to ensure the website is stable
for testing.
 Each Tester is assigned Test cases.
 Testers to ensure necessary access to the testing environment, HP ALM for
updating test status and raise defects. If any issues, will be escalated to the
Test Lead and in turn to the Project Manager as escalation.
 If any showstopper during testing will be escalated to the respective
development SPOCs for fixes.
 Each tester performs step by step execution and updates the executions
status. The tester enters Pass or Fail Status for each of the step directly in HP
ALM.
 If any failures, defect will be raised as per severity guidelines in HP ALM tool
detailing steps to simulate along with screenshots if appropriate.
  Daily Test execution status as well as Defect status will be reported to all
stakeholders.
 Testing team will participate in defect triage meetings in order to ensure all
test cases are executed with either pass/fail category.
 If there are any defects that are not part of steps but could be outside the
test steps, such defects need to be captured in HP ALM and map it against
the test case level or at the specific step that issue was encountered after
confirming with Test Lead.
 This process is repeated until all test cases are executed fully with Pass/Fail
status.
 During the subsequent cycle, any defects fixed applied will be tested and
results will be updated in HP ALM during the cycle.

As per Process, final sign-off or project completion process will be followed.

7. Approvals
Approved By ORG Role Approval(Location of approval
evidence, could be mail or in tool)
ABC ORG. Delivery Lead
ABC ORG. Project Manger
ABC ORG. Business Analyst
ABC ORG. Technology lead