RECRUIT TEST PLAN

Iniziamo. È gratuito!
o registrati con il tuo indirizzo email
RECRUIT TEST PLAN da Mind Map: RECRUIT  TEST PLAN

1. TEST STRATEGY

1.1. Test levels

1.1.1. Integration testing

1.1.1.1. We test a single working product, we do not test the modules separately

1.1.2. System testing

1.1.2.1. We test compatibility to all supported platforms, os, browsers, devices

1.2. Test types

1.2.1. Functional

1.2.1.1. Functional testing

1.2.1.1.1. We test functionality according to specification

1.2.1.2. Security testing

1.2.2. Non-functional

1.2.2.1. Performance testing

1.2.2.1.1. Stability / Reliability Testing

1.2.2.1.2. Stress testing

1.2.2.2. Usability testing

1.2.2.2.1. We need select and engage a target users (or group of people) for testing

2. FEATURES TO BE TESTED

2.1. This is a listing of what is to be tested from the users viewpoint of what the system does

3. TARGET ENVIRONMENTS

3.1. The list will be updated after analyzing the statistics

3.1.1. Web app

3.1.1.1. Mobile

3.1.1.1.1. Android (4.4/5.1/6.0/7.1)

3.1.1.1.2. iOS (9.3.5/10.3.2)

3.1.1.2. Desktop

3.1.1.2.1. Windows 8/10

3.1.1.2.2. OSX (Sierra)

3.1.2. Mob app

3.1.2.1. Android (4.4/5.1/6.0/7.1)

3.1.2.1.1. Samsung S4 (mini)

3.1.2.1.2. Lenovo Pad 8"

3.1.2.2. iOS (9.3.5/10.3.2)

3.1.2.2.1. iPhone 6(s)

3.1.2.2.2. iPhone 5(s)

3.1.2.2.3. iPad Air

4. FEATURES NOT TO BE TESTED

4.1. Some feature is not to be tested, there can be any number of reasons.

5. OBJECTIVES

5.1. Retest the whole product on all supported platforms using functional and non-functional testing approaches

6. TOOLS

6.1. Bug reporting

6.1.1. Jira

6.1.1.1. RECRUIT project

6.1.1.1.1. Bug issue with a specific label

6.2. Test Management

6.2.1. Xray (Jira)

6.2.1.1. Test Plan, Checklists, Tests cases, Test Executions

6.3. Test tools

6.3.1. Internet browser

6.3.2. Real devices (not simulators , not emulators)

6.3.3. Firebug console

6.3.4. Video recorder and screenshoter

6.3.5. JMeter

6.3.6. Selenium IDE/Selenium Builder

6.3.7. UI/Application Exerciser Monkey

7. DELIVERABLES

7.1. Bugs

7.1.1. functional

7.1.1.1. blocked

7.1.1.2. critical

7.1.1.3. major

7.1.1.4. minor

7.1.1.5. trivial

7.1.2. user interface

7.1.3. system

7.1.3.1. non visible for users

7.2. Checklists

7.2.1. Smoke testing (critical features)

7.2.2. Regression testing

7.2.2.1. of whole product

7.2.2.2. of a spesific feature

7.3. Test cases

7.3.1. Critical features

7.3.2. All features

7.4. Use cases

7.4.1. Most usable user flow on a site (in app)

7.5. Suggestions for improvements