Advantage web app test plan

Get Started. It's Free
or sign up with your email address
Rocket clouds
Advantage web app test plan by Mind Map: Advantage web app test plan

1. Introduction

1.1. Purpose

1.2. Test approach

1.3. Project general overview

1.4. Definitions, acronyms and abbreviations

1.4.1. QA - Quality Assurance

1.4.2. UX - User experience

1.4.3. LO - Learning Object

1.4.4. FF - Flexible folder

1.4.5. SRS - Software Requirements Specification

1.4.6. GUI - Graphical User Interface

1.4.7. TFS - Team Foundation Server

1.4.8. FUT - Feature under test

2. Test items

2.1. Sub functionality

2.1.1. Roles permission

2.1.2. Browser compatibility

2.2. Synchronization system

2.3. Web app functionality

2.3.1. Browser compatibility

2.3.2. Desktop web app

2.3.3. Roles permission

2.3.4. Learning module

2.3.5. Social Network module

2.3.6. Search

2.4. Settings

2.5. Business logic rules

3. Features to be tested

4. Features not to be tested

4.1. Integration with facebook/twitter/linkedin sites

4.2. Content testing

4.3. Trending news testing

5. Test strategy

5.1. Test approach

5.1.1. General info

5.1.2. Test focus for project

5.2. Test coverage

5.2.1. QA effort diagram

5.3. Test types

5.3.1. Smoke testing

5.3.2. Regression testing

5.3.3. Functional testing

5.3.4. GUI/Usability testing

5.3.5. Localization testing

5.3.6. Compatibility testing

5.3.7. Synchronization testing

5.3.8. Performance testing

6. QA efforts workflow

6.1. Collection, analyzing and clarifying info about project and project requirements

6.2. Functional requirements analysis

6.3. Test planning

6.4. Test design

6.5. Maintenance of designed test

6.6. Test data preparation

6.7. Test execution

6.8. Defect tracking

6.9. Restes

6.10. Test status reporting

6.11. Attending project meetings

6.12. Documentation review

7. Test design

8. Test execution

8.1. Test status reporting

8.2. Defect tracking

8.3. Test environment

8.3.1. Internet Explorer (9+)

8.3.2. Google Chrome

8.3.3. Mozilla Firefox

8.3.4. Opera

8.3.5. Apple Safari

8.4. Testing tools

8.4.1. TSF - Defect tracking and task management tool

8.4.2. MS Excel, Goole docs - for storing QA documentation

8.5. Entrance criteria

8.5.1. Smoke testing is passed successfully

8.5.2. Test environments are ready

8.5.3. QA resources has enough functional knowledge

8.5.4. All tools defined in Testing tools section are configured and available to QA team

8.6. Pass/fail criteria

8.6.1. Fail criteria

8.6.1.1. FUT does not work on platform, which is described in the Environment section

8.6.1.2. FUT does not operate according to a stated requirement

8.6.1.3. FUT operates in a way that will create a peception of low quality, even if stated reqyirements were met

8.6.1.4. FUT does not work properly with another one that is supposed to to be cmpatible

8.7. Exit/Acceptance criteria

9. Test deliverables

9.1. Test plan

9.2. Test design specification

9.3. Defect entered in the defect tracking tool

9.4. QA status report

9.5. Test summary report

10. Roles and responsibilities

10.1. QA Lead

10.1.1. Analysis of business logic

10.1.2. Requirements analysis

10.1.3. Test planning

10.1.4. Test design

10.1.5. Test estimation

10.1.6. Testing

10.1.7. Defect tracking

10.1.8. Test results analysis and reporting

10.1.9. Daily meetings

10.1.10. Reporting

10.1.11. Assigned QA(s): Maryna Smirnova

10.2. QA Engineer

10.2.1. Requirements analysis

10.2.2. Test design

10.2.3. Testing

10.2.4. Defect tracking

10.2.5. Test result analysis and reporting

10.2.6. Daily meetings

10.2.7. Assigned QA(s): Iryna Batiuk

11. Risk management

11.1. See attached table