0% found this document useful (0 votes)
65 views

Orthogonal Array Testing Strategy

The document discusses orthogonal array testing (OAT), a technique for testing all factor interactions using fewer test cases than exhaustive testing. It compares OAT to exhaustive testing, outlines the steps to create an orthogonal array, and provides an example of using OAT for a reimbursement claim module. Key advantages of OAT are that it allows for pairwise testing using fewer test cases, lower cost and higher efficiency compared to exhaustive testing.

Uploaded by

apareek3
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
65 views

Orthogonal Array Testing Strategy

The document discusses orthogonal array testing (OAT), a technique for testing all factor interactions using fewer test cases than exhaustive testing. It compares OAT to exhaustive testing, outlines the steps to create an orthogonal array, and provides an example of using OAT for a reimbursement claim module. Key advantages of OAT are that it allows for pairwise testing using fewer test cases, lower cost and higher efficiency compared to exhaustive testing.

Uploaded by

apareek3
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 30

Orthogonal Array Testing

Strategy

NFT-Business Process Re-Engineering


Exhaustive Vs OATS
 Exhaustive/Non  OATS
Exhaustive 

Testing ü Pair Wise Testing using OA


Ø concept
Ø Testing based on P & C ü Fewer TC’s
Ø Redundant TC’s ü Low Cost – High efficiency
Ø High Cost - Low efficiency ü Higher Bugs/Test Case
Ø Lower Bug s per TC’s ü
Analyze Functionality and

then create Test cases
 Create TC’s and then analyze
functionality
OATS
 Interactions and
integrations are a major
source of defects.

 Statistical way of testing


pair-wise interactions.

 Maximum coverage with


minimum combinations.
OA
Two Dimensional arrays of numbers.

 OA’s are commonly represented as :


 LRuns (LevelsFactors )

 Where,
 Runs – Number of rows in the array, which translates into the
number of test Cases that will be generated.
 Factors – Number of columns in the array, which translates
into the maximum number of variables that can be handled
by the array.
 Levels – Maximum number of values that can be taken on by
any single factor.
Steps to OA creation :-

Ø
ØStep 1 :
1. Decide the independent variables to be included.
2. Independent variables map to factors of the array.
3.

ØStep 2 :
1. Decide the maximum number of values each independent variable takes.
2. Value map to the Array

ØStep 3
1. From the Orthogonal Array Selector, find a suitable Orthogonal Array with the
smallest number of Runs. ( Suitable array is one that has at least as many
factors (from Step 1) and as many levels (from Step 2).
2. Map the factors and levels onto the standard array.
3. Transcribe the Runs into test cases.
4.

ØStep 4
1. Add or remove any particularly suspicious combinations that aren’t generated.
i.
Orthogonal Array Selector

url: -

http://www2.research.att.com/~njas/oadir/index.html
http://www2.research.att.com/~njas/doc/cent4.html

http://www.york.ac.uk/depts/maths/tables/orthogonal.htm


General Example
 Exhaustive Testing  OAT
 4 Variable. (4 Text Box)
 3 Values. (Each text box can
 OA (4,3) – L9(3^4)
take values between 1-3) 


 The exhaustive test set would 

require 81 test cases (3 * 3 * 

3 * 3). 

 



Mapping OA
 Important Notes

 Note 1
 The array selector assumes that each parameter has the
same number of levels. Sometimes this is not the case.
Generally, the highest value will be taken or the
difference will be split.

 Note 2
 If the array selected based on the number of parameters
and levels includes more parameters than are used in the
experimental design, ignore the additional parameter
columns.
Reimbursement Claim Module
Steps to use an OA with an Example

Step 1: Decide Number of Factor to be studied


Step 2: Decide Number of levels for each factor
8 TC without considering
 Actual No. of TCs

Login and Logout applicable


 Limitations  Mistakes to Avoid
 

 Array are difficult to construct  Applying OATS manually .


 In context of software testing,  Focusing the testing effort on
OA can be wasteful because the wrong area of the
each pair of inputs must application.
occur exactly the same  Using OATS for minimal testing
number of times. efforts
 OA is that it can only be  Using OATS for high risk
applied at the initial stage of application
the product/process design  Picking the wrong parameters
system to combine
 OA techniques are not
applicable where a
processes involving
influencing factors vary in
time.
 Parameter 1 :- Stage – 3 Level
(Pre Load , Validate , Load)

 Parameter 2 :- Select Event –
Level 2 (Post , Prior)
 Parameter 3 :- Script – Valid ,
Invalid

 Factors :- 3,Levels :- 3 ,OA :- L9

This matrix will not give proper execution results
OA 2 –Matrix also does not provide proper TC’s expected

 Preload – 2(Prior,Post)
 Validate - 2(Prior,Post)
 Load - 2(Prior,Post)
 Script - 2(Prior,Post)

 2^4 - L8
Runs Preload Validate Load Script
1 Prior Prior Prior Invalid
Prior Post Prior Valid
2
Prior Prior Post Valid
3
Prior Post Post Valid
4
Post Prior Post Valid
5
Post Post Prior Valid
6
Post Prior Post Valid
7
Post Post Prior Valid
8
9 Post Post Prior Valid
10 Post Post Post Invalid
OA 3 (Parameter 7 ; Level 2)
Runs Preload/Prior Preload/Post Validate/Prior Validate/Post Load/Prior Load/Post Script

1 No Run No Run No Run No Run No Run No Run Valid

2 No Run No Run No Run Run Run Run Valid

3 No Run Run Run No Run No Run Run Valid

4 No Run Run Run Run Run No Run Valid

5 Run No Run Run No Run Run No Run Valid

6 Run No Run Run Run No Run Run Valid

7 Run Run No Run No Run Run Run Valid

8 Run Run No Run Run No Run No Run Valid

9 Run Run Run Run Run Run Valid

10 No Run No Run No Run No Run No Run No Run Invalid


THANK YOU
LBMT – Lorenzo Blob migration tool

 Extract the configured BLOB data.


 Transform BLOB data by invoking the
corresponding LORENZO API.
 Update BLOB data into the database.

èIntegration between
I xtract I TransformI
èIetween Transform and
I nvoI e I I I .
èTransform and Update.
LBMT – Configuration
Configuration Parameters

Blob Configuration Tables 7


Col Data Type 2
API Details 1
Extraction
Extract Data from R2 DB.
Correct Details / Incorrect
API Replace Old FK-OID with New OID.

Correct/Incorrect.
Update Data to be updated.
Methods/ Classes Used in LBMT
Extraction Transformation Update Mode

Initialize GetAPIName() Read Data New Restart

Validate Input InvokeAPI Update Data ()


Extract Transform
Extract Data () Save Data Write Log ()

Save Data: Write Log ()


Transform Update
Write Log ()
Update
Update/
Update/ Load
Load
LBMT – UI Layout
LBMT - Parameters
Layout Tables Col Data Mode Stages
Type
UI 7 2 New Extract
Transform
Update
UI 7 2 Restart Transform
Update/Load
Update
Console 7 2 New Update/Load
Extract
Transform
Console 7 2 Restart Update
Transform
Update/Load
Update
Update/Load
S. No. Factors Levels

1 Extraction Initialize Validate Input Extract Data ()


Binary Text
Save Data Write Log ()

0 1 2 3 4 5

2 Transformation GetAPIName() InvokeAPI Write Log () PB:-

In the new mode Extract ,


Transform and Update is
0 1 2
possible while in Restart
mode only Transform and
Update can be done.

3 Update Read Data Update Data Write Log

0 1 2

LX [3^2 6^1] I 3^6 6^1 n=18


New
Mode
Restart

Logic http://people.sc.fsu.edu/~burkardt/datasets/oa/oa.html
http://www2.research.att.com/~njas/doc/cent4.html
http://support.sas.com/techsup/technote/ts723_Designs.txt
http://www.dotnetspider.com/resources/24806-Orthogonal-Array-for-Testing.aspx
0 0 0 0 0 0
1
1 0 1 1 2 2
2
2 1 0 2 2 1
3
3 1 2 0 1 2
4
4 2 1 2 1 0
5
5 2 2 1 0 1
6
5 0 0 2 1 2
7
4 0 2 0 2 1
8
0 1 1 1 1 1
9
1 1 2 2 0 0
10
3 2 0 1 2 0
11
2 2 1 0 0 2
12
3 0 1 2 0 1
13
14
2 0 2 1 1 0
L18
4 1 0 1 0 2
15
5 1 1 0 2 0
16
1 2 0 0 1 1
17
0 2 2 2 2 2
18
S. No. Factors Levels
Single Multiple All
1 Tables
0 1 2

4 Restart Transform

Update

Matrix L9 [3^4]
S.No Select TablesData Type Stage
A A A
1
A 1 2
2
A 2 1
3
1 A 2
4
1 1 1
5
1 2 A
6
2 A 1
7
2 1 A
8
2 2 2
9

You might also like