Software Test Life Cycle

Software Test Life Cycle / Software Test Process

Manual Test Process together with Automated Test Process (using UFT/QTP together with Selenium).

Software Test Process or Software Test Life Cycle may vary from One compay to about other together with 1 projection to another, but what I am going to explicate is Industry Standard process. Some companies may non follow formal procedure due to lack of documentation together with Time etc...

I) Software Test Process (Manual Testing)

Four Important phases of Software Test Life Cycle or Software Test Process,

i) Test Planning

ii) Test Design

iii) Test Execution

iv) Test Closure
-----------------------------------------------------------
i) Test Planning

Roles:

1) Test Lead / Team Lead / Test Manager - Test Planing together with Guidence to Team Members

2) Testers / Team Members - Contribution to Test Plan

a) Input or Reference Documents for Test Planning Phase

Test Requirements,
Project Plan,
Test Strategy,
-------------------
Design Documents
Corporate Standard documents etc...

b) Tasks

1) Understanding together with Analyzing Test Requirements
2) Risk Analysis
3) Test Strategy Implementation
4) Test Estimations (Scope, Time, Resources, Budget etc...)
5) Team Formation
6) Test Plan Documentation
7) Configuration Management Planning
8) Traceability Matrix documentation
9) Define Test Environment Setup

c) Output

Test Plan Document
---------------------------------------------
ii) Test Design

Roles:

Test Lead - Guidance, Monitoring together with Control the Test Process.

Testers - Test Case Documentation together with Test Data Collection

a) Input or Reference Documents for Software Test Design Phase

Test Requirements
Test Plan Document
----------------------
Test Case Template 
-----------------------
Design docs
Process guidelines docs
Corporate Standards docs

b) Important Tasks inward Test Design Phase

1) Understanding Test Requirements
2) Generate Test Scenarios
3) Test Case Documentation
4) Test Data Collection

c) Output

Test Case documents

Test Data
-------------------------------------------------------
iii) Test Execution

a) Input or Reference Documents for Software Test Execution Phase

Test Requirements
Test Plan document
Test Case docs
Test Data
--------------------
Defect Report Template
----------------------
Readiness of AUT (Application Under Test)
Readiness of Test Environment (Test Lab)

b) Important Tasks inward Test Execution Phase

1) Verify Test Environment Setup

2) Create Test Batches
3) Test Execution
Smoke Testing
Comprehensive Testing 
Reporting Defects
Tracking Defects
Re & Regression Testing Cycle 1
Sanity Testing
Execute Regression Test Cases
Reporting Defects
Tracking defects
Re & Regression Testing Cycle 2
Sanity Testing
Execute Regression Test Cases
Reporting Defects
Tracking Defects
.
.
.
Final Regression
-----------------------------------
c) Output

Opened together with Closed Defect Reports

Tested Software
-----------------------------------------------

iv) Test Closure

a) Input or Reference Documents for Software Test Closure Phase

Test Requirements

Traceability Matrix document

Test Plan Document

Opened together with Closed Defect Reports

------------------------------

Test Summary Report Template

----------------------------

b) Important Tasks inward Test Execution Phase

1) Evaluating Exit Criteria

2) Collect all documents together with ready Test Summary Report.

3) Send Test deliverables to Customer.

4) Improvement suggestions for futurity projects.

-----------------------------------------------------
II) Selenium Test Process

Five Important Phases inward Selenium Test Process

i) Planning

ii) Generate Basic Test Cases

iii) Enhance Test Cases

iv) Running together with Debugging Test Cases

v) Analyzing Test Results & Reporting Defects
-----------------------------------------------------------
i) Test Planning

• Get Application Environment (UI blueprint together with Database) details from Development Team.

• Analyze the AUT (Application Under Test) inward price of Object Identification.

         Using Recording characteristic inward Selenium IDE
         Using Element Inspectors nosotros tin forcefulness out inspect elements. (Page Inspector inward                Mozilla Firefox, IE or Google Chrome -Developer tools)

• Select Test cases for Automation

1) Test cases that nosotros convey to execute on Every ready (Sanity Tests)
2) Test cases that nosotros convey to execute on every modified build(Regression               Tests)
3) Test cases that nosotros convey to execute using multiple sets of Test information                     (Data Driven Tests)

•  Choose Selenium Tools together with Setup Selenium Test Environment.

Ex: Select Selenium Tool (Selenium WebDriver), programming linguistic communication (Java) together with Testing Framework(TestNG) etc...
-------------------------------------------------------------
ii) Generating Basic Tests

If y'all select Selenium IDE:
a) Using Recording
b) Type Test steps using Element locators together with Selenese Commands.

If y'all select Selenium WebDriver
Using Element locators together with Webdriver Methods/commands
------------------------
iii) Enhancing Tests

1) Inserting Verification points

Selenium IDE:
Using Assert/Verify Commands

Selenium WebDriver
a) Using Java Conditional Statements 
b) Using JUnit or TestNG Framework Assertion methods.

2) Parameterization

Selenium IDE:
Selenium IDE doesn't back upwards Parameterization.

Selenium WebDriver
By importing External files (Test data) nosotros tin forcefulness out Parameterize Test cases.

3) Synchronization

In Selenium IDE: Increase default Synchronization Time

In Selenium WebDriver:  Use Java Thread.sleep or WebDriver implicitlyWait command.

4) Error Handling

Handling expected together with unexpected errors.

5) Adding Comments (Optional)

Etc...
-------------------------------------------------
iv) Running together with Debugging Test Cases

Running /Executing Test cases (Mandatory)

Types of Test Run

Single Test Run

Test Batch Run
Using Testing Framework (JUnit/TestNG) nosotros tin forcefulness out deport Batch testing
-----------------------
Debugging Test Cases (Optional) 

When Debugging is Required?

Scenario 1: Test illustration is non showing whatever errors together with providing right output/result - Debugging is non required.

Scenario 2: Test illustration is showing errors - Debugging is Optional.

Scenario 3: Test illustration is non showing whatever errors together with Not providing right output/result - Debugging is required.
---------------------------------------------------
v) Analyzing Test Results together with Reporting Defects

Analyzing Test Results

• Selenium IDE provides exam effect (Summary only) for every Test illustration iteration.

• Selenium WebDriver doesn't convey Reporting facility.

• Using either JUnit or TestNG nosotros tin forcefulness out generate Test Reports.
--------------------------------------------------
Status of Test results inward Functional Test Automation

1) Pass (if Expected = Actual)

2) Fail (if Expected Not equals Actual)

3) Done (if in that place are no verification points  in a Test Case)

4) Warning (if whatever intermission during exam execution)
----------------------------------------------------------
Reporting Defects

Selenium doesn't integrate alongside other tools for Test management/Defect management. After analyzing the Test Results, if y'all abide by whatever departure from expected thence Report Defects using your fellowship Defect Management System.
-----------------------------------------------------------------------
Note:

In Selenium Testing (Test Automation using Selenium) focus on,

1) Selenium WebDriver to Create Test Cases using Element Locators together with WebDriver API Commands.

2) Java Programming to Enhance Test Cases

3) TestNG Framework to grouping Test Cases, prioritize Test Cases, execute Test Batches together with generate Test Reports.
-----------------------------------------------------------------------

III) UFT / QTP Test Process

Five Important stage inward UFT Test Process

i) Planning

ii) Generate Basic Tests

iii) Enhance Tests

iv) Running together with Debugging Tests

v) Analyzing Test Results & Reporting Defects
--------------------------------------------------------------

i) Test Planning

1) Get Environment (UI Design Technology together with Database)Details from Development Team together with select appropriate Add ins

2) Analyze the AUT inward price of Object Identification

3) Select areas / Test cases for Automation
        a) Tests that nosotros convey to execute on every ready (Sanity Tests)
        b) Tests that nosotros convey to execute on every modified ready (Regression Tests)
        c) Tests that nosotros convey to execute using multiple sets of Test Data (Data Driven Tests)

4) Tool settings Configuration together with Globalize

5) Automation Framework Implementation (Optional)

ii) Generate Basic Tests

In ii ways nosotros tin forcefulness out exercise Tests inward UFT (formerly QTP)

1) Object Repository based Test Design
    a) Recording
    b) Keyword Driven Methodology

2) Descriptive Programming / Programmatic Descriptions
    a) Static Programming
    b) Dynamic Programming

iii) Enhance Tests

We convey several methods for Enhancing Tests, about methods belong to UFT together with Some methods belong VBScript. You tin forcefulness out utilisation both UFT Tool features together with VBScript features to heighten Tests.

1) Inserting Checkpoints 

2) Inserting Output Values

3) Parameterization

4) Adding Comments (Optional)

5) Inserting Transaction Points 

6) Synchronization

7) Define Test Result

8) Calling Actions, Functions (Reusable Components)

9) Inserting Flow Control Statements

10) Error Handling Etc...
------------------------------------------------------
iv) Running together with Debugging Tests

• We tin forcefulness out Debugging UFT / QTP Tests using VBScript Debug commands together with Breakpoints.

• We tin forcefulness out Run Single Test together with Test Batches (Series of Tests).

---------------------------------------------------

v) Analyzing Test Result & Reporting Defects

• UFT provides Test Result for every Test iteration together with nosotros tin forcefulness out Defined Test Result using Reporter utility object.

Note: Generally UFT tool provides exam effect for every exam iteration if nosotros utilisation UFT Tool features similar Checkpoints, Transaction points, Synchronization point, Out seat values etc…, if nosotros utilisation our ain logic similar Conditional statements, loop statements user defined functions etc… thence nosotros demand to define Test Result.

Status of Test Result:

(UFT supports iv types of Status for Test Result)

        1) Pass (If expected = Actual thence Pass)

        2) Fail (If facial expression <> Actual thence Fail)

        3) Done (If in that place is no verification point, alone manifestly execution thence Done                 status)

        4) Warning (Problems during exam execution thence Warning status)

Reporting Defects

• After analyzing the Test Results, if y'all abide by whatever departure from expected thence Report Defects using your fellowship Defect Management System.

• If nosotros integrate UFT alongside ALM thence nosotros tin forcefulness out post Defects guide cast UFT Result window to ALM Project.

------------------------------------------------------------

Sumber http://www.gcreddy.com/