adv2 touch test design document

8/14/2019 AdV2 Touch Test Design Document

1/169


2/169

2

Table of ContentsIntroduction ........................................................................................................................................................ 3

Purpose of this document .............................................................................................................................. 3

Test Objective ................................................................................................................................................. 3

Work Distribution ........................................................................................................................................... 3

Schedule ......................................................................................................................................................... 3

Detail Test Strategy ............................................................................................................................................ 5

System Level Function Testing ....................................................................................................................... 5

Category Partitioning Testing ......................................................................................................................... 5

Advertisement ................................................................................................................................................ 6

Account ........................................................................................................................................................... 9

Schedule ....................................................................................................................................................... 11Test cases for Advertisement: ...................................................................................................................... 17

Account ......................................................................................................................................................... 52

Schedule ..................................................................................................................................................... 129

Boundary Value Analysis ............................................................................................................................ 158

Decision Table Testing ................................................................................................................................ 158

System Performance Testing .......................................................................................................................... 160

System Process Speed ................................................................................................................................ 160

Test Cases: .................................................................................................................................................. 161

Automation System Performance Testing ..................................................................................................... 169


3/169

3

IntroductionPurpose of this documentThe whole purpose for this document is to define a detailed view of the testing strategy of Ad-Touch V2System, mentioning the details of the testing methodology used for testing. We listed all the test cases tobe performed, information of the testers assigned to the test cases, pre-conditions for executing the testcases, test data required to execute the cases and additional information required to perform the testcases.

Test ObjectiveThe objective of this document is to provide elaborate information of the test plan required for executingthe test cases. This kind of detailed information reduces confusion for the testers while performing thetesting of the application and enhances the test coverage criteria. This document provides detailinformation about the work distribution among the team, tasks assignments and addition information

required for the tester in performing the test cases. The testing method is black box testing, all the testresults are logged in and bug report will be generated accordingly.

Work DistributionS. No. Team Member Role1. Nikhil Verma Team Lead, Test Engineer2. Pallavi Keskar Test Engineer3. Jasdeep Singh Aneja Test Engineer4. Rahul Akurati Performance Test Automation

Engineer

ScheduleNo. Members Responsibilities Duration Start time Finish time

1. Nikhil, Pallavi, Project overview 1 day 10/12/2013 10/13/2013 Jasdeep, Rahul

2. Nikhil, Pallavi, Review test plan and 3 days 10/15/2013 10/17/2013 Jasdeep, Rahul analyze test strategies

and methods 3. Jasdeep Design test case for 5 days 10/18/2013 10/22/2013

Advertisement component using black box testing methods

4. Pallavi Design test case for 5 days 10/18/2013 10/22/2013 Account component using black box testing methods

5. Rahul, Nikhil Design test case for 5 days 10/18/2013 10/22/2013 Schedule component


4/169

4

using black box testing methods

6. Nikhil, Pallavi, Design test cases for 4days 10/23/2013 10/27/2013 Jasdeep, Rahul system process speed

7. Nikhil, Pallavi, Design test cases for 3 days 10/24/2013 10/27/2013

Jasdeep, Rahul automation system and performance testing. 8. Nikhil, Pallavi, Review and submission 1 days 10/27/2013 10/28/2013

Jasdeep, Rahul for test design document


5/169

5

Detail Test StrategySystem Level Function TestingThe system level functional testing procedure requires black box testing techniques for AdTouchV5 system. The system is deployed on a VM and needs remote access if source code is not

installed. The components tested are Advertisement, Account and Schedule based on thespecifications and requirement. The process works heavily on discovering system level errors,issues with the system interface and functional errors. The Black Box testing methods used areCategory partition, boundary value analysis and decision table testing.

Category-partition testing: Advertisement, Schedule and Account features includenumerous sub-components. Each sub-component will be partitioned into its own category andtested.

Decision-table based testing: Depending on what type of user is currently logged in thefeatures - Advertisement, Schedule and Account of AdTouch responds differently. Decision-tablebased test cases are generated to test the restrains and also activity of a particular type of user asdefined in the requirement specification.

Category Partitioning TestingCriteria: The 3 features of the AdTouch Mobile Advertising System has many sub-componentsthat have to be tested. Each sub-component will be partitioned into specific categories toperform testing. The following steps need to be performed:

Divide features - Advertisement, Schedule, and Accounts into various functional units

Recognize test inputs and the environment conditions

Make up the categories.

Divide each category into specific choices

Write a test specification for every unit

Produce test cases


6/169

6

AdvertisementADVERTISEMENTTest CaseID

FunctionalityTo Be

Tested

Field to betested

Description Input Expected Output

Ad1.1 Add AdvertisementID

Test valid 987654 Pass - checkavailable


Testduplicated

987654 Not available


Test empty NO ID entered -empty box

Error in availabilitycheck

Ad1.4 Add Product Test empty Empty input Fail to add adsAd1.5 Add Product Test length ProductTest Type: Category-Partition

Priority: High Tester Name: Rahul Akurati Date: Oct 27, 2013Precondition:Account advertiser has been logged in

Description: Add function of Advertisement->Product featureSpecification

Input Expected Output ResultAd Id#: a11Product: a11Ad Type: ClassifiedAd Class: BarcodeAd Link through URL:

www.google.comAd Content key: a11Ad content text: a11

Click Add Product and notedown the system response timefor each run.Assign run=1 if success and run-0 on failure

Run1: 1Run2: 1Run3: 1Run4: 1Run5: 1Run6: 1Run7: 1Run8: 1Run9: 1Run10: 1Success rate(success/total):

Test Procedure1. Fill in all fields as input2. Click create product3. Redo step 1 and 2 with ad id#: a12,a13,a14,a15, a16, a17, a18, a19, a10 keeping all other

fields as same4. Compare with the expected output


164/169

164

Test CaseTest Case# A.1.4 Test Item: Search function of

the productTest Type: Category-Partition

Priority: High Tester Name: Rahul Akurati Date: Oct 27, 2013Precondition:Account advertiser has been logged inA.1.3 should be pass

Description: Search function of Product featureSpecification

Input Expected Output ResultAd Id#: a11Product: a11Ad Type: ClassifiedAd Class: Barcode

Ad Status: InactiveAd Approval Status: Pending

Click Search and note downthe system response time foreach run.Assign run=1 if success and run-

0 on failureRun1: 1Run2: 1Run3: 1Run4: 1Run5: 1Run6: 1Run7: 1Run8: 1Run9: 1Run10: 1

Success rate(success/total):Test Procedure1. Fill in all fields as input2. Click search product3. Redo step 1 and 2 with ad id#: a12,a13,a14,a15, a16, a17, a18, a19, a10 keeping all other



165/169

165

Test CaseTest Case# B.1.1 Test Item: Add function of the

reservationTest Type: Category-Partition

Priority: High Tester Name: Rahul Akurati Date: Oct 27, 2013Precondition:Account advertiser has been logged in

Description: Add function of reservation featureSpecification

Input Expected Output ResultAd Id#: a11Product: a11Ad Type: ClassifiedAd Class: BarcodeAd Link through URL:

www.google.comAd Content key: a11Ad content text: a11

Click Add Reservation and notedown the system response timefor each run.Assign run=1 if success and run-0 on failure


Test Procedure5. Fill in all fields as input6. Click create reservation7. Redo step 1 and 2 with ad id#: a12,a13,a14,a15, a16, a17, a18, a19, a10 keeping all other



166/169

166

Test CaseTest Case# B.1.2 Test Item: Search function of

the reservationTest Type: Category-Partition

Priority: High Tester Name: Rahul Akurati Date: Oct 27, 2013Precondition:Account advertiser has been logged inB.1.1 should be pass

Description: Search function of Advertisement featureSpecification

Input Expected Output ResultAd Id#: a11Product: a11Ad Type: ClassifiedAd Class: Barcode

Ad Status: InactiveAd Approval Status: Pending

Click Search and note downthe system response time foreach run.Assign run=1 if success and run-

0 on failureRun1: 1Run2: 1Run3: 1Run4: 1Run5: 1Run6: 1Run7: 1Run8: 1Run9: 1Run10: 1

Success rate(success/total):Test Procedure5. Fill in all fields as input6. Click search reservation7. Redo step 1 and 2 with ad id#: a12,a13,a14,a15, a16, a17, a18, a19, a10 keeping all other



167/169

167

Test CaseTest Case# C.1.1 Test Item: Add function of the

userTest Type: Category-Partition

Priority: High Tester Name: Rahul Akurati Date: Oct 27, 2013Precondition:Account admin has been logged in

Description: Add function of user featureSpecification

Input Expected Output ResultUser Id#: u11 Click Add User and note down

the system response time foreach run.Assign run=1 if success and run-0 on failure


Test Procedure9. Fill in all fields as input10. Click create user11. Redo step 1 and 2 with ad id#: a12,a13,a14,a15, a16, a17, a18, a19, a10 keeping all other



168/169


169/169

Automation System Performance TestingOur automation involves creation of scripts for performance testing and executing those for capturingthe system performance.

Criteria: Automating system performance tests reduces the manual testing activities thereby achieving

redundancy in test operations and achieve better test coverage. We have chosen Selenium IDE as thetest tool using C# for coding the scripts which helps in auto-run to test the system performance.

adv2 touch test design document

Documents