What is Test Plan

Test Plan: Here we learn what is test plan and what it consists.

Test Plan is a document which consists of all the information related to testing like what are we going to test, in scope, out of scope, resource management, etc.

Let’s assume we are working on a banking application where we have two modules debit card and credit card. Consider we are working for debit card management and this is how our test plan will go with respect to In-Scope and Out-of Scope

Best Selenium Online Training

Our Trainer Profile 

In-Scope:

Debit card management testing will be in the scope of testing

Browsers & Operating Systems:

Testing will be performed in the below browsers

IE with version IE8 and above

Chrome version with 42 above

Operating  Systems: Testing will be performed in below OS

Windows with version 2008 and above

Android version 2.0 and above

IOS version with 3.0 and above

Out of Scope:

Credit management testing is out of scope

Browsers and Operating systems other than above is not in scope for testing

Test Environment: The test environment should be set up and access should be given testing team as well as to the Dev team.

Types of Testing:

1. Regression Testing: In this testing we consider end-to-end flow as part of regression. We planned to do this testing through automation only
2. Sanity Testing: We also perform sanity testing
3. Functional testing
4. Installation / Un-installation Testing (If applicable)

Automation:

We do functional automation and non-functional (performance testing) as part of the automation

Selenium is the tool that will be used for functional automation

Load Runner is the tool that will be used for performance testing

We do in-sprint automation for every sprint.

Best Selenium Online Training

Our Trainer Profile 

Entry Criteria:

1. Test environment setup should be completed
2. The testing team provided access to this environment
3. All the test scenarios and test cases are prepared and ready for execution
4. Test cases are reviewed and approved by the client (if applicable)
5. All the tools related to automation is purchased and ready to use
6. Test Management & Defect Management tools are purchased and ready to use
7. The team got all the relevant KT on the domain
8. The team got training related to testing management/defect management tools

Exit Criteria:

1. All the test cases are executed and 95% of the test cases are passed.
2. No test cases are in blocked status
3. All the defects with Critical, High & Medium severity defects are closed

Risks:

1. If there is a delay from the development team of delivering to the testing team will lead to slippage of committed release date to the client. Mitigation plan will testing team needs to work on weekends to cover the delay.
2. Resource Management:
   1. What if a resource becomes sick and will not be available for a week
   2. What if resource got some personal emergency and will not be available for a week
3. Too Many defects: If the testing team raised too many defects and this would lead to additional efforts for Dev & Testing teams. This will also lead to slippage of derivable times

Deliverables:  Here we indicate to the client what are documents we are going to deliver once the project is completed.  It may differ to client to client and there is no rule that we need to deliver only the below documents. Here we are not talking about any deliverables from the development team and it will not be part of the Test Plan

1. Test Plan
2. Test Cases
3. Test Summary Report
4. Automation Scripts

Best Selenium Online Training

Our Trainer Profile