user's manual

XQual Cidex 436, chemin des tourres . 6330 Roquefort les pins .France

User’s Manual V1.2

Table of content

1. OBJECTIVES

2. GENERAL OVERVIEW

3. BASICS

3.1 U

3.1.1

3.1.2

3.1.3

3.1.4

3.1.5

3.1.6

3.1.7

3.2 SUT

3.2.1

3.2.2

3.3 A

3.3.1

3.3.2

3.4 R

3.4.1

3.4.2

3.4.3

3.5 S

3.5.1

3.5.2

3.6 P

3.6.1

3.6.2

3.6.3

3.6.4

3.6.5

3.6.6

3.6.7

3.6.8

3.7 T

3.7.1

3.7.2

3.7.3

3.7.4

3.8 C

3.8.1

3.8.2

3.8.3

3.8.4

3.8.5

3.8.6

3.8.7

3.9 D

3.9.1

3.9.2

Table of content

OBJECTIVES ................................

GENERAL OVERVIEW

BASICS................................

USER TREE ................................

CREATE A COMPANY

CREATE A HIERARCHY IN

CREATE A USER

SUBMIT A NEW ABSENCE

EDIT AN ABSENCE

CHECK THE CALENDARS

CHANGING ADMIN PASSWO

SUT TREE ................................

CREATE A SUT CREATE A SUT

AGENT TREE ................................

ADD MY LOCAL HOST

ADD ALL NECESSARY HOS

REQUIREMENT T

CREATE A CATEGORY

CREATE A REQUIREMENT

EDIT A REQUIREMENT

SPECIFICATION

CREATE A SPECIFICATIO

EDIT A SPECIFICATION

PROJECT TREE

CREATE A PROJECT

CREATE A TASK

CREATE A SPRINT

EDIT A SPRINT

ALLOCATE SOME RESOURC

ASSOCIATE SOME TASKS TO

DAILY UPDATE PROGRESS

SEE THE VELOCITY CHAR

TEST TREE ................................

CREATE A TEST

ASSOCIATE A TEST TO S

CREATE A TESTCASE

MOFIFY THE TESTPLAN O

CAMPAIGN TREE

CREATE A CAMPAIGN

ORDER THE TESTS IN TH

CREATE A CAMPAIGN SES

RUN A CAMPAIGN SESSIO

SEE THE EXECUTION DET

GET THE RESULTS

CHECK THE PROGRESSION

DEFECT TREE ................................

CREATE A DEFECT

EDIT A DEFECT

Table of content

................................

GENERAL OVERVIEW ................................

................................

................................

REATE A COMPANY ................................REATE A HIERARCHY IN THE COMPANY

REATE A USER ................................UBMIT A NEW ABSENCE ................................DIT AN ABSENCE ................................HECK THE CALENDARS ................................HANGING ADMIN PASSWO

................................

SUT ................................SUT INHERITING REQUIREMEN

................................

DD MY LOCAL HOST ................................DD ALL NECESSARY HOSTS

TREE ................................

REATE A CATEGORY ................................REATE A REQUIREMENT ................................DIT A REQUIREMENT ................................

PECIFICATION TREE ................................

REATE A SPECIFICATION ................................DIT A SPECIFICATION................................

REE ................................

REATE A PROJECT ................................REATE A TASK ................................REATE A SPRINT ................................DIT A SPRINT ................................LLOCATE SOME RESOURC

CIATE SOME TASKS TO

AILY UPDATE PROGRESS

EE THE VELOCITY CHARTS

................................

REATE A TEST ................................SSOCIATE A TEST TO SPECIFICATIONS

REATE A TESTCASE ................................OFIFY THE TESTPLAN OF

REE ................................

REATE A CAMPAIGN ................................RDER THE TESTS IN THE CAMPAIGN

REATE A CAMPAIGN SESSION

UN A CAMPAIGN SESSION

EE THE EXECUTION DETAILS

ET THE RESULTS ................................HECK THE PROGRESSION

................................

REATE A DEFECT ................................DIT A DEFECT ................................

................................................................

................................

................................................................

................................................................

................................THE COMPANY ................................

................................................................................................

................................................................................................

HANGING ADMIN PASSWORD ................................

................................................................

................................................................NHERITING REQUIREMEN

................................................................

................................TS ................................

................................

................................................................

................................

................................

................................................................

................................................................

................................................................................................

................................................................................................................................

LLOCATE SOME RESOURCES TO A SPRINT

CIATE SOME TASKS TO A SPRINT ................................ OF THE TASKS OF A SP

TS/CHECK THE STATUS OF

................................................................

................................................................PECIFICATIONS ................................

................................ A TESTCASE ................................

................................................................

................................E CAMPAIGN ................................

SION ................................N ................................AILS ................................

................................HECK THE PROGRESSION OF A CAMPAIGN

................................................................

................................................................................................

................................

................................................................

................................................................

................................................................

................................................................................................

................................................................................................

................................................................................................

................................................................

................................................................

................................NHERITING REQUIREMENTS FROM ANOTHER

................................

................................................................................................................................

................................................................

................................................................................................................................

................................................................

................................................................

................................................................................................................................

................................

................................................................................................

................................................................

ES TO A SPRINT ................................................................

OF THE TASKS OF A SPRINT ................................CHECK THE STATUS OF THE SPRINT

................................................................

................................................................

................................................................................................

................................

................................................................................................

................................................................................................................................

................................................................................................................................

A CAMPAIGN ................................

................................

................................................................................................

................................................................

................................

................................

................................

................................................................................................................................

................................................................................................

................................................................................................................................

................................

................................

................................................................TS FROM ANOTHER SUT ................................

................................................................

................................................................................................

................................................................

................................................................................................

................................................................

................................................................

................................................................................................

................................................................

................................................................................................................................

................................................................................................................................

................................................................................................................................

................................THE SPRINT ................................

................................

................................................................................................................................

................................................................................................................................

................................................................

................................................................................................................................

................................................................

................................................................................................

................................................................

................................................................

................................................................................................................................

................................

........................................................

...............................................

........................................................

................................................................

...............................................................................................

................................................................

........................................................

.......................................................

............................................................................

...................................................

..........................................................................................

................................

..............................................................................................

................................

................................

.............................................................................................

................................................

............................................................................

..............................................................................

............................................................................

.....................................................................................

......................................................

............................................................................

................................................................

..............................................

.............................................................................

...................................................................................................................

........................................................................................

................................

..................................................

.............................................................................

...................................... 6

........................ 6

............... 7

........................ 9

....................................... 9

......................................... 10

........................................... 10

............................... 10

......................................... 11

................................ 12

........................ 13

....................... 14

............ 14

................................... 15

................... 16

.................................... 16

.......................... 17

........................................ 18

................................... 18

.............................. 19

................................... 20

........................................ 21

............................. 21

................................... 22

................ 23

...................................... 24

............ 24

......................................... 24

.............. 25

..................................... 25

............ 26

..................... 27

....................................... 27

...................... 29

............ 30

.......................................... 30

.................................... 30

.......................................... 31

.............. 32

.................................... 33

............. 33

....................... 34

............................ 35

........................ 36

........................................ 37

..................................... 37

.................. 39

........................................ 40

............. 40

3.9.3

4. GETTING MORE INTO TH

4.1 L

4.2 INTERNATIONALIZATION

4.3 C

4.4 T

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.5 S

4.6 T

4.7 D

4.7.1

4.7.2

4.7.3

4.7.4

4.8 A

4.8.1

4.8.2

4.9 G

4.9.1

4.9.2

4.9.3

4.9.4

4.9.5

4.10 C

4.10.1

4.10.2

4.11 S

4.11.1

4.11.2

4.11.3

4.11.3.14.11.3.24.11.3.34.11.3.44.11.3.5

4.12 IMPORTING DATA

4.12.1

4.12.1.1

4.12.2

4.12.2.14.12.2.24.12.2.3

5. THE EXPERT’S CORNER

5.1 T

5.1.1

5.1.2

5.1.3

5.1.4

5.2 D

LINK A FAILED TEST TO

GETTING MORE INTO TH

LOCALIZATION ................................

NTERNATIONALIZATION

CHANGE TRACKING

TESTING COVERAGE

GLOBAL REQUIREMENTS T

GLOBAL SPECIFICATIONS

DETAILED REQUIREMENTS

DETAILED SPECIFICATIO

DETAILED TESTS COVERA

DETAILED CAMPAIGN COV

SCHEDULING TEST EXECU

TRACKING THE

DEFECTS REPORTING

PER-USER REPORTS

PER-SEVERITY REPORTS

PER-PRIORITY REPORTS

SUBMISSION/R

ATTACHMENTS ................................

ADD AN ATTACHMENT

DOWNLOAD/O

GENERATE DOCUMENTATIO

REQUIREMENTS BOOKS

SPECIFICATIONS BOOKS

PROJECTS BOOKS

TESTPLANS ................................ TEST REPORTS

CUSTOMIZING THE DOCUM

CHANGING THE LOGO

CUSTOMIZING THE REPOR

SEARCHING ................................

BY NAME ................................ BY ID ................................ ADVANCED AND PLAIN TE

4.11.3.1 Requirements4.11.3.2 Specifications4.11.3.3 Tasks4.11.3.4 Tests4.11.3.5 Defects

MPORTING DATA

FROM CSV4.12.1.1 Test and testcases

FROM XML4.12.2.1 Tests and testcases4.12.2.2 Requirements4.12.2.3 Specifications

THE EXPERT’S CORNER

TESTS ATTRIBUTES

ASSOCIATE SOME ATTRIB

CREATE AND ASSOCIATE

EDIT AN ATTRIBUTE

CREATE A CAMPAIGN BAS

DEPENDENCIES BETWEEN

INK A FAILED TEST TO A DE

GETTING MORE INTO THE DETAILS

................................

NTERNATIONALIZATION ................................

RACKING ................................

OVERAGE/TRACEABILITY

LOBAL REQUIREMENTS TRACEABILITY MATRIX

LOBAL SPECIFICATIONS TRACEABILITY MATRIX

ETAILED REQUIREMENTS

ETAILED SPECIFICATIONS COVERAGE

ETAILED TESTS COVERAGE

ETAILED CAMPAIGN COVERAGE

CHEDULING TEST EXECUTION

RACKING THE TEST IMPLEMENTATION

EPORTING ................................

USER REPORTS ................................SEVERITY REPORTS ................................PRIORITY REPORTS ................................

/RESOLUTION RATES

................................

DD AN ATTACHMENT ................................/OPEN AN ATTACHMENT

ENERATE DOCUMENTATION

EQUIREMENTS BOOKS ................................PECIFICATIONS BOOKS ................................ROJECTS BOOKS ................................

................................EST REPORTS ................................

USTOMIZING THE DOCUMENTS

HANGING THE LOGO ................................USTOMIZING THE REPOR

................................

................................................................

DVANCED AND PLAIN TEXT SEARCH

Requirements ................................Specifications ................................Tasks ................................Tests ................................Defects ................................

MPORTING DATA ................................

CSV ................................Test and testcases ................................

XML ................................Tests and testcasesRequirements ................................Specifications ................................

THE EXPERT’S CORNER ................................

ESTS ATTRIBUTES ................................

SSOCIATE SOME ATTRIBUTES TO A TEST

REATE AND ASSOCIATE A NEW ATTRIBUTE TO A

DIT AN ATTRIBUTE ................................REATE A CAMPAIGN BASED ON ATTRIBUTE FILT

EPENDENCIES BETWEEN TESTS

A DEFECT ................................

E DETAILS ................................

................................................................

................................

................................................................

RACEABILITY MATRIX

RACEABILITY MATRIX

TRACEABILITY MATRIX

COVERAGE ................................NS COVERAGE ................................

GE................................ERAGE................................

TION ................................

MPLEMENTATION ................................

................................

................................................................................................

ESOLUTION RATES ................................

................................................................

................................PEN AN ATTACHMENT ................................

................................

................................

................................................................

................................................................................................................................

ENTS ................................

................................USTOMIZING THE REPORTS ................................

................................................................

................................................................................................................................

XT SEARCH ................................................................................................

................................................................

................................................................................................................................

................................................................

................................................................................................

................................................................Tests and testcases ................................

................................

................................

................................

................................................................

UTES TO A TEST

A NEW ATTRIBUTE TO A

................................ED ON ATTRIBUTE FILT

TESTS ................................

................................

................................

................................

................................................................

................................

ATRIX ................................

RACEABILITY MATRIX ................................TRACEABILITY MATRIX ................................

................................................................

................................................................................................

................................................................

................................

................................................................

................................................................................................................................................................................................

................................

................................

................................................................................................

................................................................

................................................................

................................................................................................................................

................................................................

................................................................

................................................................................................................................

................................................................

................................................................................................

................................................................................................................................................................

................................................................

................................................................................................................................

................................

................................................................................................

................................................................................................

................................................................

................................................................

................................................................

................................

UTES TO A TEST ................................A NEW ATTRIBUTE TO A TEST ................................

................................................................ED ON ATTRIBUTE FILTER................................

................................................................

................................................................

..............................................................

................................................................

................................................................

................................................................

................................................................

................................................................

................................................................................................................................

................................................................................................

................................

................................................................

................................................................

................................................................................................................................

................................................................

................................................................

................................................................................................................................

................................

................................................................

................................................................................................................................

................................................................................................................................

................................

................................................................................................

................................

................................................................................................

................................................................................................................................................................................................

................................

................................................................

................................................................

................................................................................................................................

................................................................................................................................

................................................................

................................................................

................................

................................................................

................................................................................................

................................................................................................

................................

...................................................

..............................

.................................................

................................

................................

................................

.............................................................................................................................

............................................................................

..............................................................................................................

..........................................................

..............................................

................................

..............................................................................................................................................................

..................................................

.................................................

...............................................................................

............................................................

................................

................................................................

..............................................................................................

.........................................................

........................................................................................

.....................................................

.............................................................................................................

............................................

...................................................

...................................................................................................................................................................................

.............................................................

..............................................

................................................................................

................................................................................

...................................................

...................................................

.................................................

................................

.....................................................................................

..........................................................................................

.......................................................

................... 41

.............................. 42

................. 42

.................................... 43

.......................................... 44

...................................... 45

............................... 45

.............................. 45

............ 46

........................................... 46

.......................... 47

.................... 48

.......................... 49

.............. 50

....................................... 51

..................................... 52

............................... 52

............................... 53

.................. 54

................. 55

................................... 56

............... 56

............................ 56

................................ 56

................................ 57

........................................ 58

.................. 58

............ 59

......................... 60

.................................. 60

........................ 61

..................... 62

.................... 62

......................... 63

............ 63

................... 63

................... 64

................................ 64

................................ 65

............................. 65

.............. 66

................ 66

........................................... 66

................ 68

......................................... 68

................... 68

................... 69

................. 70

.......................................... 70

....................................... 70

..................... 71

...................................... 71

.......................... 72

....................... 73

5.3 T

5.4 D

5.4.1

5.4.2

6. LAUNCHERS

6.1 D

6.1.1

6.1.1.16.1.1.26.1.1.36.1.1.4

6.1.2

6.1.3

6.1.3.16.1.3.26.1.3.3

6.1.4

6.1.4.16.1.4.2

6.1.5

6.1.5.16.1.5.2

6.1.6

6.1.6.16.1.6.2

6.1.7

6.1.7.16.1.7.2

6.1.8

6.1.8.16.1.8.2

6.1.9

6.1.9.16.1.9.2

6.1.10

6.1.10.16.1.10.26.1.10.3

6.1.11

6.1.12

6.1.12.16.1.12.26.1.12.3

6.1.13

6.1.13.16.1.13.26.1.13.3

6.1.14

6.1.14.16.1.14.2

TEST EXECUTION HISTOR

DURATION OF TEST EXEC

ESTIMATED DURA

AVERAGE DURATION OF A

LAUNCHERS ................................

DEFAULT LAUNCHERS

MANUAL LAUNCHER

6.1.1.1 Configuration6.1.1.2 Control Bar6.1.1.3 Timeout per test6.1.1.4 Tutorial: Creating and executing manual tests

6.1.1.4.1 Declare the agent and the SUT6.1.1.4.2 Create a dedicated category for manual tests6.1.1.4.3 Create a test6.1.1.4.4 Run an individual test6.1.1.4.5 Creating a test campaign6.1.1.4.6 Run a campaign session

SIMPLE MANUA

AUTOIT LAUNCHER

6.1.3.1 Configuration6.1.3.2 Requirements6.1.3.3 Tutorial: Creating and executing AutoIt tests

6.1.3.3.1 Prerequisites6.1.3.3.2 Create a dedicated6.1.3.3.3 Creating a test campaign6.1.3.3.4 Run a campaign session

PERL LAUNCHER

6.1.4.1 Configuration6.1.4.2 Requirements

TCL LAUNCHER


AUTOMATEDQA6.1.6.1 Configuration6.1.6.2 Requirements

COMPUWARE


MICROSOFT®6.1.8.1 Configuration6.1.8.2 Requirements

BEANSHELL L6.1.9.1 Configuration6.1.9.2 Requirements

FROGLOGIC

6.1.10.1 Configuration6.1.10.2 Requirements6.1.10.3 Tutorial: Creating and executing Squish tests

6.1.10.3.1 Prerequisites6.1.10.3.2 Create a dedicated category for Squish tests and create two tests6.1.10.3.3 Creating a test campaign6.1.10.3.4 Run a

JUNIT V3 LAUNCHER

JUNIT V4 LAUNCHER

6.1.12.1 Confi6.1.12.2 Requirements6.1.12.3 Tutorial: Creating and executing JUnit tests

PYUNIT LAUNCHER

6.1.13.1 Configuration6.1.13.2 Requirements6.1.13.3 Tutorial: Creating and executing PyUnit tests

NUNIT LAUNCHER


EST EXECUTION HISTORY ................................

URATION OF TEST EXECUTION

STIMATED DURATION OF A CAMPAIGN

VERAGE DURATION OF A TEST

................................

EFAULT LAUNCHERS ................................

ANUAL LAUNCHER (MANUAL

Configuration ................................Control Bar ................................Timeout per test ................................Tutorial: Creating and executing manual tests

Declare the agent and the SUTCreate a dedicated category for manual testsCreate a test ................................Run an individual testCreating a test campaignRun a campaign session

IMPLE MANUAL LAUNCHER

AUNCHER (AUTOIT

Configuration ................................Requirements ................................Tutorial: Creating and executing AutoIt tests

Prerequisites ................................Create a dedicatedCreating a test campaignRun a campaign session

AUNCHER (PERL.JAR

Configuration ................................Requirements ................................

AUNCHER (TCL.JAR) Configuration ................................Requirements ................................

QA® TESTCOMPLETE V


OMPUWARE® TESTPARTNER


® VISUALSTUDIO


LAUNCHER (BEANSHELL

nfiguration ................................Requirements ................................

ROGLOGIC® SQUISH LAUNCHER

Configuration ................................Requirements ................................Tutorial: Creating and executing Squish tests

Prerequisites ................................Create a dedicated category for Squish tests and create two testsCreating a test campaignRun a campaign session

AUNCHER (JUNIT

AUNCHER (JUNIT

Configuration ................................Requirements ................................Tutorial: Creating and executing JUnit tests

AUNCHER (PYUNIT

Configuration ................................Requirements ................................Tutorial: Creating and executing PyUnit tests

AUNCHER (NUNIT


................................

UTION ................................

TION OF A CAMPAIGN ................................TEST ................................

................................................................

................................

MANUAL.JAR) ................................................................................................

................................................................................................

Tutorial: Creating and executing manual testsDeclare the agent and the SUT ................................Create a dedicated category for manual tests

................................................................Run an individual test ................................Creating a test campaign ................................Run a campaign session ................................

L LAUNCHER (SIMPLE_MANUAL

AUTOIT.JAR) ................................................................................................................................................................

Tutorial: Creating and executing AutoIt tests................................................................

Create a dedicated category for AutoIt tests and create a testCreating a test campaign ................................Run a campaign session ................................

JAR) ................................................................................................................................................................

................................................................................................................................................................

OMPLETE V7 LAUNCHER

................................................................................................................................

ARTNER LAUNCHER

................................................................................................................................

TUDIO LAUNCHER

................................................................................................................................

BEANSHELL.JAR

................................................................................................................................

AUNCHER (SQUISH

................................................................................................

Tutorial: Creating and executing Squish tests................................................................

Create a dedicated category for Squish tests and create two testsCreating a test campaign ................................

campaign session ................................

JUNIT3.JAR) ................................JUNIT4.JAR) ................................

................................................................................................

Tutorial: Creating and executing JUnit tests

PYUNIT.JAR) ................................................................................................................................

Tutorial: Creating and executing PyUnit tests

NUNIT.JAR) ................................................................................................................................

................................................................

................................................................

................................................................................................

................................

................................................................

................................................................

................................................................................................

Tutorial: Creating and executing manual tests ................................................................

Create a dedicated category for manual tests ................................................................

................................................................................................................................................................................................

MANUAL.JAR) ................................................................

................................................................

Tutorial: Creating and executing AutoIt tests ................................................................

category for AutoIt tests and create a test................................................................................................................................

................................................................................................................................

................................................................................................................................

AUNCHER (TESTCOMPLETE

................................................................

AUNCHER (TESTPARTNER

................................................................

AUNCHER (VISUALSTUDIO

................................................................

JAR)................................................................................................

SQUISH.JAR) ................................................................

................................................................Tutorial: Creating and executing Squish tests ................................

................................Create a dedicated category for Squish tests and create two tests

................................................................

................................................................

................................

................................................................

................................................................Tutorial: Creating and executing JUnit tests ................................

................................................................

................................................................Tutorial: Creating and executing PyUnit tests ................................

................................................................

................................................................

................................................................

................................

................................................................................................

................................................................

................................................................

................................................................................................................................

................................................................................................................................

................................................................................................

................................................................................................................................

................................................................................................................................................................................................

................................................................................................

................................................................................................................................

................................................................................................

category for AutoIt tests and create a test ................................................................................................................................................................

................................................................................................................................................................

................................................................................................................................................................

TESTCOMPLETE7.................................................................................................................................

TESTPARTNER.JAR) ................................................................................................................................................................

VISUALSTUDIO.JAR) ................................................................................................................................................................

................................................................................................................................................................................................

................................................................................................................................................................

................................................................................................

Create a dedicated category for Squish tests and create two tests ................................................................................................................................................................

................................................................

................................................................................................................................................................................................

................................

................................................................................................................................................................................................

................................

................................................................................................................................................................................................

................................

.........................................................

.....................................................................................

................................

................................

.......................................................................................................

..........................................................................................................

................................................................................................................................

................................................................................................

..................................................................................................................

............................................................................................................

...........................................................................................................

................................................................................................................................

...................................................................................................................

....................................................................................................................................................................

.......................................................................................................................................................................

7.JAR) ...................................................................................................................................

...........................................................................................................................................

...........................................................................................................................................

...........................................................................................................................................

...................................................................................................................................................................

..............................................................................................................................

................................................................................................

.............................................

................................................................................................................................................

................................................................

..................................................................................................................................................

...............................................................

.....................................................................................................................................................

................................ 74

......................... 75

........................................... 75

..................... 76

.................................... 77

...................................... 77

................. 78

...................... 78

......................... 78

................. 78

.................................. 80

................................... 80

............................................. 80

................................ 81

.................. 83

............................................. 85

............................................. 86

......................... 87

................... 87

...................... 87

..................... 87

.................................... 88

................................ 88

................... 88

............................................. 88

............................................. 89

......................... 90

...................... 90

..................... 90

............................ 91

...................... 91

..................... 91

........................ 92

...................... 92

..................... 92

....................................... 93

...................... 93

..................... 93

......................................... 94

...................... 94

..................... 94

....................................... 95

...................... 95

..................... 95

............................ 97

.................... 97

................... 98

................................. 98

.............................. 98

.......................................... 99

........................................... 99

......................................... 100

............. 101

............. 101

.................. 101

................. 101

................................. 101

............... 102

.................. 102

................. 102

............................... 102

.................. 103

.................. 103

................. 103

6.1.14.3

6.1.15

6.1.15.16.1.15.26.1.15.3

6.1.16

6.1.16.16.1.16.26.1.16.3

6.1.17

6.1.17.16.1.17.2

6.1.18

6.1.19

6.2 C

7. MEMORY PROFILING

7.1 B

7.2 R

6.1.14.3 Tutorial: Creating and executing NUnit tests

TESTNG LAUNCHER

6.1.15.1 Configuration6.1.15.2 Requirements6.1.15.3 Tutorial: Creating an

JALIAN® MARATHON

6.1.16.1 Configuration6.1.16.2 Requirements6.1.16.3 Tutorial: Creating an

EXECUTABLE


SIMULATION

SIMULATION

CUSTOM LAUNCHERS

MEMORY PROFILING

BROWSING TREES

RUNNING MANUAL TESTS

Tutorial: Creating and executing NUnit tests

AUNCHER (TESTNG

Configuration ................................Requirements ................................Tutorial: Creating an

ARATHON LAUNCHER

Configuration ................................Requirements ................................Tutorial: Creating an

XECUTABLE LAUNCHER (Configuration ................................Requirements ................................

IMULATION RANDOM LAUNC

IMULATION SUCCESS LAUNCHER

AUNCHERS ................................

MEMORY PROFILING ................................

ROWSING TREES ................................

UNNING MANUAL TESTS ON


TESTNG.JAR) ................................................................................................................................

Tutorial: Creating and executing TestNG tests

AUNCHER (MARATHON

................................................................................................

Tutorial: Creating and executing Marathon tests

(EXE.JAR) ................................................................................................................................

AUNCHER (RANDOM

AUNCHER (SUCCESS

................................

................................

................................................................

ON XAGENT ................................

Tutorial: Creating and executing NUnit tests ................................

................................................................

................................................................d executing TestNG tests ................................

MARATHON.JAR) ................................................................

................................................................d executing Marathon tests

................................................................

................................................................

RANDOM.JAR) ................................SUCCESS.JAR) ................................

................................................................

................................................................

................................

................................

................................

................................................................................................................................................................................................

................................

................................................................................................................................................................

................................

................................................................................................................................................................................................

................................................................

................................................................

................................

................................................................

................................................................

................................................................

...............................................................................................................................................

.............................................................

.........................................................................................................................................................

..........................................................

...............................................................................................................................................

..............................................................................................................

................................

....................................................

..........................................

.............................................

................................. 103

............ 104

.................. 104

................. 104

............................. 104

...................... 105

.................. 105

................. 105

.......................... 105

............ 106

.................. 106

................. 106

........................ 107

...................... 107

..................................... 107

.................... 109

.......... 109

............. 109

1. ObjectivesThis document information on how to use XS

2. General overviewAccess to Xauthenticate the user before he can use the system. Each user is then grantpermissions.

By default, an admin account is created (at installation time). The admin has (among some others) the permission to create users. If you do not know your credentials, contact your XQual Administrator. XQual Studio manage

• Users,

• SUT (Systems Under Test),

• Agents

• Requirements,

• Specifications,

• Tests,

• Test campaigns,

• Defects. Each of these entities can be smoothly

ObjectivesThis document will introduce users with X

ion on how to use XS

General overviewAccess to XStudio is restricted to users who have suitable credentials. A login process is used to authenticate the user before he can use the system. Each user is then grantpermissions.

By default, an admin account is created (at installation time). The admin has (among some others) the permission to create users. If you do not know your credentials, contact your XQual Administrator.

XQual Studio manages all entities implied in the process of testing. This includes:

Users,

SUT (Systems Under Test),

Agents

Requirements,

Specifications,

Tests,

Test campaigns,

Defects.

Each of these entities can be smoothly

Objectives will introduce users with X

ion on how to use XStudio.

General overviewStudio is restricted to users who have suitable credentials. A login process is used to

authenticate the user before he can use the system. Each user is then grant

By default, an admin account is created (at installation time). The admin has (among some others) the permission to create users. If you do not know your credentials, contact your XQual

s all entities implied in the process of testing. This includes:

SUT (Systems Under Test),

Test campaigns,

Each of these entities can be smoothly

will introduce users with XStudio’s Data Model

General overview Studio is restricted to users who have suitable credentials. A login process is used to

authenticate the user before he can use the system. Each user is then grant



Each of these entities can be smoothly and conveniently organized in

Studio’s Data Model

Studio is restricted to users who have suitable credentials. A login process is used to authenticate the user before he can use the system. Each user is then grant



and conveniently organized in

Studio’s Data Model as well as provide the basic

Studio is restricted to users who have suitable credentials. A login process is used to authenticate the user before he can use the system. Each user is then grant



and conveniently organized in separate tree

as well as provide the basic

Studio is restricted to users who have suitable credentials. A login process is used to authenticate the user before he can use the system. Each user is then granted with a list of



separate trees.

as well as provide the basic

Studio is restricted to users who have suitable credentials. A login process is used to ed with a list of


3. BasicsHere are the main entities managed in

Entity

Company

User

SUT

Agent

Requirement

Specification

Project

Task

Sprint

Category

Test

Campaign

Campaign Session

Defect

As you will see, XStudio is using a lot trees. Trees are flexible and allow managing entities a very flexible way. Each tree will be associate with a few icons: Tree Button

Basics Here are the main entities managed in

Company

Requirement

Specification

Category

Campaign

Campaign Session

As you will see, XStudio is using a lot trees. Trees are flexible and allow managing entities a very flexible way. Each tree will be associate with a few icons:

Tree Button Action

Refresh

Expand all

Expand all except for

Collapse all

Show closed items

Display the previous/next page

Here are the main entities managed in

Function

Several companies will be involved in the testing process:

• The company who deliver the product to test

• The company who is in charge of writing the testplan

• The company who is in charge of implementingOf course, all these companies can be the same.

Each company have users that will be involved in the testing process as:

• Author of the testplan

• Test developer

• Test operator

• Task perf

(System Under What we want to test. This can be a software or a Hardware target.

Tests can be run all locallyAll hosts with XStudio

Features required for the

Deduced from the requirements, the specifications precisely detail each function of the SUT.

A generic project

A project is made of tasks that will be spread in differe

Some tasks are associated to a sprint. of each sprint.

Generally, there will be different category of tests for one single product. A Category is characterized by a unique way to r

Tests are developed based on the specifications. Each test must verify one particular item of the specifications. Tests can includes different testcases.

A campaign is a selection of tests. A campadifferent version of the product: these executions are called

A campaign session is an execution instance of a campaign. This includes results from the execution associated with spec

Campaign session will highlight presence of defect in the a Campaign Session may be due to the same defect. Analyzing of the test report allows to create this defects.


Expand all

Expand all except for leaves

Collapse all

closed items (available for sprints


Here are the main entities managed in XStudio’s Data Model:


The company who deliver the product to test

The company who is in charge of writing the testplan

company who is in charge of implementingOf course, all these companies can be the same.


Author of the testplan

Test developer

Test operator

Task performer

nder Test) What we want to test. This can be a software or a Hardware target.

Tests can be run all locally or on any XStudio or XAgent

eatures required for the SUT

Deduced from the requirements, the specifications precisely detail each function

A generic project


Some tasks are associated to a sprint. .




A campaign session is an execution instance of a campaign. This includes results from the execution associated with spec


Table 1 -


leaves

(available for sprints


Table 2 - Tree Buttons

Data Model:




company who is in charge of implementingOf course, all these companies can be the same.


Author of the testplan

What we want to test. This can be a software or a Hardware target.

or on any host having XAgent MUST be referenced in the Agent

SUT.



Some tasks are associated to a sprint. An intermediate deliverable will come out




A campaign session is an execution instance of a campaign. This includes results from the execution associated with specific configuration of execution.


Entities


(available for sprints, tasks and defects)

Tree Buttons




company who is in charge of implementing and executingOf course, all these companies can be the same.



having XAgentMUST be referenced in the Agent


A project is made of tasks that will be spread in different sprints.

An intermediate deliverable will come out

Generally, there will be different category of tests for one single product. A Category is characterized by a unique way to run all the test


A campaign is a selection of tests. A campaign can be executed several time on different version of the product: these executions are called

A campaign session is an execution instance of a campaign. This includes results ific configuration of execution.

Campaign session will highlight presence of defect in the a Campaign Session may be due to the same defect. Analyzing of the test report

As you will see, XStudio is using a lot trees. Trees are flexible and allow managing entities a very

defects)



and executing



XAgent installed and running.MUST be referenced in the Agent tree.


nt sprints.


Generally, there will be different category of tests for one single product. A un all the tests under this category.


ign can be executed several time on different version of the product: these executions are called Campaign Session

A campaign session is an execution instance of a campaign. This includes results ific configuration of execution.

Campaign session will highlight presence of defect in the SUT. Several failures in a Campaign Session may be due to the same defect. Analyzing of the test report


the tests


installed and running. tree.



Generally, there will be different category of tests for one single product. A under this category.


ign can be executed several time on Campaign Session.

A campaign session is an execution instance of a campaign. This includes results

. Several failures in a Campaign Session may be due to the same defect. Analyzing of the test report


All these icons will be used along all XStudio’s GUI. They may be associated wioverlay icon which meaning is the following: Overlay

XStudio’s GUI is based on a simple

• A left panel including a tree

• A right panel:

All these icons will be used along all XStudio’s GUI. They may be associated wioverlay icon which meaning is the following:

Represents

Create

Delete

Move

Copy

Edit

View

Initialized

Playing

Paused

Stopped

Open

Add

Remove

Search

Select

Special item (read

Move to the right

Move to the left

Move up

Move down

Show items (available for closable items such as sprints, tasks or defects)

’s GUI is based on a simple

A left panel including a tree

A right panel: o showing information concerning the element selected in the treeo proposing a toolbar allowing the user to execute some

element selected in the tree.


Represents

Special item (read-only)

Move to the right

Move to the left

Move down


Table

’s GUI is based on a simple and clean

A left panel including a tree

showing information concerning the element selected in the treeproposing a toolbar allowing the user to execute some element selected in the tree.



Table 3 - Overlay Icons

and clean design:

showing information concerning the element selected in the treeproposing a toolbar allowing the user to execute some element selected in the tree.

All these icons will be used along all XStudio’s GUI. They may be associated wi


Overlay Icons

design:

showing information concerning the element selected in the treeproposing a toolbar allowing the user to execute some

All these icons will be used along all XStudio’s GUI. They may be associated wi


showing information concerning the element selected in the treeproposing a toolbar allowing the user to execute some specific

All these icons will be used along all XStudio’s GUI. They may be associated with additional


showing information concerning the element selected in the tree specific action

th additional

actions on the

3.1 UserHere is a typical use

• the total number of users

• the number of users in each company

• the number of users in each folder

• the status of the users (enabled/disabled indicated by the color of the icon)

Hierarchies, working groups and teamsof folders hosting users.

3.1.1 Create a companyThis first thing to do is to create your own company. To do this:

• in the tree,

• on the right panel, click on the

• enter the name of the company and submit

• immediately, the company appears in the tree Note: this company entity will be automatically shared in the SUT tree.

User TreeHere is a typical user tree. It immediately shows a number of useful information:

the total number of users

the number of users in each company

the number of users in each folder

the status of the users (enabled/disabled indicated by the color of the icon)

Hierarchies, working groups and teamsof folders hosting users.

Create a companyThis first thing to do is to create your own company. To do this:

in the tree, select

on the right panel, click on the

enter the name of the company and submit

immediately, the company appears in the tree

Note: this company entity will be automatically shared in the SUT tree.

Tree r tree. It immediately shows a number of useful information:

the total number of users




Hierarchies, working groups and teams

Create a companyThis first thing to do is to create your own company. To do this:

select the root folder





r tree. It immediately shows a number of useful information:




Figure 1 - User Tree

Hierarchies, working groups and teams can be easily managed in X

Create a company This first thing to do is to create your own company. To do this:

he root folder

on the right panel, click on the create company






User Tree

can be easily managed in X

This first thing to do is to create your own company. To do this:

create company button






can be easily managed in XStudio by creating a structure

button




Studio by creating a structure

Studio by creating a structure

3.1.2 Create a hierarchy in theThen, it’s important to well define the working groups and teams in the company. This can be achieved by creating a complete tree of folders and sub

• in the tree, select a company


• enter the name of the folder and submit

• immediately, the folder appears in the tree Of course, a subRedo the same operation until you are satisfied with the organisation.

3.1.3 Create a userNow that you have a cousers. To do so:

• in the tree, select a folder


• a dialog box including two tabs is

• fill the locationthe system.

• the first checkbox corresponding to the to this user)

• click on submit

• immediately, the user appears in the tree From now, you can exit

3.1.4 Submit a nEach user can enter some absences. After submission, absences have the status manager has set them as approved, the status changes accordingly. User’s absences are visible by selecting the

Create a hierarchy in theThen, it’s important to well define the working groups and teams in the company. This can be achieved by creating a complete tree of folders and sub

in the tree, select a company


enter the name of the folder and submit

immediately, the folder appears in the tree

Of course, a sub-folder can be created into a folder.Redo the same operation until you are satisfied with the organisation.

Create a userNow that you have a cousers. To do so:

n the tree, select a folder


a dialog box including two tabs is

fill the Details tab with thelocation. Do not forget to checkthe system.

the Rights tab is here to select what this user will be able to do. For now, just check the st checkbox corresponding to the

to this user)

click on submit

immediately, the user appears in the tree

From now, you can exit XStudio

Submit a nEach user can enter some absences. After submission, absences have the status manager has set them as approved, the status changes accordingly.

User’s absences are visible by selecting the

Create a hierarchy in theThen, it’s important to well define the working groups and teams in the company. This can be achieved by creating a complete tree of folders and sub

in the tree, select a company




folder can be created into a folder.Redo the same operation until you are satisfied with the organisation.

Create a user Now that you have a company with its internal organization defined, you’re ready to create some




tab with the user name, password, preferred language, email address. Do not forget to check

tab is here to select what this user will be able to do. For now, just check the st checkbox corresponding to the


XStudio, restart and login with the new user credentials.

Submit a new absenceEach user can enter some absences. After submission, absences have the status manager has set them as approved, the status changes accordingly.

User’s absences are visible by selecting the

Create a hierarchy in the companyThen, it’s important to well define the working groups and teams in the company. This can be achieved by creating a complete tree of folders and sub

on the right panel, click on the create folder



folder can be created into a folder.Redo the same operation until you are satisfied with the organisation.

mpany with its internal organization defined, you’re ready to create some

on the right panel, click on the create user

a dialog box including two tabs is displayed

user name, password, preferred language, email address. Do not forget to check the Enabled

tab is here to select what this user will be able to do. For now, just check the st checkbox corresponding to the root folder


, restart and login with the new user credentials.

bsence Each user can enter some absences. After submission, absences have the status manager has set them as approved, the status changes accordingly.

User’s absences are visible by selecting the Absences

companyThen, it’s important to well define the working groups and teams in the company. This can be achieved by creating a complete tree of folders and sub-folders. To do this:

create folder button


folder can be created into a folder. Redo the same operation until you are satisfied with the organisation.


create user button

displayed

user name, password, preferred language, email addressEnabled checkbox

tab is here to select what this user will be able to do. For now, just check the root folder (this will grant automatically ALL the rights


Each user can enter some absences. After submission, absences have the status manager has set them as approved, the status changes accordingly.

Absences tab:

company Then, it’s important to well define the working groups and teams in the company. This can be

folders. To do this:

Redo the same operation until you are satisfied with the organisation.


user name, password, preferred language, email addresscheckbox. A disabled user cannot login into

tab is here to select what this user will be able to do. For now, just check the (this will grant automatically ALL the rights


Each user can enter some absences. After submission, absences have the status manager has set them as approved, the status changes accordingly.

Then, it’s important to well define the working groups and teams in the company. This can be


user name, password, preferred language, email address. A disabled user cannot login into



Each user can enter some absences. After submission, absences have the status new. Once the

Then, it’s important to well define the working groups and teams in the company. This can be


user name, password, preferred language, email address and . A disabled user cannot login into


. Once the

To enter a new absence:

• in the tree, select the user

• on the right panel, sel

• press the

• enter the type, start and stop dates and optionally a comment and submit

• immediately, the absence appears in the list

3.1.5 Edit an absenceIf you are manager (have the rights to approve absences), then you can edit an absence and change its status.

• in the tree, select the user


• select an absence

• press the

• enter the typ

• immediately, the absence appears in the list


in the tree, select the user

on the right panel, sel

press the create absence

enter the type, start and stop dates and optionally a comment and submit

immediately, the absence appears in the list

Edit an absencemanager (have the rights to approve absences), then you can edit an absence and status. To edit an absence:



select an absence

press the edit absence





on the right panel, select the Absences

create absence button



Edit an absence manager (have the rights to approve absences), then you can edit an absence and

To edit an absence:


on the right panel, select the Absences

select an absence

absence button

e, start and stop dates and optionally a comment and submit


Absences tab

button



manager (have the rights to approve absences), then you can edit an absence and To edit an absence:

Absences tab

button



tab



manager (have the rights to approve absences), then you can edit an absence and

tab










3.1.6 Check the calendars• in the tree, select the root folder or a user


• the calendar is displayed. Two modes

• You can select the mode by clicking on the

• You can also “move” the calendar by using the arrow keys.

Check the calendarsin the tree, select the root folder or a user


the calendar is displayed. Two modeso Monthlyo Half-yearly

You can select the mode by clicking on the o Monthlyo Half-yearly

You can also “move” the calendar by using the arrow keys.

Check the calendarsin the tree, select the root folder or a user

on the right panel, select the Calendar

the calendar is displayed. Two modesMonthly mode

yearly mode

You can select the mode by clicking on the Monthly:

yearly:


Figure

Check the calendars in the tree, select the root folder or a user

Calendar tab

the calendar is displayed. Two modes are available:

You can select the mode by clicking on the


Figure 2 - Calendar Monthly

tab

are available:

You can select the mode by clicking on the appropriate


Calendar Monthly View

appropriate toggle button


View

toggle button:

3.1.7 Changing admin password

Note: The default admin user is configured with the password “password”. This is strongly recommended to change this password as soon as possible. To do so:

• in the tree, select the

• on the right panel (

Changing admin password

The default admin user is configured with the password “password”. This is strongly recommended to change this password as soon as possible. To do so:

n the tree, select the

on the right panel (

Figure



n the tree, select the admin user (XQual/Administration/admin)

on the right panel (Details sub

Figure 3 - Calendar Half



user (XQual/Administration/admin)

sub-tab), enter the new password, confirm and submit

Calendar Half-Yearly View




tab), enter the new password, confirm and submit

Yearly View




The default admin user is configured with the password “password”. This is strongly


The default admin user is configured with the password “password”. This is strongly

3.2 SUT Here is a typical SUT tre

• the total number

• the number of SUTs in each company

• the number of SUTs in each folder

• the version of each SUT

A SUT is an abstract object representing the target we want to test. It can be a hardware device or a software component. The SUT must be detailed enough so that we can identify it easily.A SUT should be uniquely defined through its name and version. It is possible to group/organize the SUTs by creating a structure of folders and subthe SUTs.

3.2.1 Create a SUTHere is the process to create a new SUT:



• enter the name and the version of the SUT and submit

• immediately, the

SUT TreeHere is a typical SUT tre

the total number

the number of SUTs in each company

the number of SUTs in each folder

the version of each SUT

A SUT is an abstract object representing the target we want to test. It can be a hardware device or ware component. The SUT must be detailed enough so that we can identify it easily.

A SUT should be uniquely defined through its name and version.

It is possible to group/organize the SUTs by creating a structure of folders and sub

Create a SUTHere is the process to create a new SUT:



enter the name and the version of the SUT and submit

immediately, the

Tree Here is a typical SUT tree. It immediately shows a number of useful information:

the total number of SUTs



the version of each SUT




Create a SUT Here is the process to create a new SUT:

n the tree, select a folder (create one if necessary)



immediately, the SUT appears in the tr

e. It immediately shows a number of useful information:



Figure 4 - SUT Tree




Here is the process to create a new SUT:

(create one if necessary)

on the right panel, click on the create sut button


appears in the tree


SUT Tree





button








It is possible to group/organize the SUTs by creating a structure of folders and sub-folders hosting


folders hosting

3.2.2 Create a SUT IHere is the process to create a new SUT inheriting requirements from another SUT:

• in the tree, select a folder (create one if necessary)


• enter the

• select the

• click the

• select the reference SUT and submit

• click the

• (opt.) select/unselect some requirements if required

• submit

• immedi

Create a SUT IHere is the process to create a new SUT inheriting requirements from another SUT:

in the tree, select a folder (create one if necessary)


enter the name and the version of the SUT

select the Requirements

click the Preset

select the reference SUT and submit

click the Preset

(opt.) select/unselect some requirements if required

submit

immediately, the SUT appears in the tree

Create a SUT Inheriting requirements from another SUTHere is the process to create a new SUT inheriting requirements from another SUT:



name and the version of the SUT

Requirements tab

import from SUT s


import from SUT


ately, the SUT appears in the tree

nheriting requirements from another SUTHere is the process to create a new SUT inheriting requirements from another SUT:


on the right panel, click on the create sut button


from SUT settings


from SUT button


ately, the SUT appears in the tree



button


ettings button




nheriting requirements from another SUT

3.3 Agent TreeHere is a typical requirement tree. It immediately shows a number of useful information:

• the total number of agents

• the number of agents in each folder

• the operating system of each agent

All hosts on the network that will have tree to be able to

3.3.1 AddHere is the process to add your local host to the system:

• in the tre


• enter the hostname or the static ip address of your local host


Note: what you enter in the and ping it.

Agent Treee is a typical requirement tree. It immediately shows a number of useful information:

the total number of agents

the number of agents in each folder

the operating system of each agent

All hosts on the network that will have tree to be able to execute

Add my local hostHere is the process to add your local host to the system:



enter the hostname or the static ip address of your local host

immediately, the

what you enter in the and ping it.

Agent Tree e is a typical requirement tree. It immediately shows a number of useful information:

the total number of agents



All hosts on the network that will have execute some tests.

my local hostHere is the process to add your local host to the system:

e, select a folder (create one if necessary)



immediately, the agent appears in the tree

what you enter in the Name field MUST be ping

e is a typical requirement tree. It immediately shows a number of useful information:



Figure 5 - Agent Tree

All hosts on the network that will have XStudio of some tests.

my local host Here is the process to add your local host to the system:


on the right panel, click on the create agent


appears in the tree

ield MUST be ping


Agent Tree

of XAgent installed on MUST be included in the

Here is the process to add your local host to the system:


agent button


appears in the tree

ield MUST be ping-able. To check this, open a windows console


installed on MUST be included in the

enter the hostname or the static ip address of your local host and submit

able. To check this, open a windows console



and submit




3.3.2 Add all necessary hostsRedo the same for all hosts that will have XStudio or XAgent installed.

Add all necessary hostsRedo the same for all hosts that will have XStudio or XAgent installed.

Add all necessary hostsRedo the same for all hosts that will have XStudio or XAgent installed.

Add all necessary hosts Redo the same for all hosts that will have XStudio or XAgent installed.Redo the same for all hosts that will have XStudio or XAgent installed.Redo the same for all hosts that will have XStudio or XAgent installed.

3.4 RequirementHere is a typical requirement tree. It immediately shows a numbe

• the total number of requirements

• the number of requirements in each category

• the number of requirements in each folder

• the status of each requirement (indicated by the color of the icon)

• the priority of each requirement (indicated

Requirements are all the conditions the SUT should be compliant with. Generally, the requirements list is the first thing we do before working on detailed specification. In a perfectshould come with a list of requirements but this may not be the case. Entering the requirements of the SUT is an optional task. We do encourage to completely the requirements though. This information is very useful for coverage re You can add in the requirement tree the complete description of each requirement or you can decide to just point to the external requirements document(s).

3.4.1 Create a categoryThis first thing to do is to create a

Requiremente is a typical requirement tree. It immediately shows a numbe

the total number of requirements

the number of requirements in each category

the number of requirements in each folder

the status of each requirement (indicated by the color of the icon)

the priority of each requirement (indicated

Requirements are all the conditions the SUT should be compliant with. Generally, the requirements list is the first thing we do before working on detailed specification. In a perfectshould come with a list of requirements but this may not be the case.

Entering the requirements of the SUT is an optional task. We do encourage to completely the requirements though. This information is very useful for coverage re

You can add in the requirement tree the complete description of each requirement or you can decide to just point to the external requirements document(s).

Create a categoryThis first thing to do is to create a

Requirement Treee is a typical requirement tree. It immediately shows a numbe






Figure




Create a categoryThis first thing to do is to create a category

Tree e is a typical requirement tree. It immediately shows a numbe






Figure 6 - Requirement Tree




Create a category category. To do this:

e is a typical requirement tree. It immediately shows a numbe



the priority of each requirement (indicated by the column)

Requirement Tree




. To do this:



column)

Requirement Tree


Entering the requirements of the SUT is an optional task. We do encourage to completely the requirements though. This information is very useful for coverage reporting.

You can add in the requirement tree the complete description of each requirement or you can

r of useful information:

Requirements are all the conditions the SUT should be compliant with. Generally, the requirements list is the first thing we do before working on detailed specification. In a perfect world, the SUT

Entering the requirements of the SUT is an optional task. We do encourage to completely porting.


Requirements are all the conditions the SUT should be compliant with. Generally, the requirements world, the SUT

Entering the requirements of the SUT is an optional task. We do encourage to completely defining


• in the tree,


• a dialog box is

• enter the name of the category.

• enter the description of the category. You can use the formatting tools (wikithe text.

• enter the launcher to be associated with that category: tests that will be included under that category will be executed using the manual test launcher.

• click on submit


Note: this category entity will be automatically shared in the

3.4.2 Create a requirementNow that you have a some requirements



• a dialog box is

• pick a requirement type

• if required, pick a requirement category

• enter the name of the

• enter the description of the requirement. You can use the formatting tools (wikiformat the text. Later, in reports this text will appear correctly formatted.

• select the status of the requirement (

in the tree, select


a dialog box is displayed

enter the name of the category.

enter the description of the category. You can use the formatting tools (wikithe text. Later, in reports

enter the launcher to be associated with that category: tests that will be included under that category will be executed using the manual test launcher.

click on submit

immediately, the

this category entity will be automatically shared in the

Create a requirementNow that you have a category

requirements. To do so:




pick a requirement type

if required, pick a requirement category

enter the name of the

enter the description of the requirement. You can use the formatting tools (wikiformat the text. Later, in reports this text will appear correctly formatted.

select the status of the requirement (

select the root folder


displayed


enter the description of the category. You can use the formatting tools (wikiin reports this text will appear correctly formatted.

enter the launcher to be associated with that category: tests that will be included under that category will be executed using the manual test

immediately, the category appears in the tree


Create a requirementcategory with its internal organization defined

. To do so:



displayed

pick a requirement type


enter the name of the requirement


select the status of the requirement (

the root folder

on the right panel, click on the create category


enter the description of the category. You can use the formatting tools (wikithis text will appear correctly formatted.


appears in the tree


Create a requirement with its internal organization defined


on the right panel, click on the create requirement


requirement


select the status of the requirement (at creation ti

ategory button



appears in the tree

this category entity will be automatically shared in the Specification

with its internal organization defined


requirement button


at creation time, you can only choose


enter the launcher to be associated with that category: manual.jartests that will be included under that category will be executed using the manual test

Specification, Tests

with its internal organization defined (see, you’re

button


, you can only choose

enter the description of the category. You can use the formatting tools (wiki-style) to format

.jar indicates that all the tests that will be included under that category will be executed using the manual test

Tests and Defect

, you’re ready to create


, you can only choose New or

style) to format

indicates that all the tests that will be included under that category will be executed using the manual test

Defect trees.

ready to create

enter the description of the requirement. You can use the formatting tools (wiki-style) to

or Ack)

• select the priority of the requirement

• click on submit

• immediately, the requirement appears in the tree

3.4.3 Edit a requirementThe requirements will probably be edited several times complete workflow including Overlay

New

Ack

Approved

To edit a requirement:

• in the tree, select a requirement

• on the right panel (details tab), edit the information you wish and submit

Note: Depending of the rights you’ve been granted, you may or may not be able to set the status to a specif

select the priority of the requirement

click on submit

immediately, the requirement appears in the tree

Edit a requirementThe requirements will probably be edited several times complete workflow including

Represents

New requirement

The requirement is being reviewed by the person who

The requirement has been approved

To edit a requirement:

n the tree, select a requirement

on the right panel (details tab), edit the information you wish and submit

Depending of the rights you’ve been granted, you may or may not be able to set the status to a specific state.



Edit a requirementThe requirements will probably be edited several times complete workflow including three states

New requirement

equirement is being reviewed by the person who


Table



Depending of the rights you’ve been granted, you may or may not be able to set the status to



Edit a requirement The requirements will probably be edited several times

three states:

equirement is being reviewed by the person who


Table 4 - Requireme





The requirements will probably be edited several times by different people

equirement is being reviewed by the person who is supposed to

Requirements Status



by different people

is supposed to sign it off

nts Status



by different people and will go through a

sign it off



go through a


3.5 Specification TreeHere is a typical specification tree. It immediately shows a number of useful information:

• the total number of specifications

• the number of specifications in each category

• the number of specifications in each folder

• the stat

• the priority of each specification (indicated by the

Specifications are detailed and unitary description of a specific behavi You can add in the decide to just point to the external requirements document(s).

3.5.1 Create a To create a specification

• in the tree, select a folder (create one


• a dialog box is

Specification Treeis a typical specification tree. It immediately shows a number of useful information:

the total number of specifications

the number of specifications in each category

the number of specifications in each folder

the status of each specification (indicated by the color of the icon)

the priority of each specification (indicated by the

Specifications are detailed and unitary description of a specific behavi

You can add in the specificationdecide to just point to the external requirements document(s).

Create a specificationTo create a specification

n the tree, select a folder (create one



Specification Treeis a typical specification tree. It immediately shows a number of useful information:




us of each specification (indicated by the color of the icon)


Figure


specification tree the complete description of each decide to just point to the external requirements document(s).

specificationTo create a specification:

n the tree, select a folder (create one


displayed

Specification Tree is a typical specification tree. It immediately shows a number of useful information:






Figure 7 - Specification Tree


tree the complete description of each decide to just point to the external requirements document(s).

specification


on the right panel, click on the create specification

is a typical specification tree. It immediately shows a number of useful information:




the priority of each specification (indicated by the column)

Specification Tree


tree the complete description of each decide to just point to the external requirements document(s).

if necessary)

specification button



column)

Specification Tree

Specifications are detailed and unitary description of a specific behavior..

tree the complete description of each specification

button


specification or you can

or you can

• check the formal checkbox if needed


• enter the description of the format the text. Later, in reports this text will appear correctly formatted.

• select the status of the

• select the priority of the

• click on submit

• immediately, t

3.5.2 Edit a The specificationscomplete workflow including three states: Overlay

New

Ack

Approved

To edit a specification

• In the tree, select a

• on the right panel

Note: Depending of the rights you’ve been granted, you may or may not be able to set the status to a specific state.

check the formal checkbox if needed


enter the description of the format the text. Later, in reports this text will appear correctly formatted.

select the status of the

select the priority of the

click on submit

immediately, the

Edit a specificationspecifications will probably be edited several times by different people and will go through a

complete workflow including three states:

Represents

New specification

The specification

The specification

specification:

In the tree, select a

on the right panel



enter the name of the specification

enter the description of the specificationformat the text. Later, in reports this text will appear correctly formatted.

select the status of the specification

select the priority of the specification

he specification

specificationwill probably be edited several times by different people and will go through a


specification

ification is being reviewed by the person who

specification has been approved

Table

In the tree, select a specification




specification

specification. You can use the formatting toolsformat the text. Later, in reports this text will appear correctly formatted.

specification (at creation time

specification

specification appears in the tree

specification will probably be edited several times by different people and will go through a


is being reviewed by the person who

has been approved

Table 5 - Specification Status

specification

(details tab), edit the information you wish and submit


. You can use the formatting toolsformat the text. Later, in reports this text will appear correctly formatted.

at creation time, you can only choose

appears in the tree

will probably be edited several times by different people and will go through a

is being reviewed by the person who is supposed to

Specification Status



. You can use the formatting toolsformat the text. Later, in reports this text will appear correctly formatted.

, you can only choose


is supposed to sign it off

Specification Status



. You can use the formatting tools (wikiformat the text. Later, in reports this text will appear correctly formatted.

, you can only choose New or


sign it off



(wiki-style) to

or Ack)



3.6 Project TreeHere is a typical project tree. It immediately shows a number

• the total number of projects

• the total number of sprints

• the total number of tasks

• the number of sprints in each project

• the number of tasks in each project

• the status of each sprint (indicated by the color of the

• if the tasks have been already affected to a sprint or not (indicated by the color of the task

icon

A project must be created for anydevelopment project but can also the main product line but also for automated testsuitescompany. A project is made of develop (a feature is made of several tasks). The scrumproject. So, to deliver a product, you will deliver several intermediate releases, each corresponding

Project TreeHere is a typical project tree. It immediately shows a number

the total number of projects

the total number of sprints

the total number of tasks

the number of sprints in each project

the number of tasks in each project

the status of each sprint (indicated by the color of the

he tasks have been already affected to a sprint or not (indicated by the color of the task

icon – a grayed icon

must be created for anydevelopment project but can also the main product line but also for automated testsuites

A project is made of tasksdevelop (a feature is made of several tasks).

scrum methodology defines the notion of o, to deliver a product, you will deliver several intermediate releases, each corresponding

Project Tree Here is a typical project tree. It immediately shows a number

the total number of projects

the total number of sprints

the total number of tasks





a grayed icon indicates that the task

must be created for any development project but can also be more genericthe main product line but also for automated testsuites

tasks. Most of the time, a develop (a feature is made of several tasks).

methodology defines the notion of o, to deliver a product, you will deliver several intermediate releases, each corresponding

Here is a typical project tree. It immediately shows a number





indicates that the task

Figure 8 - Project Tree

new “productbe more generic

the main product line but also for automated testsuites

. Most of the time, a develop (a feature is made of several tasks).

methodology defines the notion of sprintso, to deliver a product, you will deliver several intermediate releases, each corresponding

Here is a typical project tree. It immediately shows a number of useful information:

the status of each sprint (indicated by the color of the project


indicates that the task is already affected to a spint

Project Tree

product” you want to be more generic. Project can be created for the development of

the main product line but also for automated testsuites and much other internal project in your

. Most of the time, a task is the smaller

sprints. A sprint is the result of any iteration in a o, to deliver a product, you will deliver several intermediate releases, each corresponding

of useful information:

project icon)


is already affected to a spint

you want to deliver. A project is usually a roject can be created for the development of

and much other internal project in your

task is the smaller entity that a developer can

. A sprint is the result of any iteration in a o, to deliver a product, you will deliver several intermediate releases, each corresponding

of useful information:


is already affected to a spint)

. A project is usually a roject can be created for the development of


entity that a developer can



. A project is usually a roject can be created for the development of


entity that a developer can


to a sprint. A sprint is generally at most 2 or 3 weeks long. A number of tasks will be associated to each sprint and at the end of the sprint a demo of all the fea

3.6.1 Create a To create a



• a dialog box is displayed


• enter a focus ratio effective work)

• enter the description of the the text. Later, in reports this text will appear correctly formatted.

• click


3.6.2 Create a taskTo create a task:




• enter the

• enter the description of the text. Later, in reports this text

• enter the priority of this task

• enter the estimated effort in man.days (peopl

• click on submit


3.6.3 Create a sprintTo create a sprint:

• in the tree, select a project




Create a projectTo create a project:





enter a focus ratio effective work)

enter the description of the the text. Later, in reports this text will appear correctly formatted.

click on submit

immediately, the

Create a taskTo create a task:

in the tree, select a folder




enter the description of the text. Later, in reports this text

enter the priority of this task

enter the estimated effort in man.days (peopl

click on submit

immediately, the

Create a sprintTo create a sprint:

in the tree, select a project




project




enter the name of the project

enter a focus ratio (this corresponds to the percentage of time that people will spend on

enter the description of the projectthe text. Later, in reports this text will appear correctly formatted.

immediately, the project appears in the tree

Create a task

in the tree, select a folder belonging to a project



name of the task

enter the description of the tasktext. Later, in reports this text

enter the priority of this task


immediately, the task appears in the tree

Create a sprint

in the tree, select a project





on the right panel, click on the create project

(this corresponds to the percentage of time that people will spend on

project. You can use the formatting tools (wikithe text. Later, in reports this text will appear correctly formatted.

appears in the tree

belonging to a project

on the right panel, click on the create task

task. You can use the formatting tools (wikitext. Later, in reports this text will appear correctly formatted


appears in the tree

on the right panel, click on the create sprint

to a sprint. A sprint is generally at most 2 or 3 weeks long. A number of tasks will be associated to each sprint and at the end of the sprint a demo of all the features developed can be done.


project button


. You can use the formatting tools (wikithe text. Later, in reports this text will appear correctly formatted.

appears in the tree

belonging to a project (create one if necessary)

task button

. You can use the formatting tools (wikiwill appear correctly formatted

enter the estimated effort in man.days (people working 100% of their time)

sprint button

to a sprint. A sprint is generally at most 2 or 3 weeks long. A number of tasks will be associated to tures developed can be done.


. You can use the formatting tools (wikithe text. Later, in reports this text will appear correctly formatted.


. You can use the formatting tools (wikiwill appear correctly formatted

e working 100% of their time)



. You can use the formatting tools (wiki-style) to format


. You can use the formatting tools (wiki-style) to format the

e working 100% of their time)



style) to format

style) to format the

• enter the name

• enter the description of the sprint. You can use the formatting tools (wikithe text. Later, in reports this text will appear correctly formatted.

• select the status of the sprint (at creation time, you can only choose

• select the start and stop dates for this sprint

• click on submit

• immediately, the sprint appears in the tree

3.6.4 Edit a The sprints workflow including thr Overlay

Idle

Running

Finished

To edit a sprint


• on the right panel (details tab), ed

• the duration (in effective man.days) is automatically updated

Note: Depending of the rights you’ve been granted, you may or may not be able to set the status to a specific state.

3.6.5 Allocate some resources to a spAll the tasks associated to a sprint will be performed by a pool of resources. These resources are users (taken from the user tree). To allocate some resources to a sprint:

• in the tree, select the sprint


• un-toggle the

• check all the users that need to be allocated to the current sprint and indicate by editing the percentage of availability of each resource

• (opt.) re

• click on submit


enter the description of the sprint. You can use the formatting tools (wikithe text. Later, in reports this text will appear correctly formatted.

select the status of the sprint (at creation time, you can only choose

select the start and stop dates for this sprint

click on submit

immediately, the sprint appears in the tree

Edit a sprint will probably be edited several times by different people and will go through a complete

workflow including three states:

Represents

Idle sprint

The sprint is currently running

The sprint if finished

sprint:


on the right panel (details tab), ed

the duration (in effective man.days) is automatically updated


Allocate some resources to a spAll the tasks associated to a sprint will be performed by a pool of resources. These resources are users (taken from the user tree). To allocate some resources to a sprint:

in the tree, select the sprint


toggle the select filter

check all the users that need to be allocated to the current sprint and indicate by editing the percentage of availability of each resource

(opt.) re-toggle the

click on submit

of the sprint





sprint will probably be edited several times by different people and will go through a complete

ee states:

sprint is currently running

sprint if finished

In the tree, select a sprint

on the right panel (details tab), ed





on the right panel, select the Resources

select filter button







will probably be edited several times by different people and will go through a complete

sprint is currently running

Table 6 - Sprint





Resources tab

button to display the complete user tree


select filter button to





Sprint Status

it the information you wish and submit



Allocate some resources to a sprintAll the tasks associated to a sprint will be performed by a pool of resources. These resources are users (taken from the user tree). To allocate some resources to a sprint:

tab

to display the complete user tree


to display only the selected users







rint All the tasks associated to a sprint will be performed by a pool of resources. These resources are users (taken from the user tree). To allocate some resources to a sprint:


check all the users that need to be allocated to the current sprint and indicate by editing the

display only the selected users

enter the description of the sprint. You can use the formatting tools (wiki-style) to format

select the status of the sprint (at creation time, you can only choose Idle or Running




All the tasks associated to a sprint will be performed by a pool of resources. These resources are



display only the selected users

style) to format

Running)



All the tasks associated to a sprint will be performed by a pool of resources. These resources are


Note: You can check if some of the resources are overloaded by checking their calendars from the user tree.

3.6.6 Associate A sprint will contain some tasks

• in the tree, select the


• un-toggle the

• check all the

• (opt.) re

• click on submit

You can check if some of the resources are overloaded by checking their calendars from the user tree.

Associate sprint will contain some tasks

n the tree, select the



check all the tasks


click on submit

You can check if some of the resources are overloaded by checking their calendars from the

Associate some taskssprint will contain some tasks. To associate

n the tree, select the sprint

on the right panel, select the Backlog


tasks that need to be

the select filter


some tasks to a sprint. To associate some tasks

Backlog (this is the terminology in Scrum)

button to display the complete

that need to be associated

select filter button to display only the selected


a sprint some tasks to one

(this is the terminology in Scrum)

to display the complete

associated to the current

to display only the selected


one sprint:

(this is the terminology in Scrum)

to display the complete task tree

to the current sprint

to display only the selected


(this is the terminology in Scrum) tab

tree

to display only the selected tasks


3.6.7 Daily update progress of the tasks of a sprintOn a daily basis, you can update the progress of the tasks in a sprint:

• in the tree, select the sprint


• move the progress bar of each task. While you’re moving the sliders:

• click on submit

3.6.8 See the velocity charts/check the status of the sprint• in the tree, select the sprint


• some graph are displayed showing several useful information:

Daily update progress of the tasks of a sprintOn a daily basis, you can update the progress of the tasks in a sprint:



move the progress bar of each task. While you’re moving the sliders:o the percentage of progress is update in the next columno the equivalent in days is updated in the next columno the last column indicates the esti

click on submit

See the velocity charts/check the status of the sprintin the tree, select the sprint


some graph are displayed showing several useful information:



on the right panel, select the Backlog

move the progress bar of each task. While you’re moving the sliders:the percentage of progress is update in the next columnthe equivalent in days is updated in the next columnthe last column indicates the esti

See the velocity charts/check the status of the sprintin the tree, select the sprint

on the right panel, select the Velocity



Backlog tab

move the progress bar of each task. While you’re moving the sliders:the percentage of progress is update in the next columnthe equivalent in days is updated in the next columnthe last column indicates the estimated number of days for this task

See the velocity charts/check the status of the sprint

Velocity tab



move the progress bar of each task. While you’re moving the sliders:the percentage of progress is update in the next columnthe equivalent in days is updated in the next column

mated number of days for this task




move the progress bar of each task. While you’re moving the sliders:the percentage of progress is update in the next column the equivalent in days is updated in the next column




Daily update progress of the tasks of a sprint

move the progress bar of each task. While you’re moving the sliders:


See the velocity charts/check the status of the sprintSee the velocity charts/check the status of the sprint

The top graph shows:

• the theoretical curve of progress

• the cumulated breakdown of all the tasks in this sprint The bottom graph shows:

• the theoretical curve of progress

• the two curves representing the deal (top blue linrepresenting what we can do theoretically with the resources allocated

• the status of the project:

graph shows:

the theoretical curve of progress

the cumulated breakdown of all the tasks in this sprint

he bottom graph shows:


the two curves representing the deal (top blue linrepresenting what we can do theoretically with the resources allocated

the status of the project:o Red area means that the project is at risko Green means that the project is in a good shape



he bottom graph shows:



the status of the project: area means that the project is at risk

means that the project is in a good shape

the theoretical curve of progress (the dashed red line)


the theoretical curve of progress (the dashed red line)


area means that the project is at riskmeans that the project is in a good shape

(the dashed red line)


(the dashed red line)

the two curves representing the deal (top blue line) and real (bottom blue line) curves representing what we can do theoretically with the resources allocated

area means that the project is at risk means that the project is in a good shape

e) and real (bottom blue line) curves representing what we can do theoretically with the resources allocated

means that the project is in a good shape

e) and real (bottom blue line) curves representing what we can do theoretically with the resources allocated

e) and real (bottom blue line) curves

3.7 TestHere is a typica

• the total number of tests and testcases

• the number of tests and testcases in each category

• the number of tests and testcases in each folder

This screen is a bit different from the others since the left panel includes 2 separate areas:

• the usual tree including all the tests that we have on the system

• a subtest

Tests can be arranged by placing them in specific folders. For instance, the tests can be organized the same way as the specificationto have one test per function/methodyour test suite by adding stress test or negative tests etc. Tests and testcases are obviously what is the most important in the Data Model definition. The normal process is to check that specifications are all properly functioning.

Test TreeHere is a typical test tree. It immediately shows a number of useful information:

the total number of tests and testcases

the number of tests and testcases in each category

the number of tests and testcases in each folder


he usual tree including all the tests that we have on the system

sub-tree on the bottom that will list the testcases corresponding to the currently selected est

Tests can be arranged by placing them in specific folders. For instance, the tests can be organized the same way as the specificationto have one test per function/methodyour test suite by adding stress test or negative tests etc.

Tests and testcases are obviously what is the most important in the Data Model definition. The normal process is to start from specifications and make as many tests and testcases to check that specifications are all properly functioning.

Tree l test tree. It immediately shows a number of useful information:






tree on the bottom that will list the testcases corresponding to the currently selected

Tests can be arranged by placing them in specific folders. For instance, the tests can be organized the same way as the specifications. But to have one test per function/methodyour test suite by adding stress test or negative tests etc.

Tests and testcases are obviously what is the most important in the Data Model definition. The to start from specifications and make as many tests and testcases

to check that specifications are all properly functioning.

l test tree. It immediately shows a number of useful information:




Figure 9 - Test Tree




Tests can be arranged by placing them in specific folders. For instance, the tests can be organized But if you’re testing a software API, it’s a common way of doing

to have one test per function/method and group theyour test suite by adding stress test or negative tests etc.






Test Tree




Tests can be arranged by placing them in specific folders. For instance, the tests can be organized f you’re testing a software API, it’s a common way of doing

and group these functions by groupsyour test suite by adding stress test or negative tests etc. so probably need additional folders.








se functions by groupsso probably need additional folders.






se functions by groups. You can then so probably need additional folders.

Tests and testcases are obviously what is the most important in the Data Model definition. The to start from specifications and make as many tests and testcases as necessary




You can then extend so probably need additional folders.

Tests and testcases are obviously what is the most important in the Data Model definition. The necessary



• on the right panel, click on t

• a dialog box

• fill the

• fill theuse the formatting tools (wikicorrectly formatted.

• Pick one user in the

• click on submit


3.7.2 Associate a test to specificationsA test is probablyspecifications:

• in the tree, select the test

• on the right panel, select the

• un-toggle the

• check all the specification that need to be associated to the current test

• (opt.) re

• click on submit

3.7.3 Create a We already mentioned that, for instance, a test could verify a specific function of an API. But there are a lot of parameters One testcase must be able to check one specific function in some particular conditions. The sum of all the testcases makes one test. To have a test succeeding, all the testcase must succeed. To create a testcase:

• in the tree, select a test

• on the r

• a dialog box

Create a testTo create a test:


on the right panel, click on t

a dialog box including three tabs

fill the Details tab with

fill the Testplan use the formatting tools (wikicorrectly formatted.

Pick one user in the

click on submit

immediately, the

Associate a test to specificationsprobably coming from at least one specification. To associate a test to one or several

specifications:

n the tree, select the test

on the right panel, select the


check all the specification that need to be associated to the current test


click on submit

Create a testcaseWe already mentioned that, for instance, a test could verify a specific function of an API. But there

of things to check to validate one single function. You may want to test all combination of and check that the result is cor

One testcase must be able to check one specific function in some particular conditions. The sum of all the testcases makes one test. To have a test succeeding, all the testcase must succeed.

To create a testcase:

n the tree, select a test


a dialog box including two

test



including three tabs

tab with the name and priority

tab with the prerequisites and the general description of the tesuse the formatting tools (wiki-correctly formatted.

Pick one user in the Author tab that will be

immediately, the test appears in the tree

Associate a test to specificationscoming from at least one specification. To associate a test to one or several

n the tree, select the test

on the right panel, select the Specifications



the select filter

testcase We already mentioned that, for instance, a test could verify a specific function of an API. But there

things to check to validate one single function. You may want to test all combination of check that the result is cor


n the tree, select a test

ight panel, click on the

including two tabs is


he create test

including three tabs is displayed

name and priority

with the prerequisites and the general description of the tes-style) to format the text. Later, in reports this text will appear

tab that will be

rs in the tree

Associate a test to specificationscoming from at least one specification. To associate a test to one or several

Specifications

button to display the complete specification tree


select filter button to display only the selected specifications

We already mentioned that, for instance, a test could verify a specific function of an API. But there

things to check to validate one single function. You may want to test all combination of check that the result is correct.


ight panel, click on the create testcase

tabs is displayed


button

displayed

name and priority of the test

with the prerequisites and the general description of the tesstyle) to format the text. Later, in reports this text will appear

tab that will be registered as the author or the test.

Associate a test to specifications coming from at least one specification. To associate a test to one or several

Specifications tab

to display the complete specification tree


to display only the selected specifications

We already mentioned that, for instance, a test could verify a specific function of an API. But there things to check to validate one single function. You may want to test all combination of


testcase button

displayed

of the test (leave the canonical path blank)

with the prerequisites and the general description of the tesstyle) to format the text. Later, in reports this text will appear

as the author or the test.

coming from at least one specification. To associate a test to one or several






(leave the canonical path blank)

with the prerequisites and the general description of the test. You can style) to format the text. Later, in reports this text will appear

as the author or the test.







(leave the canonical path blank).

t. You can style) to format the text. Later, in reports this text will appear





• fill the within a testtools (wikiDo not forget to check the executed when running a campaign. In case of maImplemented

• selecttestcase:

• click on submit

• immediately, the test

3.7.4 Mofify the testplan of a testcaseTo modify the testplan of a test


• in the sub

• on the right panel (

• click on

• apply the changes and submit

fill the Details tab with the within a test), nametools (wiki-style) to format the text. Later, in reports this text will appear correctly formatted.Do not forget to check the executed when running a campaign. In case of maImplemented checkbox.

select the Testplantestcase:

o add a step� in the tree, select the root folder

� click on the � enter the description of t

o add parameters (opt)� in the tree, select the � click on the � enter the description of the � repeat the operation if you

o add checks (opt.):� in the� click on � click on the new operator and click on the � enter the description of the check and submit� repeat the operation if you need to specify more checks (you

many o repeat the operation

click on submit

immediately, the test

Mofify the testplan of a testcaseTo modify the testplan of a test

in the tree, select a test

in the sub-tree, select a testcase

on the right panel (

click on the edit a node

apply the changes and submit

tab with the index (defining the order in which the testcases will be executed), name and general description of the testca

style) to format the text. Later, in reports this text will appear correctly formatted.Do not forget to check the executed when running a campaign. In case of ma

checkbox.

Testplan tab and define all the steps and checks that will be needed in this

add a step: in the tree, select the root folder

click on the create enter the description of t

add parameters (opt)in the tree, select the click on the create enter the description of the repeat the operation if you

add checks (opt.): in the tree, select the click on one of the click on the new operator and click on the enter the description of the check and submitrepeat the operation if you need to specify more checks (youmany different b

repeat the operation

immediately, the testcase appears in the

Mofify the testplan of a testcaseTo modify the testplan of a testcase:


tree, select a testcase

on the right panel (Testplan tab), select the node in the tree you wish to modify

edit a node button


index (defining the order in which the testcases will be executedand general description of the testca

style) to format the text. Later, in reports this text will appear correctly formatted.Do not forget to check the Implementedexecuted when running a campaign. In case of ma

and define all the steps and checks that will be needed in this

in the tree, select the root folder

create step button enter the description of the step and submit

add parameters (opt): in the tree, select the parameters

create parameterenter the description of the repeat the operation if you

, select the checksone of the create

click on the new operator and click on the enter the description of the check and submitrepeat the operation if you need to specify more checks (you

different boolean operatorrepeat the operation for every step

appears in the sub

Mofify the testplan of a testcase

tree, select a testcase

tab), select the node in the tree you wish to modify

button


index (defining the order in which the testcases will be executedand general description of the testca

style) to format the text. Later, in reports this text will appear correctly formatted.Implemented checkbox. Non

executed when running a campaign. In case of ma



button he step and submit

parameters node parameter button

enter the description of the parameter and submitrepeat the operation if you need to specify more parameters

checks node boolean operators

click on the new operator and click on the enter the description of the check and submitrepeat the operation if you need to specify more checks (you

oolean operators as you want)for every step and submit

sub-tree on the left panel

Mofify the testplan of a testcase


index (defining the order in which the testcases will be executedand general description of the testcase. You can use the formatting

style) to format the text. Later, in reports this text will appear correctly formatted.checkbox. Non-implemented test are NOT

executed when running a campaign. In case of manual test, always check the


he step and submit

node

and submit need to specify more parameters

boolean operators buttons click on the new operator and click on the create checkenter the description of the check and submit repeat the operation if you need to specify more checks (you

as you want) and submit

tree on the left panel


index (defining the order in which the testcases will be executedYou can use the formatting

style) to format the text. Later, in reports this text will appear correctly formatted.implemented test are NOT

nual test, always check the


need to specify more parameters

buttons check button

repeat the operation if you need to specify more checks (you can mix as


index (defining the order in which the testcases will be executed You can use the formatting

style) to format the text. Later, in reports this text will appear correctly formatted. implemented test are NOT

nual test, always check the


can mix as

3.8 Campaign TreeHere is a typical campaign

• the total number of

• the number of

• the number of

• the status (stopped,overlay on the icon)

• the start and stop date and time of each campaign session

Once all the tests have been defined and implemented, yhave to gather all the tests you which to run in a campaign. For instance, it may be of interest to define a campaign including all the tests of a specific category (or just a subset). A campaign is by definition just an At this stage, you would be able to run a campaign but what happens if you run a campaign several times? of course you want to be able to retrieve results from each runs of a campaign. Here comes the Campaign Session. You can create from a campaign as many campaign sessions as you want. This allows to archive independently all the results and report of each execution of the tests.

Campaign TreeHere is a typical campaign

the total number of

the number of campaigns and campaign sessions

the number of campaigns and campaign sessions

the status (stopped,overlay on the icon)

the start and stop date and time of each campaign session

Once all the tests have been defined and implemented, yhave to gather all the tests you which to run in a campaign. For instance, it may be of interest to define a campaign including all the tests of a specific category (or just a subset). A campaign is by

just an ordered list of tests

At this stage, you would be able to run a campaign but what happens if you run a campaign several times? of course you want to be able to retrieve results from each runs of a campaign. Here comes the Campaign Session.

can create from a campaign as many campaign sessions as you want. This allows to archive independently all the results and report of each execution of the tests.

Campaign Tree Here is a typical campaign tree. It immediately shows a number of useful information:

the total number of campaigns

campaigns and campaign sessions


the status (stopped, paused, running, idle) of each campaign session (indicated by the overlay on the icon)


Figure


ordered list of tests.

At this stage, you would be able to run a campaign but what happens if you run a campaign several times? of course you want to be able to retrieve results from each runs of a campaign. Here comes


tree. It immediately shows a number of useful information:




paused, running, idle) of each campaign session (indicated by the


Figure 10 - Campaign Tree





campaign sessions

campaigns and campaign sessions in each category

campaigns and campaign sessions in each folder



Campaign Tree

Once all the tests have been defined and implemented, you have to run them. To do so, you’ll first have to gather all the tests you which to run in a campaign. For instance, it may be of interest to define a campaign including all the tests of a specific category (or just a subset). A campaign is by




in each category

in each folder



Campaign Tree

ou have to run them. To do so, you’ll first have to gather all the tests you which to run in a campaign. For instance, it may be of interest to define a campaign including all the tests of a specific category (or just a subset). A campaign is by







can create from a campaign as many campaign sessions as you want. This allows to archive




can create from a campaign as many campaign sessions as you want. This allows to archive


• in the tree, select a folder (create one if necessar


• a dialog box including

• fill the

• in the

• click on submit


3.8.2 Order the tests in the campaign• in the tree, select the


• select one or several tests in the list and usetest(s) wherever

• click on submit

Create a campaignTo create a campaign:

in the tree, select a folder (create one if necessar


a dialog box including

fill the Details tab with the name

the Content tab

click on submit

immediately, the

Order the tests in the campaignin the tree, select the


select one or several tests in the list and usetest(s) wherever

click on submit

campaign




tab with the name

tab, select all the tests you want to be part of this

immediately, the campaign appears in the tree

Order the tests in the campaignin the tree, select the campaign

on the right panel, select the Order

select one or several tests in the list and use you want in the list

campaign


on the right panel, click on the create campaign

tabs is displayed

tab with the name of the campaign

, select all the tests you want to be part of this

appears in the tree

Order the tests in the campaigncampaign

Order tab

select one or several tests in the list and useyou want in the list


campaign icon

displayed

the campaign

, select all the tests you want to be part of this

appears in the tree

Order the tests in the campaign

select one or several tests in the list and use the move buttons

, select all the tests you want to be part of this campaign

move buttons

campaign

to position the

to position the

3.8.3 Create a campaign sessionTo create a campaign session

• in the tree, select a campaign


• a dialog box including seven

• fill the

• (opt.)

• select the the tests on the local host, leahost)

• select the

• select the involved in this campaign session. purpose) to change the configurations associated.

Create a campaign sessionTo create a campaign session

in the tree, select a campaign


a dialog box including seven

fill the Details tab with the

(opt.) select the Test operator

select the Agentthe tests on the local host, leahost)

select the SUT tab and pick the SUT on which the session will be run

select the Configurationinvolved in this campaign session. purpose) to change the configurations associated.

Create a campaign sessionTo create a campaign session:



a dialog box including seven tabs is

tab with the name of the session

Test operator

Agent tab and pick the agent on which the session will be runthe tests on the local host, lea

tab and pick the SUT on which the session will be run

Configuration tab and pick the configuration you which for each category involved in this campaign session. purpose) to change the configurations associated.

Create a campaign session


on the right panel, click on the create campaign session

tabs is displayed

ame of the session

Test operator tab and pick the user who will run the session

tab and pick the agent on which the session will be runthe tests on the local host, leave the default selection (that should already match the local


tab and pick the configuration you which for each category involved in this campaign session. Once a campaign session is created, it is impossible (by purpose) to change the configurations associated.

Create a campaign session

campaign session

displayed

ame of the session.

tab and pick the user who will run the session

tab and pick the agent on which the session will be runve the default selection (that should already match the local


tab and pick the configuration you which for each category Once a campaign session is created, it is impossible (by

purpose) to change the configurations associated. If no configuration are available:

campaign session button


tab and pick the agent on which the session will be runve the default selection (that should already match the local



If no configuration are available:


tab and pick the agent on which the session will be run. If you wish to run ve the default selection (that should already match the local




. If you wish to run ve the default selection (that should already match the local



• (opt.) if needed, modify the dynamic attributes values in the

• (opt.) select the campaign session will be completed

• click on submit


3.8.4 Run a campaign sessionTo run a campaign session

• in the tree, select a campaig


• immediately, the Test campaign details screen appears and will display real time the results of testing

• If the campaign includes tests to be executed manually (the tests are part of one or severcategories where you choose get additional dialog boxes such as:

o click on the o a dialog box is o enter the name of the configurationo fill in all the forms displayed and submito the launchers (xml and jar files) needed for this campaign session MUST be

accessible in the bin/launchers folder

(opt.) if needed, modify the dynamic attributes values in the

(opt.) select the campaign session will be completed

click on submit

immediately, the

Run a campaign sessionrun a campaign session

in the tree, select a campaig

on the right panel

immediately, the Test campaign details screen appears and will display real time the results of testing

If the campaign includes tests to be executed manually (the tests are part of one or severcategories where you choose get additional dialog boxes such as:

click on the create configurationa dialog box is displayedenter the name of the configuration

ll the forms displayed and submitthe launchers (xml and jar files) needed for this campaign session MUST be accessible in the bin/launchers folder


(opt.) select the CC Emails tabcampaign session will be completed

immediately, the campaign session

Run a campaign sessionrun a campaign session:

in the tree, select a campaign session

on the right panel, click on the start button


If the campaign includes tests to be executed manually (the tests are part of one or severcategories where you choose get additional dialog boxes such as:

create configuration displayed

enter the name of the configurationll the forms displayed and submit

the launchers (xml and jar files) needed for this campaign session MUST be accessible in the bin/launchers folder


tab and check some users to receive a notification when the campaign session will be completed

campaign session appears in the

Run a campaign session

n session

click on the start button

immediately, the Test campaign details screen appears and will display real time the

If the campaign includes tests to be executed manually (the tests are part of one or severcategories where you choose manual.jar or get additional dialog boxes such as:

button

enter the name of the configuration ll the forms displayed and submit

the launchers (xml and jar files) needed for this campaign session MUST be accessible in the bin/launchers folder


and check some users to receive a notification when the

appears in the tree in idle state

click on the start button


If the campaign includes tests to be executed manually (the tests are part of one or severor simple_manual.jar

the launchers (xml and jar files) needed for this campaign session MUST be

(opt.) if needed, modify the dynamic attributes values in the Attributes


tree in idle state


If the campaign includes tests to be executed manually (the tests are part of one or seversimple_manual.jar as launcher), then you


Attributes tab



If the campaign includes tests to be executed manually (the tests are part of one or severas launcher), then you




If the campaign includes tests to be executed manually (the tests are part of one or several as launcher), then you will

3.8.5 See the To see the details

• in the tree, select a campaign session

• on t

• the screen is split in three different areas

See the executiondetails of the campaign session execution:


on the right panel

the screen is split in three different areaso a test tree showing the tests included in the campaign with their results

number of useful information:� the total number of tests that succeeded or failed

� the number of tests that succeeded or failed� the number of tests that succeeded or failed

o a testcase sub

executionof the campaign session execution:


he right panel, select the Content

the screen is split in three different areasa test tree showing the tests included in the campaign with their resultsnumber of useful information:

the total number of tests that succeeded or failed success failed unknown

the number of tests that succeeded or failedthe number of tests that succeeded or failed

a testcase sub-tree showing success failed

execution details of the campaign session execution:


Content tab

the screen is split in three different areas a test tree showing the tests included in the campaign with their resultsnumber of useful information:

the total number of tests that succeeded or failed

unknown the number of tests that succeeded or failedthe number of tests that succeeded or failed

showing the result of each testcase

of the campaign session execution:

a test tree showing the tests included in the campaign with their results


the number of tests that succeeded or failedthe number of tests that succeeded or failed

the result of each testcase

a test tree showing the tests included in the campaign with their results


the number of tests that succeeded or failed in each categorythe number of tests that succeeded or failed in each folder

the result of each testcase

a test tree showing the tests included in the campaign with their results. It

in each category in each folder

It shows a

The process to get all the details of an execution is the following:

• click on

• the testcase sub

• click on

• the message area show the details

3.8.6 Get the resultsTo see the results of the campaign session execution:

• in the t


The screen is split in two columns:

• the

• the Each column

• in the header tables:

• in the pie charts:

3.8.7 Check the progression of a campaignA Statisticscampaign. The information the results are put in a graph so that the evolution (progression or regression) in time is clvisible. The last session's results are also displayed.that shows the evolution of

o a message area


click on a test

the testcase sub

click on a testcase

the message area show the details

Get the resultsTo see the results of the campaign session execution:


on the right panel


the Tests column gives the statistics/results only based on the tests results

the Testcases column

Each column immediately shows a number of useful information:

in the header tables:o the percentage of success, failure etc. of tests/testcaseso the coverage of the execution (based on the number of tests/testcases that were

not execut

in the pie charts:o the number of success, failure etc. of tests/testcaseso the percentage of success and failure (after removal of the unknown, relative or not

executed tests/testcases)

Check the progression of a campaignStatistics tab is present on

The information the results are put in a graph so that the evolution (progression or regression) in time is clvisible. The last session's results are also displayed.that shows the evolution of

not executed relative (somethat will need to be analyzed by an operator)

a message area showing the details of execution of one specific testcase


the testcase sub-tree is updated showing the associated testcases results

a testcase

the message area show the details

Get the results To see the results of the campaign session execution:

ree, select a campaign session

on the right panel, select the Results


column gives the statistics/results only based on the tests results

column gives the statistics/results only based on

immediately shows a number of useful information:

in the header tables: the percentage of success, failure etc. of tests/testcasesthe coverage of the execution (based on the number of tests/testcases that were not executed)

in the pie charts: the number of success, failure etc. of tests/testcasesthe percentage of success and failure (after removal of the unknown, relative or not executed tests/testcases)

Check the progression of a campaigntab is present on any campaign

The information is taken from all the the results are put in a graph so that the evolution (progression or regression) in time is clvisible. The last session's results are also displayed.that shows the evolution of tests results and another one going deeper at the

not executed (some tests –

that will need to be analyzed by an operator)showing the details of execution of one specific testcase


tree is updated showing the associated testcases results

the message area show the details of each step during the testcase execution

To see the results of the campaign session execution:

ree, select a campaign session

Results tab


gives the statistics/results only based on


the percentage of success, failure etc. of tests/testcasesthe coverage of the execution (based on the number of tests/testcases that were

the number of success, failure etc. of tests/testcasesthe percentage of success and failure (after removal of the unknown, relative or not executed tests/testcases)

Check the progression of a campaigncampaign. This tab shows

taken from all the sessions the results are put in a graph so that the evolution (progression or regression) in time is clvisible. The last session's results are also displayed.

results and another one going deeper at the

– i.e. performances that will need to be analyzed by an operator)

showing the details of execution of one specific testcase



of each step during the testcase execution

To see the results of the campaign session execution:


gives the statistics/results only based on


the percentage of success, failure etc. of tests/testcasesthe coverage of the execution (based on the number of tests/testcases that were

the number of success, failure etc. of tests/testcasesthe percentage of success and failure (after removal of the unknown, relative or not

Check the progression of a campaign. This tab shows

sessions executed belonging to the campaign. All the results are put in a graph so that the evolution (progression or regression) in time is clvisible. The last session's results are also displayed. The new tab is split in 2 tabbed panes: one

results and another one going deeper at the

i.e. performances - may just return some values that will need to be analyzed by an operator)






gives the statistics/results only based on the testcases results


the percentage of success, failure etc. of tests/testcases the coverage of the execution (based on the number of tests/testcases that were

the number of success, failure etc. of tests/testcases the percentage of success and failure (after removal of the unknown, relative or not

Check the progression of a campaign . This tab shows the progression/

executed belonging to the campaign. All the results are put in a graph so that the evolution (progression or regression) in time is cl

The new tab is split in 2 tabbed panes: one results and another one going deeper at the

may just return some values





the testcases results

the coverage of the execution (based on the number of tests/testcases that were

the percentage of success and failure (after removal of the unknown, relative or not

the progression/regression of this executed belonging to the campaign. All

the results are put in a graph so that the evolution (progression or regression) in time is clThe new tab is split in 2 tabbed panes: one

results and another one going deeper at the testcase level:

may just return some values


the testcases results

the coverage of the execution (based on the number of tests/testcases that were

the percentage of success and failure (after removal of the unknown, relative or not

regression of this executed belonging to the campaign. All

the results are put in a graph so that the evolution (progression or regression) in time is clearly The new tab is split in 2 tabbed panes: one

level:

3.9 DefectHere is a typical defect tree. It imme

• the total number of

• the number of

• the number of

• the status of each defect (indicated by the color of the icon)

• the severity of each specification (indicat

• the priority of each specification (indicated by the

Defect TreeHere is a typical defect tree. It imme

the total number of

the number of defects

the number of defects

the status of each defect (indicated by the color of the icon)

the severity of each specification (indicat


Tree Here is a typical defect tree. It immediately shows a number of useful information:

the total number of defects

defects in each category

defects in each folder


the severity of each specification (indicat


diately shows a number of useful information:

in each category

in each folder


the severity of each specification (indicated by the


Figure 11 - Defect Tree



ed by the column)

the priority of each specification (indicated by the column)

Defect Tree



column)

column)


Executing some tests (running some campaign session) makes you able to generate reports. It’s good to have a static viewtests that failed to actual defectsdefect. At this point, aassociate all

3.9.1 Create a defectTo create a defect:



• a dialog box

• fill the operating system, status, severity and priority

• pick one user in the the defect

• in the

• click on submit

• immediately, the defect appears in the tree

3.9.2 Edit a The defect will probably be edited several times by different people and will go through a cworkflow including five Overlay

New

Assigned

Ack

Resolved

Closed

To edit a defect

Executing some tests (running some campaign session) makes you able to generate reports. It’s good to have a static viewtests that failed to actual defects

At this point, a report analysis must be done by the test operator. Thiall failed testcases to

Create a defectTo create a defect:



a dialog box including three tabs

fill the Details tab with the name, description, steps to reproduce, reproducibility, platform, operating system, status, severity and priority

pick one user in the e defect

in the Found in

click on submit

immediately, the defect appears in the tree

Edit a defectwill probably be edited several times by different people and will go through a c

workflow including five states:

Represents

New defect

The defect has been assigned to a person to resolve it

The defect is being

The defect has been declared as resolved

The fix has been veri

defect:

Executing some tests (running some campaign session) makes you able to generate reports. It’s good to have a static view of what is working and what is nottests that failed to actual defects. Hence

report analysis must be done by the test operator. Thitestcases to some

Create a defect



including three tabs

tab with the name, description, steps to reproduce, reproducibility, platform, operating system, status, severity and priority

pick one user in the Assigned to

tab, check all the SUTs on which this defect can be observed


defect will probably be edited several times by different people and will go through a c

states:

has been assigned to a person to resolve it

is being investigated

defect has been declared as resolved

The fix has been verified and the

Executing some tests (running some campaign session) makes you able to generate reports. It’s of what is working and what is not

Hence, several failing testcases may be due to only one single

report analysis must be done by the test operator. Thisome defects.


on the right panel, click on the create defect

including three tabs is displayed


Assigned to tab who will be registered as the one assigned to resolve



will probably be edited several times by different people and will go through a c


investigated

defect has been declared as resolved

fied and the defect has been closed

Table 7 - Defect Status

Executing some tests (running some campaign session) makes you able to generate reports. It’s of what is working and what is not but it would be even better to link the

, several failing testcases may be due to only one single

report analysis must be done by the test operator. Thi


defect button

displayed


tab who will be registered as the one assigned to resolve





has been closed

Defect Status

Executing some tests (running some campaign session) makes you able to generate reports. It’s but it would be even better to link the


report analysis must be done by the test operator. This analysis should lead to

tab with the name, description, steps to reproduce, reproducibility, platform,






s analysis should lead to







s analysis should lead to





• on the right panel (details tab), edit the information you wish and submit Some fields will be accessible only when a cert Assigned: Correction target date Ack: Correction target versionCompletion Resolved/ClosedCorrection typeCorrection descriptionCorrection patches

Note: For better tracking purposes, when setting a defect’s status to one SUT in the

3.9.3 Link a failed test to a defectTo link a failed test to a defect:

• switch to the



• select a tes

• click on the

• a dialog box is

• un-toggle the

• check all the

• (opt.)

• click on submit



Some fields will be accessible only when a cert

Correction target date

Correction target version %

Resolved/Closed: Correction type Correction description Correction patches

For better tracking purposes, when setting a defect’s status to one SUT in the Fixed in

Link a failed test to a defectTo link a failed test to a defect:

switch to the Campaigns


on the right panel

select a test with status failed or unknown

click on the Link to a defect



check all the defects


click on submit

In the tree, select a defect


Some fields will be accessible only when a cert

Correction target version

For better tracking purposes, when setting a defect’s status to Fixed in tab.

Link a failed test to a defectTo link a failed test to a defect:

Campaigns tab on the left panel


on the right panel, select the Content

with status failed or unknown

Link to a defect button

displayed


defects that need to be associated to the

oggle the select filter


Some fields will be accessible only when a certain status is reached:

For better tracking purposes, when setting a defect’s status to

Link a failed test to a defect

tab on the left panel


Content tab

with status failed or unknown

button

button to display the complete

that need to be associated to the

select filter button to display only the selected requirement


ain status is reached:

For better tracking purposes, when setting a defect’s status to

Link a failed test to a defect


to display the complete

that need to be associated to the test execution

to display only the selected requirement


ain status is reached:

For better tracking purposes, when setting a defect’s status to Resolved

to display the complete defect tree

test execution



olved, you should also pick

tree

test execution


, you should also pick


4. Getting

4.1 LocalizationXStudio is entirely localized. There are currently 4 languages supported:

• English

• French

• Italian

• Spanish To have XStudio running in a specific language, you just need to set your profile with one on those four languages

At the next login, the applicatio

Getting more into the d

LocalizationXStudio is entirely localized. There are currently 4 languages supported:

English

French

Italian (partially)

Spanish (partially

To have XStudio running in a specific language, you just need to set your profile with one on those four languages:

t the next login, the applicatio

more into the d

Localization XStudio is entirely localized. There are currently 4 languages supported:

(partially)

rtially)

To have XStudio running in a specific language, you just need to set your profile with one on those

t the next login, the application will show up appropriately localized:

more into the d

XStudio is entirely localized. There are currently 4 languages supported:


n will show up appropriately localized:

more into the details




etails






You can also override this setting during login b

4.2 InternationalizationA user is given a language (localization) which is used to display the application with a specific language but is also associated with a location (internationalization) which is used to know which public holidays and week Each country can be easily configured: public holidays can be addition, each country is associated to some weekthe world are using Qatar, Algeria etc.) are using Thursday and

The default settings are supposed to be correct but it's customizes it if necessary. These settings are accessible through the

Hence, all the calendars are affected by this change as each user may have different

Absences are also inclustaff workload, s


InternationalizationA user is given a language (localization) which is used to display the application with a specific language but is also associated with a location (internationalization) which is used to know which

holidays and week

Each country can be easily configured: public holidays can be ddition, each country is associated to some week

are using Saturday Qatar, Algeria etc.) are using

and Friday.



are also inclustaff workload, status are then easier to figure out.


InternationalizationA user is given a language (localization) which is used to display the application with a specific language but is also associated with a location (internationalization) which is used to know which

holidays and week-ends this user will benefit from.


Saturday and Sunday Qatar, Algeria etc.) are using Friday



are also included in the calendars so you have a complete picture of the ptatus are then easier to figure out.

You can also override this setting during login by forcing a specific language

Internationalization A user is given a language (localization) which is used to display the application with a specific language but is also associated with a location (internationalization) which is used to know which

ends this user will benefit from.


Sunday for the week and Saturday



ded in the calendars so you have a complete picture of the ptatus are then easier to figure out.

forcing a specific language

A user is given a language (localization) which is used to display the application with a specific language but is also associated with a location (internationalization) which is used to know which

ends this user will benefit from.

Each country can be easily configured: public holidays can be ddition, each country is associated to some week-ends settings. Hence, most of the countries in

for the week-ends but some others (such as Israel, Saturday and again some others (such as Saudi Arabia)

The default settings are supposed to be correct but it's good to let the administrator of the system customizes it if necessary. These settings are accessible through the


ded in the calendars so you have a complete picture of the p

forcing a specific language:


Each country can be easily configured: public holidays can be added, edited ends settings. Hence, most of the countries in

ends but some others (such as Israel, and again some others (such as Saudi Arabia)

good to let the administrator of the system customizes it if necessary. These settings are accessible through the Settings


ded in the calendars so you have a complete picture of the p

:


edited and deletedends settings. Hence, most of the countries in


good to let the administrator of the system Settings menu entry.

Hence, all the calendars are affected by this change as each user may have different week

ded in the calendars so you have a complete picture of the projects or the


deleted. In ends settings. Hence, most of the countries in


good to let the administrator of the system menu entry.

week-ends.

rojects or the

Note that the calendar tree is still expandable you want to know the details about why a user is overloaded in a certain time frame. A legend (including some

4.3 Change TrackingXStudio allows tracking any changes on the database. This feature is particularly useful to track modifications that occurred on:

• requirements

• specifications

• tests/testcases

• defects To check the history of an element, click on it and select the panel shows a table gathering all the dated changes. Here are for instance changes you could see on a defect:

Note: You can edit directly the details of a user by clicking on his name in the changes table.

Week-ends and holidays are easily identifiable as they are in black and grey

Note that the calendar tree is still expandable you want to know the details about why a user is overloaded in a certain time frame.

A legend (including some

Change TrackingStudio allows tracking any changes on the database. This feature is particularly useful to track

modifications that occurred on:

requirements

specifications

tests/testcases

defects

To check the history of an element, click on it and select the panel shows a table gathering all the dated changes. Here are for instance changes you could see on a defect:

You can edit directly the details of a user by clicking on his name in the changes table.

ends and holidays are easily identifiable as they are in black and grey

Note that the calendar tree is still expandable you want to know the details about why a user is overloaded in a certain time frame.

A legend (including some gradient colors for the workload) has

Change TrackingStudio allows tracking any changes on the database. This feature is particularly useful to track

modifications that occurred on:

To check the history of an element, click on it and select the panel shows a table gathering all the dated changes. Here are for instance changes you could see



Note that the calendar tree is still expandable as usual. This greatly facilitates the reading i.e. when you want to know the details about why a user is overloaded in a certain time frame.

colors for the workload) has

Change Tracking Studio allows tracking any changes on the database. This feature is particularly useful to track

To check the history of an element, click on it and select the panel shows a table gathering all the dated changes. Here are for instance changes you could see



as usual. This greatly facilitates the reading i.e. when you want to know the details about why a user is overloaded in a certain time frame.

colors for the workload) has

Studio allows tracking any changes on the database. This feature is particularly useful to track

To check the history of an element, click on it and select the Changespanel shows a table gathering all the dated changes. Here are for instance changes you could see




colors for the workload) has been added to help the reading


Changes tab panel shows a table gathering all the dated changes. Here are for instance changes you could see




been added to help the reading


on the right panel.panel shows a table gathering all the dated changes. Here are for instance changes you could see


as usual. This greatly facilitates the reading i.e. when

been added to help the reading.


on the right panel. The panel shows a table gathering all the dated changes. Here are for instance changes you could see


4.4 Testing CoveragOne of the major testing. As you’ve already seen in previous chapters, requirements are linked to specifications and specifications are linked to tes Those metrics are computed per category and are retrievable from requirements, specifications and tests.

4.4.1 GlobalTo get global requirements traceability

• switch to the

• in the tree, select the root folder


• the requirement tree appears including in the right column, all the specifications covering each requiremen

This traceability matrix is also present in the requirement book (that can be generated from XStudio).

4.4.2 Global To get global specifications traceability matrix:

• switch to the

• in the tree, select the root folder


• the specification tree appears including in the right column, all the tests covering each specifications.

Testing CoveragOne of the major intereststesting. As you’ve already seen in previous chapters, requirements are linked to specifications and specifications are linked to tes

trics are computed per category and are retrievable from requirements, specifications

Global requirements traceability mTo get global requirements traceability

switch to the Requirements


on the right panel

the requirement tree appears including in the right column, all the specifications covering each requiremen

This traceability matrix is also present in the requirement book (that can be generated from

Global specificationTo get global specifications traceability matrix:

switch to the Specifications

the tree, select the root folder

on the right panel

the specification tree appears including in the right column, all the tests covering each specifications.

Testing Coveraginterests in using test management tool is the ability to track the coverage of your

testing. As you’ve already seen in previous chapters, requirements are linked to specifications and specifications are linked to tests. From this data, it is possible to generate some coverage metrics.


requirements traceability mTo get global requirements traceability

Requirements tab on the left panel


on the right panel, select the Traceability Matrix

the requirement tree appears including in the right column, all the specifications covering each requirement.


pecificationTo get global specifications traceability matrix:

Specifications tab on the left panel


on the right panel, select the Traceability Matrix

the specification tree appears including in the right column, all the tests covering each

Testing Coverage/Traceability Matrixin using test management tool is the ability to track the coverage of your

testing. As you’ve already seen in previous chapters, requirements are linked to specifications and ts. From this data, it is possible to generate some coverage metrics.


requirements traceability mTo get global requirements traceability matrix:



Traceability Matrix

the requirement tree appears including in the right column, all the specifications covering


pecifications traceability mTo get global specifications traceability matrix:



Traceability Matrix


/Traceability Matrixin using test management tool is the ability to track the coverage of your



requirements traceability m


Traceability Matrix tab



s traceability m


Traceability Matrix tab


/Traceability Matrixin using test management tool is the ability to track the coverage of your



requirements traceability matrix



s traceability matrix


/Traceability Matrix in using test management tool is the ability to track the coverage of your






in using test management tool is the ability to track the coverage of your testing. As you’ve already seen in previous chapters, requirements are linked to specifications and

ts. From this data, it is possible to generate some coverage metrics.





This traceability matrix is also present in the specificatXStudio).

4.4.3 Detailed rTo get requirements coverage metrics:

• switch to the

• in the tree, select a category


• twosuch as:

4.4.4 Detailed sTo get specifications

This traceability matrix is also present in the specificat

Detailed rTo get requirements coverage metrics:


in the tree, select a category

on the right panel

two tabs By specificationssuch as:

o percentage of the coverageo the list of requirements covered (at least partly) and not covered by respectively

some specifications or tests

Detailed sspecifications coverage metrics:


Detailed requirements To get requirements coverage metrics:


in the tree, select a category or a folder

on the right panel, select the Coverage

By specifications

percentage of the coveragethe list of requirements covered (at least partly) and not covered by respectively some specifications or tests

Detailed specificatcoverage metrics:


equirements coverageTo get requirements coverage metrics:


or a folder

Coverage tab

and By tests

percentage of the coverage the list of requirements covered (at least partly) and not covered by respectively some specifications or tests

pecifications coveragecoverage metrics:

This traceability matrix is also present in the specification book (that can be generated from

overage


tab

By tests are displayed. Each shows useful information

the list of requirements covered (at least partly) and not covered by respectively

overage

ion book (that can be generated from

are displayed. Each shows useful information








• switch to the



• the panel shows useful information such as:

4.4.5 Detailed To get tests

• switch to the


• on the right

• the panel shows useful information such as:

switch to the Specifications


on the right panel

the panel shows useful information such as:o percentage of the coo the list of

specifications

Detailed tests tests coverage metrics:

switch to the Tests


on the right panel

the panel shows useful information such as:o percentage of the coverageo the list of

Specifications tab on the left panel



the panel shows useful information such as:percentage of the coveragethe list of specificationsspecifications

ests coveragecoverage metrics:

Tests tab on the left panel


panel, select the Coverage

the panel shows useful information such as:percentage of the coveragethe list of tests covering


or a folder

Coverage tab

the panel shows useful information such as:verage

specifications covered (at least partly) and not covered by some

overage


or a folder

Coverage tab

the panel shows useful information such as:percentage of the coverage

tests covering (at least one


tab

the panel shows useful information such as:

covered (at least partly) and not covered by some

tab

the panel shows useful information such as:

one) and not covering


) and not covering some specifications


some specifications


some specifications

4.4.6 Detailed campaign coverageSince a test campaign is by definition a growell. To get campaign

• switch to the

• in the tree, select a


• the panel shows useful information

Detailed campaign coverageSince a test campaign is by definition a gro

campaigns coverage metrics:

switch to the Campaigns

in the tree, select a

on the right panel

the panel shows useful informationo percentage of the coverageo the list of o the list of

Detailed campaign coverageSince a test campaign is by definition a gro

s coverage metrics:




the panel shows useful informationpercentage of the coveragethe list of specificationsthe list of requirements fully

Detailed campaign coverageSince a test campaign is by definition a group of test,


campaign

Coverage tab

the panel shows useful information such as:percentage of the coverage

specifications fully, partially or not covered by the campaignrequirements fully, partially or not

Detailed campaign coverage up of test, it is possible to


tab

such as:

fully, partially or not covered by the campaign, partially or not covered by the campaign

it is possible to get some coverage metrics as

fully, partially or not covered by the campaigncovered by the campaign

some coverage metrics as

fully, partially or not covered by the campaign covered by the campaign

some coverage metrics as

4.5 ScWhen some tests are aimed at being execautomatic launcher), you can schedule a campaign to be executed on a regular basis. you need to create a created and To create a schedule:



• a dialog box including seven

• fill the

Scheduling test executionWhen some tests are aimed at being execautomatic launcher), you can schedule a campaign to be executed on a regular basis. you need to create a Schedulecreated and executed by XSTudio.

To create a schedule:



a dialog box including seven

fill the Details tab with the name

ing test executionWhen some tests are aimed at being execautomatic launcher), you can schedule a campaign to be executed on a regular basis.

chedule. Then, at the right time, a campaign session will be automatically executed by XSTudio.



a dialog box including seven tabs is

tab with the name

ing test executionWhen some tests are aimed at being executed completely automatically (using some specific automatic launcher), you can schedule a campaign to be executed on a regular basis.

. Then, at the right time, a campaign session will be automatically


on the right panel, click on the create schedule

tabs is displayed

tab with the name and the description

ing test execution uted completely automatically (using some specific

automatic launcher), you can schedule a campaign to be executed on a regular basis. . Then, at the right time, a campaign session will be automatically

schedule button

displayed

and the description of

uted completely automatically (using some specific automatic launcher), you can schedule a campaign to be executed on a regular basis.


button

of the schedule

uted completely automatically (using some specific automatic launcher), you can schedule a campaign to be executed on a regular basis. To do this,


schedule

uted completely automatically (using some specific To do this,


• in the

created and executed. Don’t forget to check the will not generate any test execution

• (opt.) select the

• select the needs to have XAgent installed and running

• select the

• select the involved in this schedule. Once a schedulechange the configurations associated. Ifcreate one

• (opt.) select the campaign session

• click on submit


When the time will come for an agent to execute tsession and then execute it. session will appear under the schedule node in the tree.

4.6 Tracking the Test ImplementationAs already seen, when addinnot. This parameter is tracked so that some reports can be generated. This helps for example in knowing exactly what the status of the automation development is. To control the progress

• switch to the



in the Schedulingcreated and executed. Don’t forget to check the will not generate any test execution


select the Agentneeds to have XAgent installed and running

select the SUT tab and pick the SUT on which the session

select the Configurationnvolved in this schedule. Once a schedulechange the configurations associated. Ifcreate one

(opt.) select the campaign session

click on submit

immediately, the

When the time will come for an agent to execute tsession and then execute it. session will appear under the schedule node in the tree.

Tracking the Test ImplementationAs already seen, when addinnot. This parameter is tracked so that some reports can be generated. This helps for example in knowing exactly what the status of the automation development is.

To control the progress of the test implementations:

switch to the Tests


on the right panel

Scheduling tab, select the days and the time when you want the sessions to be created and executed. Don’t forget to check the will not generate any test execution

Test operator

Agent tab and pick the agent on which the sessionneeds to have XAgent installed and running

tab and pick the SUT on which the session

Configuration tab and pick the configuration you which for each category nvolved in this schedule. Once a schedulechange the configurations associated. If

(opt.) select the CC Emails campaign sessions will be completed

immediately, the schedule appears in the tree

When the time will come for an agent to execute tsession and then execute it. From any station hosting XSTudio, after a refresh, the session will appear under the schedule node in the tree.

Tracking the Test ImplementationAs already seen, when adding a test in the system, you can specify if the test is implemented or not. This parameter is tracked so that some reports can be generated. This helps for example in knowing exactly what the status of the automation development is.

of the test implementations:

Tests tab on the left panel


on the right panel, select the Statistics

tab, select the days and the time when you want the sessions to be created and executed. Don’t forget to check the will not generate any test execution

Test operator tab and pick the user who will

tab and pick the agent on which the sessionneeds to have XAgent installed and running


tab and pick the configuration you which for each category nvolved in this schedule. Once a schedulechange the configurations associated. If

tab and check some users to receive a notification when the will be completed

ppears in the tree

When the time will come for an agent to execute tFrom any station hosting XSTudio, after a refresh, the

session will appear under the schedule node in the tree.

Tracking the Test Implementationg a test in the system, you can specify if the test is implemented or

not. This parameter is tracked so that some reports can be generated. This helps for example in knowing exactly what the status of the automation development is.



Statistics tab

tab, select the days and the time when you want the sessions to be created and executed. Don’t forget to check the Enabled

and pick the user who will

tab and pick the agent on which the sessionneeds to have XAgent installed and running


tab and pick the configuration you which for each category nvolved in this schedule. Once a schedule is created, it is impossible (by purpose) to

no configuration are available you will nee

tab and check some users to receive a notification when the

ppears in the tree

When the time will come for an agent to execute the tests, the agent will create the campaign From any station hosting XSTudio, after a refresh, the

session will appear under the schedule node in the tree.

Tracking the Test Implementationg a test in the system, you can specify if the test is implemented or



tab

tab, select the days and the time when you want the sessions to be Enabled checkbox. A disabled schedule

and pick the user who will (virtually)

tab and pick the agent on which the sessions will be run.

tab and pick the SUT on which the sessions will be run

tab and pick the configuration you which for each category is created, it is impossible (by purpose) to



he tests, the agent will create the campaign From any station hosting XSTudio, after a refresh, the

Tracking the Test Implementation g a test in the system, you can specify if the test is implemented or


tab, select the days and the time when you want the sessions to be checkbox. A disabled schedule

(virtually) run the session

will be run. This agent

will be run




he tests, the agent will create the campaign From any station hosting XSTudio, after a refresh, the

g a test in the system, you can specify if the test is implemented or not. This parameter is tracked so that some reports can be generated. This helps for example in

tab, select the days and the time when you want the sessions to be checkbox. A disabled schedule

run the sessions

This agent


no configuration are available you will need to


he tests, the agent will create the campaign From any station hosting XSTudio, after a refresh, the campaign

g a test in the system, you can specify if the test is implemented or not. This parameter is tracked so that some reports can be generated. This helps for example in

The panel is split in two different areas:

• a table displaying:

• a series of graph displaying:

4.7 Defects RA defect tracking system is good only if it provides a simple and efficient way of retrieving information about them. XStudio generates extensive reporting on defects. To get those reports,

• switch to the

• in the tree,


• choose a range of dates using the date pickers Then a huge

• on the

• on the passive defects (

• on all the defects

• submission/resolution rates trends


a table displaying:o for each date, the number of tests and to for each date, the percentage of tests and testcases implemented

a series of graph displaying:o the evolution of the number of tests and testcases implementedo the evolution of the percentage of tests and testcases implemented

Defects RA defect tracking system is good only if it provides a simple and efficient way of retrieving information about them. XStudio generates extensive reporting on defects.

To get those reports,

switch to the Defects


on the right panel

choose a range of dates using the date pickers

huge number of reports can be

the active defects (o per user (

� So major defects trends (o minor defects trends (o high priority defects trends (o low priority trends (

on the passive defects (o idem

on all the defectso idem

bmission/resolution rates trends


a table displaying: for each date, the number of tests and tfor each date, the percentage of tests and testcases implemented

a series of graph displaying: the evolution of the number of tests and testcases implementedthe evolution of the percentage of tests and testcases implemented

Defects ReportingA defect tracking system is good only if it provides a simple and efficient way of retrieving information about them. XStudio generates extensive reporting on defects.

Defects tab on the left panel

select a category

on the right panel, select the Statistics


number of reports can be

active defects (New, Aper user (Assigned to

Status, Severimajor defects trends (minor defects trends (high priority defects trends (low priority trends (Normal

on the passive defects (Resolved

on all the defects



for each date, the number of tests and tfor each date, the percentage of tests and testcases implemented

the evolution of the number of tests and testcases implementedthe evolution of the percentage of tests and testcases implemented

eporting A defect tracking system is good only if it provides a simple and efficient way of retrieving information about them. XStudio generates extensive reporting on defects.


Statistics tab


number of reports can be retrieved.

Assigned, Ackssigned to or Reported by

everity or Prioritymajor defects trends (Blocking, Majorminor defects trends (Minor, Cosmetichigh priority defects trends (High)

Normal, Low)

Resolved, Closed


for each date, the number of tests and testcases implementedfor each date, the percentage of tests and testcases implemented


A defect tracking system is good only if it provides a simple and efficient way of retrieving information about them. XStudio generates extensive reporting on defects.

tab


Ack) eported by)

riority trends Major)

Cosmetic, Enhancement

losed)

estcases implementedfor each date, the percentage of tests and testcases implemented


A defect tracking system is good only if it provides a simple and efficient way of retrieving information about them. XStudio generates extensive reporting on defects.

Enhancement)

estcases implemented for each date, the percentage of tests and testcases implemented

the evolution of the number of tests and testcases implemented the evolution of the percentage of tests and testcases implemented

A defect tracking system is good only if it provides a simple and efficient way of retrieving A defect tracking system is good only if it provides a simple and efficient way of retrieving

4.7.1 PerTo get per-user reports,

• select the tab corresponding to the desired group of defects:

• select if you want some data

• select a name in the user list

• select which

• The report will display the corresponding trendthe current status

4.7.2 PerTo get per-severity reports,

• select the tab corresponding to the desired group of defects:

• select if you want some d

• The report will display the corresponding trendthe current status

Per-user reportsuser reports,

elect the tab corresponding to the desired group of defects:o Active Defectso Passiveo All Defects

select if you want some data

select a name in the user list

select which kind of informationo Status o Severityo Priority

The report will display the corresponding trendthe current status

Per-severity reportsseverity reports,


select if you want some do Major defects (o Minor defects (


user reports

elect the tab corresponding to the desired group of defects:Defects (New

Passive Defects (ResolvedAll Defects

select if you want some data about defects

select a name in the user list

kind of information

Severity


severity reportsseverity reports,

elect the tab corresponding to the desired group of defects:Defects (New


select if you want some data aboutdefects (Blockingdefects (Minor


elect the tab corresponding to the desired group of defects:New, Assigned and

Resolved and C

about defects

kind of information you’re interested in:

The report will display the corresponding trend

severity reports

elect the tab corresponding to the desired group of defects:New, Assigned and

Resolved and C

ata about Blocking, Major) Minor, Cosmetic,

The report will display the corresponding trend

elect the tab corresponding to the desired group of defects:and Ack) Closed)

about defects Assigned to

you’re interested in:

The report will display the corresponding trends and an additional pie chart represe

elect the tab corresponding to the desired group of defects:and Ack) Closed)

, Enhancement

The report will display the corresponding trends and an additional pie chart representing

elect the tab corresponding to the desired group of defects:

Assigned to or of Reported by

and an additional pie chart represe

elect the tab corresponding to the desired group of defects:

Enhancement)

and an additional pie chart representing

Reported by a specific user

and an additional pie chart represe


a specific user



4.7.3 PerTo get per-priority reports,

• selec

• select if you want some data about

• The repothe current status

Per-priority reportspriority reports,


select if you want some data abouto High Priorityo Low Priority


priority reportspriority reports,

t the tab corresponding to the desired group of defects:Defects (New


select if you want some data aboutHigh Priority defects (Low Priority defects (

rt will display the corresponding trendthe current status

priority reports

t the tab corresponding to the desired group of defects:New, Assigned and

Resolved and C

select if you want some data about defects (High) defects (Normal and

rt will display the corresponding trend

t the tab corresponding to the desired group of defects:and Ack) Closed)

and Low)

rt will display the corresponding trends and an additional pie chart representing

t the tab corresponding to the desired group of defects:


and an additional pie chart representing and an additional pie chart representing

4.7.4 Submission/Resolution ratesTo get submission/Resolution rates reports,

• select the

The top part of the panel shows the progreswell as the metrics as of now and as of the last record.

Submission/Resolution ratesTo get submission/Resolution rates reports,

elect the Resolution Rates



Resolution Rates



tab

The top part of the panel shows the progression of the number of well as the metrics as of now and as of the last record.

Submission/Resolution rates

sion of the number of well as the metrics as of now and as of the last record.

sion of the number of Active and

and Passive defects as defects as

The bottom part of the panel shows

4.8 AttachmentsYou have the ability to attach somXStudio. This is an extremely powerful way of centralizing/sharing documents. Attachments can be created to the following entities Requirements tree:

• category

• folder Specifications tree:

• category

• folder Test tree:

• cate

• folder

• test

• testcase Campaign tree:

• campaign session

• testcase execution (only uploadable programmatically by the launcher/test) Defect tree:

• defect The GUI is extremely

Whenever it’s possible, two panels are displayed: one for attachmenentity and another one for the attachments inherited from the ancestor nodes. It is possible to modirectly to one of these parents by clicking on the anchors

The bottom part of the panel shows

AttachmentsYou have the ability to attach som

. This is an extremely powerful way of centralizing/sharing documents. Attachments can be created to the following entities

Requirements tree:

category

folder

Specifications tree:

category

folder

category

folder

test

testcase

Campaign tree:

campaign session

testcase execution (only uploadable programmatically by the launcher/test)

tree:

defect

The GUI is extremely simple


The bottom part of the panel shows the submission and resolution rates.

Attachments You have the ability to attach some files (whatever the forma

. This is an extremely powerful way of centralizing/sharing documents. Attachments can be created to the following entities:

campaign session


simple:


the submission and resolution rates.

e files (whatever the forma. This is an extremely powerful way of centralizing/sharing documents. Attachments can be




e files (whatever the forma. This is an extremely powerful way of centralizing/sharing documents. Attachments can be


Whenever it’s possible, two panels are displayed: one for attachmenentity and another one for the attachments inherited from the ancestor nodes. It is possible to modirectly to one of these parents by clicking on the anchors.


e files (whatever the format is) to some entities managed by . This is an extremely powerful way of centralizing/sharing documents. Attachments can be


Whenever it’s possible, two panels are displayed: one for attachments directly attached to the entity and another one for the attachments inherited from the ancestor nodes. It is possible to mo

is) to some entities managed by . This is an extremely powerful way of centralizing/sharing documents. Attachments can be


ts directly attached to the entity and another one for the attachments inherited from the ancestor nodes. It is possible to mo

is) to some entities managed by . This is an extremely powerful way of centralizing/sharing documents. Attachments can be

ts directly attached to the entity and another one for the attachments inherited from the ancestor nodes. It is possible to move

4.8.1 Add an attachmentTo add an attachment:

• click on the

• a dialog box is

• pick a file and submit

4.8.2 Download/Open an attachmentTo download/open an attachment:

• select an item in the list

• click on the

4.9 Generate

4.9.1 RIt may be interesting to export or to print a list of requirements. With partial or complete requirement books. To do so:

• switch to the

• in the tree, select a category or a folder

• click on the

• first

• a dialog box is

• select the HTML you can select one transformdocument to know how to do that). By default, two XSLT are provided along with XStudio (RawResult

Add an attachmentTo add an attachment:

click on the Create attach


pick a file and submit

Download/Open an attachmentTo download/open an attachment:

select an item in the list

click on the Download attachment

Generate

Requirementbe interesting to export or to print a list of requirements. With

partial or complete requirement books.



click on the Create

first select the destination folder for the book


select the extensionHTML you can select one transform (one document to know how to do that). By default, two XSLT are provided along with XStudio RawResult - the more detailed

Add an attachment

Create attachment

displayed

pick a file and submit

Download/Open an attachmentTo download/open an attachment:

select an item in the list

Download attachment

Generate documentation

equirements bookbe interesting to export or to print a list of requirements. With




ate report button

select the destination folder for the book

displayed

extension of the book (HTML or XMLHTML you can select one t

(one .xslt file) so that ydocument to know how to do that). By default, two XSLT are provided along with XStudio

the more detailed

Add an attachment

ment button

Download/Open an attachment

Download attachment / Open attachment

documentation

books be interesting to export or to print a list of requirements. With




button


of the book (HTML or XMLtype of book. Each type corresponds to one

file) so that you can add your own if you wish (see later in this document to know how to do that). By default, two XSLT are provided along with XStudio

the more detailed - and TraceabilityMatrix

Download/Open an attachment

/ Open attachment

documentation

be interesting to export or to print a list of requirements. With



of the book (HTML or XML). If you choose toof book. Each type corresponds to one

ou can add your own if you wish (see later in this document to know how to do that). By default, two XSLT are provided along with XStudio

TraceabilityMatrix

/ Open attachment button

be interesting to export or to print a list of requirements. With XSTudio

If you choose toof book. Each type corresponds to one


TraceabilityMatrix):

XSTudio you can export

If you choose to generate the book in of book. Each type corresponds to one specific XSLT


you can export

generate the book in specific XSLT


• provid

• submit

• after it has been generated, the book is automatically opened:

4.9.2 SpecificationTo generate specification books, requirement books (but from the

provide the filename

submit

after it has been generated, the book is automatically opened:

pecificationTo generate specification books, requirement books (but from the

filename for the book


pecifications booksTo generate specification books, requirement books (but from the Specificatio

for the book


books To generate specification books, follow the same instructions than those

Specifications tab on the left panel).


follow the same instructions than thosetab on the left panel).


follow the same instructions than thosetab on the left panel).

follow the same instructions than those for generating for generating

4.9.3 Projects booksTo generate projects books, follow the same instructions than those for generating requirement books (but from the

4.9.4 TestplansTo generate (but from the

Projects booksTo generate projects books, follow the same instructions than those for generating requirement books (but from the Projects

estplansTo generate testplans, follow the same instructi(but from the Tests tab on the left panel).

Projects books To generate projects books, follow the same instructions than those for generating requirement

Projects tab on the left panel).

estplans , follow the same instructi

tab on the left panel).

To generate projects books, follow the same instructions than those for generating requirement tab on the left panel).

, follow the same instructions than those for generating requirement books tab on the left panel).

To generate projects books, follow the same instructions than those for generating requirement tab on the left panel).

ons than those for generating requirement books

To generate projects books, follow the same instructions than those for generating requirement






4.9.5 Test reportsTo generate (but from the

est reportsTo generate test reports, follow the same instructions than those for generating requirement books (but from the Campaigns

est reports , follow the same instructions than those for generating requirement books


, follow the same instructions than those for generating requirement books tab on the left panel).

, follow the same instructions than those for generating requirement books

, follow the same instructions than those for generating requirement books

, follow the same instructions than those for generating requirement books , follow the same instructions than those for generating requirement books

4.10 Customizing the documentsAll the documents that you can generate from

4.10.1 Changing the logoAll the documents generated from be changed very simply:

• copy you

• from the menu, select

• in the

Customizing the documentsAll the documents that you can generate from

Changing the logoAll the documents generated from be changed very simply:

opy your logo picture file (i.e. gif, jpg, png etc.) to the following folders:o requirementso specificationso testplanso reports

from the menu, select

the company logo

Customizing the documentsAll the documents that you can generate from

Changing the logoAll the documents generated from XStudio

r logo picture file (i.e. gif, jpg, png etc.) to the following folders:requirements specifications testplans

from the menu, select Settings

company logo text field,

Customizing the documentsAll the documents that you can generate from XStudio

Changing the logo XStudio include a logo on the upper top side of it. This logo can

r logo picture file (i.e. gif, jpg, png etc.) to the following folders:

Settings > General

text field, enter the name of the picture file

Customizing the documentsXStudio are customizable.

include a logo on the upper top side of it. This logo can


General

enter the name of the picture file

Customizing the documents are customizable.



enter the name of the picture file and submit



and submit


• from now, all t

4.10.2 CAll documents that are generated by transformed into a different format

For instance, let’s own XSLT file. For example, you can take the file and modify it as much as you want, rename it

from now, all the documents that you wil generate will have your own logo in the header:

Customizing the reportsAll documents that are generated by transformed into a different format

For instance, let’s imagineown XSLT file. For example, you can take the file and modify it as much as you want, rename it

he documents that you wil generate will have your own logo in the header:

ustomizing the reportsAll documents that are generated by transformed into a different format using specific XSLT tr

imagine you want to generate own XSLT file. For example, you can take the file and modify it as much as you want, rename it


ustomizing the reports All documents that are generated by XSTudio are

using specific XSLT tr

you want to generate a own XSLT file. For example, you can take the file and modify it as much as you want, rename it requirem


are first internally generated in XML then possibly

using specific XSLT transforms

a custom requirement bookown XSLT file. For example, you can take the file requirement

requirementHTML_My_Own_Report1.xslt


first internally generated in XML then possibly ansforms:

requirement bookrequirementHTML_RawResult.xslt

entHTML_My_Own_Report1.xslt


first internally generated in XML then possibly

requirement book. You can create your HTML_RawResult.xslt as a basis

entHTML_My_Own_Report1.xslt


first internally generated in XML then possibly

You can create your as a basis

entHTML_My_Own_Report1.xslt and

ensure it is located along with the other only a standalone install or on the Apache/Tomcat server to share this report with everybody connecting to this server From now, when you will try to generate a requirements book, the type available in the combo box:

The internal process is

• several SQL request are made to the database to get all the necessary information

• a structured

• if the user chose correct name

• if the user chose to the selected

The only constraint is to use a specific naming convention: where:

• <type>

• <name> signs.

4.11 Searching

4.11.1 ByAll the trees in

by his nametree

ensure it is located along with the other only a standalone install or on the Apache/Tomcat server to share this report with everybody connecting to this server

From now, when you will try to generate a requirements book, the type available in the combo box:

he internal process is then

several SQL request are made to the database to get all the necessary information

structured XML document including

if the user chose correct name

if the user chose to the selected type

The only constraint is to use a specific naming convention:

<type> can be: o "requiremento "specificationo "task" o "testplano "report" o "defect".

<name> can be any name including alphanumeric characters plusigns.

Searching

By nameAll the trees in XStudio include an indexing system allowing to search real

by his name. To experiment it by yourself just s

ensure it is located along with the other only a standalone install or on the Apache/Tomcat server to share this report with everybody connecting to this server).

From now, when you will try to generate a requirements book, the type available in the combo box:

then the following:


XML document including

if the user chose XML, the XML is saved on the disk in the

if the user chose HTML, the XML document is transformed using the Xype.


requirement" specification"

testplan"

".

can be any name including alphanumeric characters plu

Searching

name include an indexing system allowing to search real

To experiment it by yourself just s

ensure it is located along with the other .xslt filesonly a standalone install or on the Apache/Tomcat server to share this report with everybody

From now, when you will try to generate a requirements book, the type

the following:


XML document including all the required

, the XML is saved on the disk in the

the XML document is transformed using the X



include an indexing system allowing to search real

To experiment it by yourself just start entering some text in the

files (in the export/xslonly a standalone install or on the Apache/Tomcat server to share this report with everybody

From now, when you will try to generate a requirements book, the type


all the required data

, the XML is saved on the disk in the


The only constraint is to use a specific naming convention: <type>HTML_<name>.xslt


include an indexing system allowing to search real

tart entering some text in the

export/xsl folder only a standalone install or on the Apache/Tomcat server to share this report with everybody

From now, when you will try to generate a requirements book, the type My_Own_report1


data is generated

, the XML is saved on the disk in the requirements


<type>HTML_<name>.xslt

can be any name including alphanumeric characters plus underscore and dash

include an indexing system allowing to search real-time an entity in the tree

tart entering some text in the

folder – either locally if using only a standalone install or on the Apache/Tomcat server to share this report with everybody

My_Own_report1


is generated

requirements folder with the

the XML document is transformed using the XSLT corresponding

<type>HTML_<name>.xslt

s underscore and dash

time an entity in the tree

tart entering some text in the Search field

either locally if using only a standalone install or on the Apache/Tomcat server to share this report with everybody

My_Own_report1 will be


folder with the

SLT corresponding

s underscore and dash

time an entity in the tree

field of the

To automatically select a searched item in the tree, you can move suggestion list and validate by pressing

4.11.2 ByThe data modelform: Template

R_<id>

S_<id>

T_<id>

TC_<id>

C_<id>

D_<id>

TA_<id>

Ids are also available from corresponds to

To search for an entity from its Id, just type the Id in the validate.

4.11.3 Advanced and plain textSearching items such as requirements, specificationscombination of some very specific criteria can be not only very useful but extremely important to control/guarantee the quality of the products.

4.11.3.1 Requirements

Procedure:

• in the requirement tree, select a category


• check all the checkboxes

• (opt.) type some text in the Text to search field and press


By Id data model gives unique identifier for each entity man

Represents

Requirement

Specification

Test

Testcase

Campaign session

Defect

Tasks

ds are also available from corresponds to <id> in the templates.

To search for an entity from its Id, just type the Id in the

Advanced and plain textearching items such as requirements, specifications

combination of some very specific criteria can be not only very useful but extremely important to control/guarantee the quality of the products.

Requirements

in the requirement tree, select a category

on the right panel

check all the checkboxes

(opt.) type some text in the Text to search field and press


gives unique identifier for each entity man

Represents

Requirement

Specification

Test

Testcase

Campaign session

Defect

Tasks

Table 8

ds are also available from XStudioin the templates.


Advanced and plain textearching items such as requirements, specifications


Requirements


on the right panel, select the Search

check all the checkboxes (Status


To automatically select a searched item in the tree, you can move suggestion list and validate by pressing Enter or just click on the item in the list.

gives unique identifier for each entity man

Campaign session

8 - Unique Identifier Templates

XStudio’s GUI (in in the templates.


Advanced and plain text earching items such as requirements, specifications



Search tab

Status and Priority


To automatically select a searched item in the tree, you can move or just click on the item in the list.

gives unique identifier for each entity managed by

Unique Identifier Templates

’s GUI (in Details tab you have an

To search for an entity from its Id, just type the Id in the Search Id

search earching items such as requirements, specifications, tasks, tests

combination of some very specific criteria can be not only very useful but extremely important to

Priority) that match your search criteria


To automatically select a searched item in the tree, you can move using the arrows keys or just click on the item in the list.

aged by XStudio

Unique Identifier Templates

tab you have an

Search Id field

, tasks, tests or defect based on a

combination of some very specific criteria can be not only very useful but extremely important to

that match your search criteria

(opt.) type some text in the Text to search field and press Enter

using the arrows keys or just click on the item in the list.

XStudio. The Ids are on the

tab you have an Identifier

or defect based on a combination of some very specific criteria can be not only very useful but extremely important to


using the arrows keys within the

. The Ids are on the

field that

and

or defect based on a combination of some very specific criteria can be not only very useful but extremely important to

Note: The results it. The results table can be ordered by clicking on the

4.11.3.2 Specifications

Procedure:

• in the


• check all the checkboxes

• (opt.) type some text in the Text to search field and press

4.11.3.3 Tasks

Procedure:

The results list is updated realit. The results table can be ordered by clicking on the

Specifications

in the specification

on the right panel

check all the checkboxes


Tasks

list is updated real-time and you can reach one particular defect by just clicking on it. The results table can be ordered by clicking on the

Specifications

specification tree, select a category


check all the checkboxes (Status


time and you can reach one particular defect by just clicking on it. The results table can be ordered by clicking on the

tree, select a category

Search tab

Status and Priority


time and you can reach one particular defect by just clicking on it. The results table can be ordered by clicking on the column

Priority) that match your search criteria


time and you can reach one particular defect by just clicking on column headers.



time and you can reach one particular defect by just clicking on


time and you can reach one particular defect by just clicking on

• in the


• type some text in the Text to search field and press

4.11.3.4 Tests

Procedure:

• in the test tree, select the root folder


• type some text in the Text to search field and press

4.11.3.5 Defects

Searching defects based on a combination of some very specific criteria is extremely important to control the quality of the product.

in the project tree, select the root

on the right panel

type some text in the Text to search field and press

Tests

in the test tree, select the root folder

on the right panel


Defects

defects based on a combination of some very specific criteria is extremely important to control the quality of the product.

project tree, select the root






defects based on a combination of some very specific criteria is extremely important to control the quality of the product.

project tree, select the root folder

Search tab



Search tab


defects based on a combination of some very specific criteria is extremely important to

type some text in the Text to search field and press Enter

type some text in the Text to search field and press Enter


Enter

Enter


defects based on a combination of some very specific criteria is extremely important to defects based on a combination of some very specific criteria is extremely important to

To do so:

• in the defect tree, select a category


• check all the checkboxes Severity

• (opt.) type some text in the Text to search field and

4.12 Importing data

4.12.1 From CSVIf you are migrating from manual test management XStudio - you may want to import all your tests and testcases from CSV text files (indeed, all spreadsheet programs provide easy way to export to CSV). The source CSV file must use semicolumn (‘;’) delimiter.

4.12.1.1 Test and

To import tests and testcases from a CSV file


• a dialog box is

• pick the

• click on the

• the raw data area dis

• click on

in the defect tree, select a category

on the right panel

check all the checkboxes Severity and Priority

(opt.) type some text in the Text to search field and

Importing data

From CSVIf you are migrating from manual test management

you may want to import all your tests and testcases from CSV text files (indeed, all spreadsheet programs provide easy way to export to CSV). The source CSV file must use semi

’) delimiter.

Test and testcases

import tests and testcases from a CSV file



pick the Tests and Testcases (without testplan)

click on the Open

the raw data area dis

click on Submit



check all the checkboxes (Reported byPriority) that match your search criteria


Importing data

From CSV If you are migrating from manual test management

you may want to import all your tests and testcases from CSV text files (indeed, all spreadsheet programs provide easy way to export to CSV). The source CSV file must use semi

testcases

import tests and testcases from a CSV file

from the menu, select File > Import from CSV

displayed

Tests and Testcases (without testplan)

Open button and select the file you wish to import

the raw data area displays the content of the file


Search tab

Reported bythat match your search criteria


Importing data

If you are migrating from manual test management you may want to import all your tests and testcases from CSV text files (indeed, all

spreadsheet programs provide easy way to export to CSV). The source CSV file must use semi

import tests and testcases from a CSV file:

File > Import from CSV

Tests and Testcases (without testplan)

button and select the file you wish to import

plays the content of the file

Reported by, Assigned tothat match your search criteria


If you are migrating from manual test management - using a basic spryou may want to import all your tests and testcases from CSV text files (indeed, all



Tests and Testcases (without testplan) option


plays the content of the file

signed to, Found in

press Enter

using a basic spreadsheet application to you may want to import all your tests and testcases from CSV text files (indeed, all


option


Found in, Fixed in

eadsheet application to you may want to import all your tests and testcases from CSV text files (indeed, all


Fixed in, Status,

eadsheet application to you may want to import all your tests and testcases from CSV text files (indeed, all

spreadsheet programs provide easy way to export to CSV). The source CSV file must use semi-

After the import task has completed, the tests and testcases appear immediately in the test tree.

If you wish to import tests and testcases course be more complexused as well as the semi To do so:


• a dialog box is

• pick the

• click on the

• the raw data area displays the content of the file

• click on


If you wish to import tests and testcases more complex

used as well as the semi



pick the Tests and Testcases (with

click on the Open


click on Submit


If you wish to import tests and testcases more complex (a testcase is then defined on several lines and the tabular character is

used as well as the semi-column delimiter).

from the menu, select File > Import from CSV

displayed

Tests and Testcases (with




If you wish to import tests and testcases including the testplan(a testcase is then defined on several lines and the tabular character is

column delimiter).


Tests and Testcases (with testplan)




including the testplan(a testcase is then defined on several lines and the tabular character is


estplan) option




including the testplan, the syntax of the CSV file (a testcase is then defined on several lines and the tabular character is



, the syntax of the CSV file (a testcase is then defined on several lines and the tabular character is


, the syntax of the CSV file will of (a testcase is then defined on several lines and the tabular character is

4.12.2 From XMLThe XML format used is the same as the one used to export tests/testcase in XML.

4.12.2.1 Tests and tes

To import tests and testcases from XML:


• a dialog box is

• pick the

• click on the


• click on




• a dialog box is

• pick the

• click on the

• the raw data area di

• click on

From XMLThe XML format used is the same as the one used to export tests/testcase in XML.

Tests and tes




pick the Tests option

click on the Open


lick on Submit

Requirements




pick the Requirements

click on the Open

the raw data area di

click on Submit

From XML The XML format used is the same as the one used to export tests/testcase in XML.

Tests and testcases


from the menu, select File > Import from

displayed

option



Requirements



displayed

Requirements option



The XML format used is the same as the one used to export tests/testcase in XML.


File > Import from XML





option


splays the content of the file


XML



XML


splays the content of the file





4.12.2.3 Specifications



• a dialog box is

• pick the

• click on the


• click on

Specifications




pick the Specifications

click on the Open


click on Submit

Specifications



displayed

Specifications option

Open button and select the file you wi




option

button and select the file you wi


XML



sh to import

5. The

5.1 Tests attributesYou can create and associate custom attribute to your tests. These attributes can be used later in filters to automatically select some

There are two types of attributes: static and dynamic. Dynamic attributes are identified with the icon. A dynamic attribute is an attribute that you can overwrite when creating

5.1.1 Associate To associate attributes to a test:



• un-toggle the

• check

• give a value to each of these attributes. Depending of the type of the attribute the value field will be different:

The expert

Tests attributesYou can create and associate custom attribute to your tests. These attributes can be used later in filters to automatically select some


Associate To associate attributes to a test:




check the attributes that need to be associated to

give a value to each of these attributes. Depending of the type of the attribute the value field will be different:

o Booleano Integer

of numbers.� you

will define all numbers included in between 10 and 15. This is equivalent to “

� you can also use the character “� both can be combined

1;67:68

o String� you can use the character “

bar;john doe;jane doe

expert’s corner

Tests attributesYou can create and associate custom attribute to your tests. These attributes can be used later in filters to automatically select some tests matching some specific criteria.


Associate some attributes to a testTo associate attributes to a test:


on the right panel, select the Attributes


attributes that need to be associated to

give a value to each of these attributes. Depending of the type of the attribute the value field will be different:

Boolean: a check boxInteger: a text field accepting

of numbers. you can use the character “will define all numbers included in between 10 and 15. This is equivalent to “10;11;12;13;14;15you can also use the character “both can be combined

1;67:68”

String: a text fieldyou can use the character “

bar;john doe;jane doe

’s corner

Tests attributes You can create and associate custom attribute to your tests. These attributes can be used later in

tests matching some specific criteria.


attributes to a test

Attributes tab

button to display the complete attributes list

attributes that need to be associated to

give a value to each of these attributes. Depending of the type of the attribute the value

a check box a text field accepting

can use the character “will define all numbers included in between 10 and 15. This is equivalent to 10;11;12;13;14;15”

you can also use the character “both can be combined (i.e. you can use strings like “

a text field accepting a string or a list of strings.you can use the character “

bar;john doe;jane doe”

You can create and associate custom attribute to your tests. These attributes can be used later in tests matching some specific criteria.



tab

to display the complete attributes list

attributes that need to be associated to the current test


a text field accepting a combination of number, range of numbers, list

can use the character “:” to define a range of numbers (i.e. “will define all numbers included in between 10 and 15. This is equivalent to

you can also use the character “;” as a delimiter of several numbers(i.e. you can use strings like “

accepting a string or a list of strings.you can use the character “;” as a delimiter of several strings (i.e. “

”

You can create and associate custom attribute to your tests. These attributes can be used later in tests matching some specific criteria.




the current test.


a combination of number, range of numbers, list

” to define a range of numbers (i.e. “will define all numbers included in between 10 and 15. This is equivalent to

” as a delimiter of several numbers(i.e. you can use strings like “

accepting a string or a list of strings. ” as a delimiter of several strings (i.e. “

You can create and associate custom attribute to your tests. These attributes can be used later in

There are two types of attributes: static and dynamic. Dynamic attributes are identified with the icon. A dynamic attribute is an attribute that you can overwrite when creating a campaign




” to define a range of numbers (i.e. “will define all numbers included in between 10 and 15. This is equivalent to

” as a delimiter of several numbers(i.e. you can use strings like “-4;34:56;

” as a delimiter of several strings (i.e. “

You can create and associate custom attribute to your tests. These attributes can be used later in

There are two types of attributes: static and dynamic. Dynamic attributes are identified with the session.



” to define a range of numbers (i.e. “10:15” will define all numbers included in between 10 and 15. This is equivalent to

” as a delimiter of several numbers 4;34:56;-2:-

” as a delimiter of several strings (i.e. “foo

• (opt.) re

• click on

5.1.2 Create To create a new (not already existing) attribute



• un-toggle the

• click on the

• a dialog box is

• enter the name of the attribute

• choose the type for this attribute

• Select the checkbox dynamic if you thicreation time

• click on

• immediately, the attribute appears in the tree

• check

• give a value

• (opt.) re

• click on

5.1.3 Edit an attributeTo rename an attribute or change its ”dynamic” property:


click on Submit

Create and associate a new a new (not already existing) attribute




click on the create


enter the name of the attribute

choose the type for this attribute

Select the checkbox dynamic if you thicreation time

click on Submit

immediately, the attribute appears in the tree

check this attribute

give a value to this attribute


click on Submit

Edit an attributeTo rename an attribute or change its ”dynamic” property:

toggle the select filte

and associate a new a new (not already existing) attribute


on the right panel, select the Attrib


reate attribute button

displayed



Select the checkbox dynamic if you thi


this attribute

to this attribute


Edit an attribute To rename an attribute or change its ”dynamic” property:

select filter button to display only the selected attributes

and associate a new a new (not already existing) attribute and associate

Attributes tab

button to display the complete attributes list

button



Select the checkbox dynamic if you this attribute to be over


select filter button to display only the s

To rename an attribute or change its ”dynamic” property:

to display only the selected attributes

and associate a new attributeand associate it

tab


s attribute to be over


to display only the s

To rename an attribute or change its ”dynamic” property:


attribute to a testit to a test:


s attribute to be over-writeable at campaign session



to a test


writeable at campaign session

elected attributes

writeable at campaign session



• un-toggle the

• select the attribute you want to edit

• click on the


• enter the dynamic property (note that if you change the type of theassociations with some tests will be deleted)

• click on


5.1.4 Create a campaign based on attribute filterWhen you gave a lot of tests, it may be interesting to preselvalues. To create a campaign based on attribute filter:



• a dialog box including two tabs is

• fill the

• in the




select the attribute you want to edit

click on the edit


enter the new name of the attributedynamic property (note that if you change the type of theassociations with some tests will be deleted)

click on Submit

immediately, the

Create a campaign based on attribute filterWhen you gave a lot of tests, it may be interesting to presel

To create a campaign based on attribute filter:




fill the Details tab wi

in the Content tabo click on the o a dialog box is

� select the root folder and add a � click on the � a dialog box is


on the right panel, select the Attributes



attribute button


name of the attributedynamic property (note that if you change the type of theassociations with some tests will be deleted)

immediately, the modified attribute appears in the tree







tab click on the preset filter settingsa dialog box is displayed

select the root folder and add a click on the add an expressiona dialog box is

Attributes tab

button to display the complete attributes


button

name of the attribute, change the type of the attribute or select/unselect the dynamic property (note that if you change the type of theassociations with some tests will be deleted)

attribute appears in the tree





th the name of the campaign

preset filter settings displayed

select the root folder and add a add an expression


tab

to display the complete attributes

, change the type of the attribute or select/unselect the dynamic property (note that if you change the type of theassociations with some tests will be deleted)

attribute appears in the tree

Create a campaign based on attribute filterWhen you gave a lot of tests, it may be interesting to preselect all tests having certain attribute

campaign icon

displayed

th the name of the campaign

button

select the root folder and add a AND operatoradd an expression button

to display the complete attributes

, change the type of the attribute or select/unselect the dynamic property (note that if you change the type of the attribute, all the former

Create a campaign based on attribute filterect all tests having certain attribute

operator button


, change the type of the attribute or select/unselect the attribute, all the former

Create a campaign based on attribute filter ect all tests having certain attribute

, change the type of the attribute or select/unselect the attribute, all the former

ect all tests having certain attribute

• click on submit

• immediately, the campaign appears in the tree

5.2 Dependencies between testsIt is possible to add dependencies between tests. One test can be the parent of one or several tests. The reverse is also true.Ultimately, XStudio will be able to use this information to:

• execute only child tests if the parents are all successful

� enter the expression � click on submit

o click on submito click on the o filtering will be performed and the content tab will highlight and pre

tests matching the filter. You can of course unselect or selist

click on submit


Dependencies between testsIt is possible to add dependencies between tests. One test can be the parent of one or several tests. The reverse is also true.

imately, XStudio will be able to use this information to:

execute only child tests if the parents are all successful

enter the expression click on submit

click on submit click on the preset filterfiltering will be performed and the content tab will highlight and pretests matching the filter. You can of course unselect or se


Dependencies between testsIt is possible to add dependencies between tests. One test can be the parent of one or several tests. The reverse is also true.



enter the expression “new attribute” starts with “value for”click on submit

preset filter button filtering will be performed and the content tab will highlight and pretests matching the filter. You can of course unselect or se


Dependencies between testsIt is possible to add dependencies between tests. One test can be the parent of one or several



new attribute” starts with “value for”

filtering will be performed and the content tab will highlight and pretests matching the filter. You can of course unselect or se


Dependencies between tests It is possible to add dependencies between tests. One test can be the parent of one or several




filtering will be performed and the content tab will highlight and pretests matching the filter. You can of course unselect or select new tests from this

It is possible to add dependencies between tests. One test can be the parent of one or several


filtering will be performed and the content tab will highlight and pre-select all the lect new tests from this


select all the lect new tests from this


• override the order of execution of the tests

To create some dependencies between tests:



• select the

• un-toggle the

• check all the

• (opt.) re

• click on submit

In this example,

5.3 Test execution historyOne very interesting option is also to check the history of all the executions of one specific test. To do so, it is ex



override the order of execution of the tests




select the Child of


check all the tests


click on submit

In this example, Test1 will be child of

Test execution historyOne very interesting option is also to check the history of all the executions of one specific test. To do so, it is extremely simple:






on the right panel, select the Dependencies

Child of (or Father of


tests that are childs of (or fathers of)


will be child of

Test execution historyOne very interesting option is also to check the history of all the executions of one specific test. To

tremely simple:


on the right panel, select the Results



Dependencies

Father of) tab

button to display the complete test tree

are childs of (or fathers of)

select filter button to di

will be child of Test2 and Test3

Test execution historyOne very interesting option is also to check the history of all the executions of one specific test. To

Results tab


Dependencies tab

to display the complete test tree

are childs of (or fathers of) the current


Test3.

Test execution history One very interesting option is also to check the history of all the executions of one specific test. To


the current test

splay only the selected requirement

One very interesting option is also to check the history of all the executions of one specific test. To






The panel shows a number of useful information:

• the campaign sessions that were already executed and that included that test

• the start and stop date of this campaign

• the result of this test in the campaign session

Note: You can reach one particular

5.4 Duration

5.4.1 Estimated duration oAs we’ve seen before, a campaign is made of a list of testtimes, Xstudio can provide an estimated duration based on previous executions as well as the probability of exactness. This information is available in the Details tab of the campaign:

shows a number of useful information:

the campaign sessions that were already executed and that included that test

the start and stop date of this campaign

the result of this test in the campaign session

ou can reach one particular

uration

Estimated duration oAs we’ve seen before, a campaign is made of a list of test

tudio can provide an estimated duration based on previous executions as well as the probability of exactness.

This information is available in the Details tab of the campaign:



the start and stop date of this campaign


ou can reach one particular campaign session

of test execution

Estimated duration oAs we’ve seen before, a campaign is made of a list of test

tudio can provide an estimated duration based on previous executions as well as the




the start and stop date of this campaign session


campaign session

of test execution

Estimated duration of a campaignAs we’ve seen before, a campaign is made of a list of test




session


campaign session by just clicking on it.

of test execution

f a campaignAs we’ve seen before, a campaign is made of a list of test. If a test has already been run several




by just clicking on it.

f a campaign . If a test has already been run several



. If a test has already been run several tudio can provide an estimated duration based on previous executions as well as the

. If a test has already been run several tudio can provide an estimated duration based on previous executions as well as the

5.4.2 Average duration of If a test has already been run several times, Xprevious executions. This information is available in the Details tab of the test:

Average duration of If a test has already been run several times, Xprevious executions.

This information is available in the Details tab of the test:

Average duration of If a test has already been run several times, X


Average duration of a testIf a test has already been run several times, Xstudio can provide the average duration based on


t tudio can provide the average duration based on


tudio can provide the average duration based on



6. LaunchersXStudio can execute any kind of tests (scripts, native codemeans that your already existing test suites are usable as they are. The only condition is to develop (in Java) a tiny component allowing the Launcher You may have different types of test implementation that require completely different approaches to execute them. To each type of test (i.e. tests developed in different languages) corresponds a “category”. For any category of tests you have, you’ll need a sp Several launchers can live together. You just need to add all the necessary launchers (.jar files) in the <Install_folder

To get more information on how to develop your own launcher, read the “Developer’s guide”

6.1 Default launchersBy default, X Launcher

manual.jar

simple_manual.jar

autoit.jar

perl.jar

tcl.jar

testcomplete7.jar

testpartner.jar

visualstudio.jar

beanshell.jar

squishqt.jar

squishweb.jar

junit3.jar

junit4.jar

pyunit.jar

nunit.jar

testng.jar

marathon.jar

exe.jar

random.jar

success.jar

Launcherscan execute any kind of tests (scripts, native code

means that your already existing test suites are usable as they are. The only condition is to develop ) a tiny component allowing

Launcher.

may have different types of test implementation that require completely different approaches to execute them. To each type of test (i.e. tests developed in different languages) corresponds a “category”. For any category of tests you have, you’ll need a sp

Several launchers can live together. You just need to add all the necessary launchers (.jar files) in Install_folder>/bin/launchers


Default launchersXStudio is provided with several

simple_manual.jar

testcomplete7.jar

testpartner.jar

visualstudio.jar

beanshell.jar

squishqt.jar

squishweb.jar

marathon.jar

success.jar

Launchers can execute any kind of tests (scripts, native code

means that your already existing test suites are usable as they are. The only condition is to develop ) a tiny component allowing X


Several launchers can live together. You just need to add all the necessary launchers (.jar files) in >/bin/launchers folder.


Default launchersis provided with several

Description

For manual testing (step

For manual testing (all

For autoit test s

For perl test scripts

For TCL test scripts

For AutomatedQA

For Compuware

For Microsoft

For Beanshell

For Froglogic

For Froglogic

For JUnit v3 tests

For JUnit v4 tests

For PyUnit tests

For NUnit tests (so covering any VisualBasic.NET

For TestNG tests

For Jalian® Marathon

For executable tests

Simulation launcher (returns random results)

Simulation launcher (returns only success results)

Table 9

can execute any kind of tests (scripts, native codemeans that your already existing test suites are usable as they are. The only condition is to develop

XStudio to interact with the test. This piece of code is called


Several launchers can live together. You just need to add all the necessary launchers (.jar files) in folder.


Default launchers is provided with several ready-

testing (step-by-

testing (all-in-one procedure )

test scripts

test scripts

test scripts

AutomatedQA® TestComplete 7

Compuware® TestPartner

Microsoft® VisualStudio Team System

Beanshell test scripts

Froglogic® Squish for Qt

Froglogic® Squish for

tests

tests

tests

tests (so covering any VisualBasic.NET)

tests

Marathon tests

executable tests


mulation launcher (returns only success results)

– XStudio’s D

can execute any kind of tests (scripts, native codemeans that your already existing test suites are usable as they are. The only condition is to develop

to interact with the test. This piece of code is called

may have different types of test implementation that require completely different approaches to execute them. To each type of test (i.e. tests developed in different languages) corresponds a “category”. For any category of tests you have, you’ll need a specific Launcher.

Several launchers can live together. You just need to add all the necessary launchers (.jar files) in


-to-use launchers:

-step procedure)

one procedure )

® TestComplete 7 tests

TestPartner tests

VisualStudio Team System

Squish for Qt tests

Squish for the web tests

tests (so covering any .NET tests:

tests



XStudio’s Default Launchers

can execute any kind of tests (scripts, native code, interpreted code, xml etc.). This means that your already existing test suites are usable as they are. The only condition is to develop


may have different types of test implementation that require completely different approaches to execute them. To each type of test (i.e. tests developed in different languages) corresponds a

ecific Launcher.



launchers:

step procedure)

tests

VisualStudio Team System (Test Edition) tests

tests: C#, J#, C++/CLI



efault Launchers

, interpreted code, xml etc.). This means that your already existing test suites are usable as they are. The only condition is to develop



ecific Launcher.



(Test Edition) tests

C++/CLI, Managed C++

, interpreted code, xml etc.). This means that your already existing test suites are usable as they are. The only condition is to develop





Managed C++,

6.1.1 Manual lThe manual testing lnot automateentered in the system to request the user to perform some questions.

6.1.1.1 Configuration

The manual Parameter

General > step fails

Timing > delay

These values can be changed while creating the campaign session from

6.1.1.2 Control Bar

The manual launchercontrol bar includes the following buttons:

• Go b

• Go back to previous testcase:

• Restart current testcase:

• Pause current testcase:

• Resume current testcase:

• Go forward to next testcase:

• Go forward to next test:

6.1.1.3 T

While executing manual (and do verifications). The instance, it is possible to give 10 minute

Manual launcheranual testing launcher

not automated and consist in just following some procedures.entered in the system to request the user to perform some

Configuration

manual.xml file allows pre

General > set testcase

delay between


Control Bar

The manual launcher includes a control bar allowing controlling the execution of the tests. Thecontrol bar includes the following buttons:

Go back to previous test

Go back to previous testcase:

Restart current testcase:

Pause current testcase:

Resume current testcase:

Go forward to next testcase:

Go forward to next test:

Timeout per test

executing manual (and do verifications). The instance, it is possible to give 10 minute

auncher (manual.jar)auncher can be used as is

d and consist in just following some procedures.entered in the system to request the user to perform some

Configuration

file allows pre-configuring the launch

testcase as failed as soon as one

between testcases (ms


Control Bar

includes a control bar allowing controlling the execution of the tests. Thecontrol bar includes the following buttons:

ack to previous test :


Restart current testcase:

Pause current testcase:

Resume current testcase:

Go forward to next testcase:

Go forward to next test:

per test

executing manual tests, the launcher provides instructions to the operator to execute actions (and do verifications). The tests are configurable so that some timing restrictions can be added. For instance, it is possible to give 10 minute

(manual.jar)can be used as is to

d and consist in just following some procedures.entered in the system to request the user to perform some

configuring the launch

as failed as soon as one

ms)


includes a control bar allowing controlling the execution of the tests. Thecontrol bar includes the following buttons:


, the launcher provides instructions to the operator to execute actions configurable so that some timing restrictions can be added. For

instance, it is possible to give 10 minutes maximum for the operator to execute the

(manual.jar) to perform manual testing i

d and consist in just following some procedures. The launcher will use the testplan as entered in the system to request the user to perform some manual

configuring the launcher with some default values:

Description

as failed as soon as one If set to true, when one step fails in the testcase the complete testcase is set as failed and the remaining steps are skipped. Default value i

Default value


includes a control bar allowing controlling the execution of the tests. The


s maximum for the operator to execute the

perform manual testing if your tests are currently The launcher will use the testplan as manual tasks and to answer some

er with some default values:

Description

If set to true, when one step fails in the testcase the complete testcase is set as failed and the remaining steps are skipped.

Default value is: false

Default value is: 0

These values can be changed while creating the campaign session from XStudio




f your tests are currently The launcher will use the testplan as

tasks and to answer some

er with some default values:


XStudio.




f your tests are currently The launcher will use the testplan as

tasks and to answer some





actions/verifications (i.e. you need to test that a message appears on the screen of the SUT in less than 10 minutes; if the operator doesn't validate that he saw that message within the 10 minutes then the test is If you want to set some specific timeouts to a test you just need to associate to this test one or several of the following attributes (with a value for the timeout):

• timeout test description (ms)

• timeout test prerequisites (ms)

• timeout testcases execution (ms)implied by the testcases in this test

When manually executed,

Note also, that all these attributes are session, you can overwrite any of these default values (on each test if necessary) to customize onecampaign session execution:

actions/verifications (i.e. you need to test that a message appears on the screen of the SUT in less than 10 minutes; if the operator doesn't validate that he saw that message within the 10 minutes then the test is automatically set as failed).

If you want to set some specific timeouts to a test you just need to associate to this test one or several of the following attributes (with a value for the timeout):

timeout test description (ms)

timeout test prerequisites (ms)

timeout testcases execution (ms)implied by the testcases in this test

When manually executed,


actions/verifications (i.e. you need to test that a message appears on the screen of the SUT in less than 10 minutes; if the operator doesn't validate that he saw that message within the 10 minutes

automatically set as failed).


timeout test description (ms)

timeout test prerequisites (ms)

timeout testcases execution (ms)implied by the testcases in this test

When manually executed, each test will be applied with their specific timeout values.



automatically set as failed).


timeout test description (ms): maximum delay to validate

timeout test prerequisites (ms): maximum delay to validate the test prerequisites

timeout testcases execution (ms): maximum delay to execute any actions or verifications implied by the testcases in this test

each test will be applied with their specific timeout values.

Note also, that all these attributes are dynamic. This means that when creating the campaign session, you can overwrite any of these default values (on each test if necessary) to customize one



: maximum delay to validate

: maximum delay to validate the test prerequisites

: maximum delay to execute any actions or verifications


. This means that when creating the campaign session, you can overwrite any of these default values (on each test if necessary) to customize one


If you want to set some specific timeouts to a test you just need to associate to this test one or

: maximum delay to validate the test description

: maximum delay to validate the test prerequisites






the test description : maximum delay to validate the test prerequisites






: maximum delay to validate the test prerequisites : maximum delay to execute any actions or verifications


6.1.1.4 Tutorial

In this tutorial we will learn how to setup from scratch a manual test suite, execute it and analyze the results.

6.1.1.4.1

If it does not already exist, know the name of your PC, use the

command on Linux.

• in the


• enter the name of the folder (i.e. “

• in the tree, select the newly added folder (i.e. “


• enter the hostname or the static ip address of your local host and submit Then create a

• in the


• enter the name of the company (i.e. “

• in the tree, select the newly added company (i.e. “




• on the right panel, click

• enter the name (i.e. “

6.1.1.4.2

We now need to c

• in the



Tutorial: Creating and executing manual tests

In this tutorial we will learn how to setup from scratch a manual test suite, execute it and analyze

Declare the agent

If it does not already exist, know the name of your PC, use the

command on Linux. This name/IP address must be ping

in the Agents tree,


enter the name of the folder (i.e. “

in the tree, select the newly added folder (i.e. “


ter the hostname or the static ip address of your local host and submit

Then create a SUT (System Under Test):

in the SUTs tree,


enter the name of the company (i.e. “

in the tree, select the newly added company (i.e. “




on the right panel, click

enter the name (i.e. “

Create a dedicated category for manual tests

We now need to create a category in the test tree

in the Tests tree,



: Creating and executing manual tests


the agent and the SUT

If it does not already exist, create an agentknow the name of your PC, use the

This name/IP address must be ping

tree, select the root folder






(System Under Test):



enter the name of the company (i.e. “






enter the name (i.e. “My Browser


reate a category in the test tree






and the SUT

agent with the exact name (or the IP Address) of your PC. To know the name of your PC, use the ipconfig /all

This name/IP address must be ping

e root folder


enter the name of the folder (i.e. “France Office


on the right panel, click on the create agent


(System Under Test):

the root folder

on the right panel, click on the create company

enter the name of the company (i.e. “Acme



enter the name of the folder (i.e. “QA”) and submit


on the create sut button

My Browser”) and the version (i.e. “


reate a category in the test tree that will gather all the manual tests.

the root folder

on the right panel, click on the create category



with the exact name (or the IP Address) of your PC. To ipconfig /all command on Windows and

This name/IP address must be ping-able from the network.


France Office”) and submit

in the tree, select the newly added folder (i.e. “France Office

agent button


create company button

Acme”) and submit

in the tree, select the newly added company (i.e. “Acme


”) and submit

in the tree, select the newly added folder (i.e. “QA”)

button

”) and the version (i.e. “


that will gather all the manual tests.

ategory button



with the exact name (or the IP Address) of your PC. To command on Windows and

able from the network.

”) and submit

France Office”)


button

nd submit

Acme”)

”) and the version (i.e. “1.0”) of the SUT and submit




with the exact name (or the IP Address) of your PC. To command on Windows and ifconfig

able from the network.


”) of the SUT and submit



with the exact name (or the IP Address) of your PC. To ifconfig

”) of the SUT and submit

• enter the name of the category

• enter the description of the category. You can use the formatting tools (the text. Later, in reports this text will appear correctly formatted.

• enter the launcher to be associated with that category:

• click on submit

6.1.1.4.3

To create a test:

• in the tree, select the newly added categor





• a dialog box including three tabs is displayed

• fill the canonical path blank).

• fill the use the formatting tools (wikicorrectly formatted and submit

enter the name of the category

enter the description of the category. You can use the formatting tools (the text. Later, in reports this text will appear correctly formatted.

enter the launcher to be associated with that category:

click on submit

Create a test

To create a test:

in the tree, select the newly added categor





a dialog box including three tabs is displayed

fill the Details tab with the name (i.e. “canonical path blank).

fill the Testplan use the formatting tools (wikicorrectly formatted and submit

enter the name of the category



Create a test







tab with the name (i.e. “canonical path blank).

tab with the prerequisites and the general description of the teuse the formatting tools (wiki-correctly formatted and submit

enter the name of the category (i.e. “Manual tests





enter the name of the folder (i.e. “My browser tests


on the right panel, click on the create test


tab with the name (i.e. “

tab with the prerequisites and the general description of the te-style) to format the text. Later, in reports this text

correctly formatted and submit

Manual tests”).


enter the launcher to be associated with that category: manual

in the tree, select the newly added category (i.e. “Manual tests


My browser tests”) and submit

in the tree, select the newly added folder (i.e. “My browser tests

button


tab with the name (i.e. “basic test”) and priority of the test (leave the

tab with the prerequisites and the general description of the testyle) to format the text. Later, in reports this text


manual.jar

Manual tests”)

”) and submit

My browser tests”)

”) and priority of the test (leave the

tab with the prerequisites and the general description of the testyle) to format the text. Later, in reports this text

enter the description of the category. You can use the formatting tools (wiki-style) to format


tab with the prerequisites and the general description of the test. You can style) to format the text. Later, in reports this text will appear

style) to format


st. You can will appear


• in the tree, select a newly added test (i.e. “

• on the right panel, click

• a dialog box including two tabs is displayed

• fill the within a test), name (i.e. “use the formatting tools (wikicorrectly formatted. Do not forget to check the test are NOT executed when running a campaign. In caImplemented

• select the testcase:


in the tree, select a newly added test (i.e. “

on the right panel, click


fill the Details tab with the index (defining the order in which the testcases will be executed within a test), name (i.e. “use the formatting tools (wikicorrectly formatted. Do not forget to check the test are NOT executed when running a campaign. In caImplemented checkbox.

select the Testplantestcase:

o add a step� in the tree, select the root folder

� click on the � enter the descript

o add parameters (opt)� in the tree, select the � click on the � enter the description of the parameter and submit� repeat the operation if you need to specify more parameters

o add checks (opt.)




tab with the index (defining the order in which the testcases will be executed within a test), name (i.e. “first test caseuse the formatting tools (wiki-correctly formatted. Do not forget to check the test are NOT executed when running a campaign. In ca

checkbox.

Testplan tab and define all the steps and checks that will be needed in this

add a step: in the tree, select the root folder

click on the create enter the descript

add parameters (opt)in the tree, select the click on the create enter the description of the parameter and submitrepeat the operation if you need to specify more parameters

add checks (opt.):


on the create testcase


tab with the index (defining the order in which the testcases will be executed first test case”) and general description of th

-style) to format the text. Later, in reports this text will appear correctly formatted. Do not forget to check the test are NOT executed when running a campaign. In ca

tab and define all the steps and checks that will be needed in this


create step button enter the description of the step and submit

add parameters (opt): in the tree, select the parameters

create parameterenter the description of the parameter and submitrepeat the operation if you need to specify more parameters

in the tree, select a newly added test (i.e. “basic test”)

testcase button


tab with the index (defining the order in which the testcases will be executed ”) and general description of th

style) to format the text. Later, in reports this text will appear correctly formatted. Do not forget to check the Implementedtest are NOT executed when running a campaign. In ca



button ion of the step and submit

parameters node parameter button

enter the description of the parameter and submitrepeat the operation if you need to specify more parameters

tab with the index (defining the order in which the testcases will be executed ”) and general description of th

style) to format the text. Later, in reports this text will appear Implemented checkbox. Non

test are NOT executed when running a campaign. In case of manual test, always check the


ion of the step and submit

node

enter the description of the parameter and submit repeat the operation if you need to specify more parameters

tab with the index (defining the order in which the testcases will be executed ”) and general description of the testcase.

style) to format the text. Later, in reports this text will appear checkbox. Non-implemented

se of manual test, always check the


repeat the operation if you need to specify more parameters

tab with the index (defining the order in which the testcases will be executed e testcase. You can

style) to format the text. Later, in reports this text will appear implemented

se of manual test, always check the


• click on submit

• immediately, the testcase appears in the sub You can create other testcases and other tests using the s

6.1.1.4.4

• In the test tree, select the newly created test press the "start" button

• Check in the

• Select the "

• Select a pre

• If no configuration are available

• Press the Submit button

Some popup dialog boxes will assertions

� in the tree� click on � click on the new operator and click on the � enter the description of the check and submit� repeat the operation if you need to specify more che

many different boolean operators as you want)o repeat the operation

click on submit

immediately, the testcase appears in the sub

You can create other testcases and other tests using the s

Run an individual

In the test tree, select the newly created test press the "start" button

Check in the Agent

Select the "My brow

Select a pre-existing configur

If no configuration are available

o click on the o a dialog box is displayedo enter the name of the configurationo fill in all the forms displaye

Press the Submit button

popup dialog boxes will

in the tree, select the click on one of the click on the new operator and click on the enter the description of the check and submitrepeat the operation if you need to specify more chemany different boolean operators as you want)

repeat the operation



an individual test

In the test tree, select the newly created test press the "start" button

Agent tab of the pop up window that your PC is selected by default

My browser 1.0" in the SUT tre

existing configuration in the Configuration tab

If no configuration are available

click on the create configurationa dialog box is displayedenter the name of the configurationfill in all the forms displaye

Press the Submit button

popup dialog boxes will ask the operator

, select the checksone of the create

click on the new operator and click on the enter the description of the check and submitrepeat the operation if you need to specify more chemany different boolean operators as you want)

repeat the operation for every step



test

In the test tree, select the newly created test

tab of the pop up window that your PC is selected by default

" in the SUT tre

ation in the Configuration tab


create configuration a dialog box is displayed enter the name of the configurationfill in all the forms displayed and submit

ask the operator to execute some operations and/or verify some

checks node boolean operators

click on the new operator and click on the enter the description of the check and submitrepeat the operation if you need to specify more chemany different boolean operators as you want)

for every step and submit

immediately, the testcase appears in the sub-tree on the left panel

You can create other testcases and other tests using the same procedure.

In the test tree, select the newly created test (i.e. “basic test


" in the SUT tree


button

enter the name of the configuration d and submit

to execute some operations and/or verify some

boolean operators buttons click on the new operator and click on the create checkenter the description of the check and submit repeat the operation if you need to specify more chemany different boolean operators as you want)

and submit

tree on the left panel

ame procedure.

basic test”) (not the test case




buttons check button

repeat the operation if you need to specify more checks (you can mix as

(not the test case!) and



cks (you can mix as

) and


• When the test is finished, you can control the results in the campaign tree (a new test

camp

• In the content tab, you can select a test, then a test case (in the dynamic subcheck the complete log of the execution

6.1.1.4.5

At this stage yotestsuite? XStudioFor this, two different elements must be distinguished: test campaign and campaign s

• The

• A new adds to the test campaign notion, the target on which the tests will be performed and how. The "how"

To create a campaign:



• a dialog box including two tabs is displayed

• fill the

• in the

• click on submit

• immediately, the campaign appears in the tree To create a campaign session:


• on the right panel, cli

• a dialog box including seven tabs is displayed

• fill the

• (opt.) select the

• select the the tests on the local host, leave the default selection (that should already match the local host)

• select the

• select the involved in this campaign session. Once a campaign session is created, it is impossible (by purpose) to change the configurations associated.

• (opt.) if needed, modify the dynamic attributes values in t

• (opt.) select the campaign session will be completed

When the test is finished, you can control the results in the campaign tree (a new test campaign and campaign session have been automatically created in the campaign tree)

In the content tab, you can select a test, then a test case (in the dynamic subcheck the complete log of the execution

Creating a test campaign

At this stage you know how to individually run aXStudio provides a very efficient and simple way of managing manual test campaign.

For this, two different elements must be distinguished: test campaign and campaign s

The test campaign

A new campaign sessionadds to the test campaign notion, the target on which the tests will be performed and how. The "how" is characterized

To create a campaign:




fill the Details tab

in the Content tab, select all the tests you want to be part of this

click on submit


To create a campaign session:


on the right panel, cli

a dialog box including seven tabs is displayed

fill the Details tab with the name of the session.


select the Agentthe tests on the local host, leave the default selection (that should already match the local host)

select the SUT tab and pick the SUT on which the session will be run

select the Configurationinvolved in this campaign session. Once a campaign session is created, it is impossible (by purpose) to change the configurations associated.

(opt.) if needed, modify the dynamic attributes values in t

(opt.) select the campaign session will be completed

When the test is finished, you can control the results in the campaign tree (a new test aign and campaign session have been automatically created in the campaign tree)



know how to individually run aprovides a very efficient and simple way of managing manual test campaign.


test campaign defines just a list of tests to be executed

campaign session will be created each time the campaign will be performed. It adds to the test campaign notion, the target on which the tests will be performed and how.

characterized by some dynamic configurable parameters.







To create a campaign session:




tab with the name of the session.

Test operator

Agent tab and pick the agthe tests on the local host, leave the default selection (that should already match the local


Configuration tab ainvolved in this campaign session. Once a campaign session is created, it is impossible (by purpose) to change the configurations associated.


(opt.) select the CC Emails tab and check some users to receive a notification when the campaign session will be completed




know how to individually run aprovides a very efficient and simple way of managing manual test campaign.


defines just a list of tests to be executed

will be created each time the campaign will be performed. It adds to the test campaign notion, the target on which the tests will be performed and how.

by some dynamic configurable parameters.




with the name of the campaign




ck on the create campaign session



Test operator tab and pick the user who will run the session

tab and pick the agent on which the session will be run. If you wish to run the tests on the local host, leave the default selection (that should already match the local


tab and pick the configuration you which for each category involved in this campaign session. Once a campaign session is created, it is impossible (by purpose) to change the configurations associated.


tab and check some users to receive a notification when the campaign session will be completed


In the content tab, you can select a test, then a test case (in the dynamic sub

know how to individually run a manual test. But how to deal with a complete provides a very efficient and simple way of managing manual test campaign.






campaign icon


with the name of the campaign



campaign session




ent on which the session will be run. If you wish to run the tests on the local host, leave the default selection (that should already match the local


nd pick the configuration you which for each category involved in this campaign session. Once a campaign session is created, it is impossible (by purpose) to change the configurations associated.




In the content tab, you can select a test, then a test case (in the dynamic sub

manual test. But how to deal with a complete provides a very efficient and simple way of managing manual test campaign.





tab, select all the tests you want to be part of this campaign

campaign session button




nd pick the configuration you which for each category involved in this campaign session. Once a campaign session is created, it is impossible (by

(opt.) if needed, modify the dynamic attributes values in the Attributes



In the content tab, you can select a test, then a test case (in the dynamic sub-tree) and


For this, two different elements must be distinguished: test campaign and campaign session:



campaign





Attributes tab



tree) and


ession:





• click on submit

• immediately, the campaign session appears in the tree in idle state

6.1.1.4.6

To run a campaign session:

• in the tree, select a campaign session

• on the right panel, click on the start button

• immediately, the Test campaign details screen appears and will display real time the results of testing

click on submit

immediately, the campaign session appears in the tree in idle state


a campaign session:






a campaign session:













immediately, the Test campaign details screen appears and will display real time the immediately, the Test campaign details screen appears and will display real time the immediately, the Test campaign details screen appears and will display real time the

6.1.2 Simple manual launcher (simple_manual.jarThe simple manual testing launcher differs from the Manual testing launcher by the fact that it will not prompt the user for each step and check but instead will show the complete testcase procedure and will just Refer to the manual launcher section for the configuration and tutorial.

6.1.3 Autoit Launcher (autoit.jar)The Autoit It has been tested with


The autoit.xml Parameter

General > Test root path

General > Asynchronous timeout (in seconds)

AutoIt > AutoIt install path



1) Each test in equal to the name of the test. 2) The .au3This allows the script to execute different routines depending The interpreter is executed by the launcher using this syntax: AutoIt3.exe <testRootPath>/<testPath>/<testName>.au3 /debug /testcaseIndex=<testcaseIndex> 3) When the Indeed, the executions of the autoit scripts are asynchronous. to know when the test is completed. A timeout of 10 minutes is predefined. If the create the test_completed.txtcrashed and skip 4) the .au3actions performed by the test as well as the result of each action. This flauncher and all the information will be passed/stored automatically in log.txt MUST respect a specific format: Each

Simple manual launcher (simple_manual.jarimple manual testing launcher differs from the Manual testing launcher by the fact that it will

not prompt the user for each step and check but instead will show the complete testcase procedure just ask the user

Refer to the manual launcher section for the configuration and tutorial.

Autoit Launcher (autoit.jar) launcher allows

It has been tested with AutoIt

Configuration

xml file allows pre


Asynchronous timeout (in seconds)



Requirements

1) Each test in XStudioequal to the name of the test.

.au3 script must be able to parse This allows the script to execute different routines depending The interpreter is executed by the launcher using this syntax:

utoIt3.exe <testRootPath>/<testPath>/<testName>.au3 /debug /testcaseIndex=<testcaseIndex>

3) When the .au3 has executed all its ahe executions of the autoit scripts are asynchronous.

to know when the test is completed. A timeout of 10 minutes is predefined. If the test_completed.txt

rashed and skips it.

.au3 script must generate a actions performed by the test as well as the result of each action. This flauncher and all the information will be passed/stored automatically in

MUST respect a specific format: Each


not prompt the user for each step and check but instead will show the complete testcase procedure ask the user for a result. The setup/conf


Autoit Launcher (autoit.jar)launcher allows interfacing

AutoIt 3.

Configuration

file allows pre-configuring the launcher with some default values:





Requirements

XStudio must have his dedicated equal to the name of the test.

be able to parse This allows the script to execute different routines depending The interpreter is executed by the launcher using this syntax:


has executed all its ahe executions of the autoit scripts are asynchronous.

to know when the test is completed. A timeout of 10 minutes is predefined. If the test_completed.txt within t

script must generate a log.txtactions performed by the test as well as the result of each action. This flauncher and all the information will be passed/stored automatically in



not prompt the user for each step and check but instead will show the complete testcase procedure The setup/conf


Autoit Launcher (autoit.jar)interfacing with AutoIt


Description

This must indicate where are located all theThis is a root path. Each test in path that wilThis path MUST not include Default value is:

This must indicates the maximum time the system will wait for the test to complete. Default value

This must indicate where is installed AutoIt on the host. Default value is:


have his dedicated

be able to parse the argument This allows the script to execute different routines depending The interpreter is executed by the launcher using this syntax:


has executed all its action, it MUST create an empty he executions of the autoit scripts are asynchronous.

to know when the test is completed. A timeout of 10 minutes is predefined. If the within the first 10 minutes, then the launcher consider

log.txt during its execution. This file MUST describe all the actions performed by the test as well as the result of each action. This flauncher and all the information will be passed/stored automatically in



not prompt the user for each step and check but instead will show the complete testcase procedure The setup/configuration is exactly the same.


Autoit Launcher (autoit.jar) AutoIt (.au3) scripts.


Description

This must indicate where are located all theThis is a root path. Each test in path that will be appended to This path MUST not include

Default value is: C:/my_autoit_scripts

This must indicates the maximum time the system will wait for the test to complete.

Default value is: 600

This must indicate where is installed AutoIt on the host.

Default value is: C:/tools/


have his dedicated .au3 script. The name of the script MUST be

the argument testcaseIndexThis allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:


ction, it MUST create an empty he executions of the autoit scripts are asynchronous. T

to know when the test is completed. A timeout of 10 minutes is predefined. If the he first 10 minutes, then the launcher consider

during its execution. This file MUST describe all the actions performed by the test as well as the result of each action. This flauncher and all the information will be passed/stored automatically in

MUST respect a specific format: Each line MUST include the strings “


not prompt the user for each step and check but instead will show the complete testcase procedure iguration is exactly the same.


scripts.


This must indicate where are located all theThis is a root path. Each test in XStudio

l be appended to this path.This path MUST not include an ending slash

C:/my_autoit_scripts

This must indicates the maximum time the system will wait


C:/tools/autoit-3


script. The name of the script MUST be

testcaseIndex passed during interpretation. on the testcase


ction, it MUST create an empty test_coThis mechanism allows the launcher

to know when the test is completed. A timeout of 10 minutes is predefined. If the he first 10 minutes, then the launcher consider

during its execution. This file MUST describe all the actions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be passed/stored automatically in the XStudio

line MUST include the strings “

Simple manual launcher (simple_manual.jar) imple manual testing launcher differs from the Manual testing launcher by the fact that it will

not prompt the user for each step and check but instead will show the complete testcase procedure iguration is exactly the same.


This must indicate where are located all the .au3XStudio has a canonical

his path. ending slash.

C:/my_autoit_scripts



XStudio.


passed during interpretation. testcase index.


test_completed.txthis mechanism allows the launcher

to know when the test is completed. A timeout of 10 minutes is predefined. If the .au3 script did not he first 10 minutes, then the launcher considers the test has

during its execution. This file MUST describe all the ile will be parsed by the XStudio database.

line MUST include the strings “[Success]

imple manual testing launcher differs from the Manual testing launcher by the fact that it will not prompt the user for each step and check but instead will show the complete testcase procedure

.au3 scripts. has a canonical




passed during interpretation.


mpleted.txt file. his mechanism allows the launcher

script did not the test has

during its execution. This file MUST describe all the ile will be parsed by the

database. The [Success]",

"[Failure]" or "flagged as passed or failed.

6.1.3.3 Tutorial

In this tutorial, we will learn to run some AutoIt test scripts.

6.1.3.3.1

Install AutoIt in the folder We will modify one of the example script provided with AutoIt.Copy the file calculator_test Insert in the beginning of the file

#include <File.au3>

$RESULT_FILENAME = "Log.txt"

FileDelete($RESULT_FILENAME)

$FLAG_FILENAME = "test_completed.txt"

FileDelete($FLAG_FILENAME)

And insert at the end of the file:

; log a success

logFileAndConsoleWrite($RESULT_FILENAME, "[Log] fir

logFileAndConsoleWrite($RESULT_FILENAME, "[Log] second message")

logFileAndConsoleWrite($RESULT_FILENAME, "[Success] testcase succeeded")

;logFileAndConsoleWrite($RESULT_FILENAME, "[failure] testcase failed")

; create the test_completed.txt f

FileOpen($FLAG_FILENAME, 1)

Func logFileAndConsoleWrite($logFile, $input)

ConsoleWrite($input & @CRLF)

_FileWriteLog($logFile, $input)

EndFunc

6.1.3.3.2

• create a category

• under this category, with

6.1.3.3.3

" or "[Log]" or the line will not flagged as passed or failed.

Tutorial: Creating and executing AutoIt tests


Prerequisites

Install AutoIt in the folder

We will modify one of the example script provided with AutoIt.Copy the file C:\Program Files

_test.au3.

Insert in the beginning of the file

#include <File.au3>






; log a success










EndFunc

Create a dedicate

create a category

nder this category, with a canonical path set to


" or the line will not flagged as passed or failed.

Creating and executing AutoIt tests


Prerequisites

Install AutoIt in the folder C:\Program f

We will modify one of the example script provided with AutoIt.Program Files

Insert in the beginning of the file calculator

#include <File.au3>















Create a dedicated category for AutoIt tests and create

create a category AutoIt associated to

nder this category, create (somewhere in the treecanonical path set to /Examples


" or the line will not be treated. Based



Program files\AutoIt3

We will modify one of the example script provided with AutoIt.Program Files\AutoIt3|Examples

calculator_test.au3








; create the test_completed.txt file





d category for AutoIt tests and create

associated to the launcher

somewhere in the treeExamples.


be treated. Based on this



AutoIt3

We will modify one of the example script provided with AutoIt. AutoIt3|Examples\calculator.au3

.au3 the following lines o







the launcher autoit.jar

somewhere in the tree) a test

on this information, the


calculator.au3

the following lines of code:

logFileAndConsoleWrite($RESULT_FILENAME, "[Log] first message")





autoit.jar

a test with name

information, the testcase

and rename it as

f code:

st message")




d category for AutoIt tests and create a test

with name calculator

testcase will be

and rename it as

calculator_test and

• create a campaign including only the test

• create a

6.1.3.3.4

Run the campaign session

create a campaign including only the test

create a campaign session specifying in the configuration:o Test root path: o AutoIt install path:



create a campaign including only the test

campaign session specifying in the configuration:Test root path: C:/ Program FilesAutoIt install path: C:/



create a campaign including only the test calculator

campaign session specifying in the configuration:Program Files C:/Program Files


calculator_test

campaign session specifying in the configuration: /AutoIt3

Program Files/AutoIt3

_test

campaign session specifying in the configuration:

6.1.4 Perl Launcher (perl.jar)The Perl launcher allows It has been


The perl.xml Parameter



Perl > Perl

These values can be changed while creating the camp


1) Each test in to the name of the test. 2) The .pl script This allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax: perl.exe <testRootPath>/<testPath>/<testName>.pl /debug /testcaseIndex=<testcaseIndex> 3) When the Indeed, the to know when the test is completed. A timeout of 10 minutes is predefined. If create the test_completed.crashed and skip 4) the .pl script must generate a performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be passed/stored automatically in MUST respect a specific format: Each"[Log]" or the line will not be treated. Based passed or failed.

Perl Launcher (perl.jar)launcher allows

It has been tested with ActivePerl

Configuration

xml file allows pre



install path


Requirements

1) Each test in XStudio to the name of the test.

script must be able to parse This allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:

erl.exe <testRootPath>/<testPath>/<testName>.pl /debug /testcaseIndex=<testcaseIndex>

3) When the .pl has executed all its ache executions of the Perl scripts are

to know when the test is completed. A timeout of 10 minutes is predefined. If test_completed.

crashed and skips it.

script must generate a med by the test as well as the result of each action. This file will be parsed by the launcher

and all the information will be passed/stored automatically in MUST respect a specific format: Each

" or the line will not be treated. Based passed or failed.

Perl Launcher (perl.jar)launcher allows interfacing with

ActivePerl 5.8.9

Configuration





Requirements

must have his dedicated

be able to parse This allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:


has executed all its acexecutions of the Perl scripts are

to know when the test is completed. A timeout of 10 minutes is predefined. If test_completed.txt within the first 10 minutes, then the launcher considers the test has

script must generate a log.txtmed by the test as well as the result of each action. This file will be parsed by the launcher

and all the information will be passed/stored automatically in MUST respect a specific format: Each

" or the line will not be treated. Based

Perl Launcher (perl.jar) with .perl scripts.

5.8.9.


Description

This must indicate where are located all theThis is a root path. Each test in path that will be appended to This path MUST not include Default value is:

This must indicatfor the test to complete. Default value is:

This must indicate where is installed Default value is:


must have his dedicated .

be able to parse the argument This allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:


has executed all its actions, it MUST create an empty executions of the Perl scripts are asynchronous. This mechanism allows the launcher

to know when the test is completed. A timeout of 10 minutes is predefined. If within the first 10 minutes, then the launcher considers the test has

log.txt during its execution. This file MUST describe all the actions med by the test as well as the result of each action. This file will be parsed by the launcher

and all the information will be passed/stored automatically in MUST respect a specific format: Each line MUST include the strin

" or the line will not be treated. Based on this

scripts.


Description

This must indicate where are located all theThis is a root path. Each test in path that will be appended to This path MUST not include

Default value is: C:/my_



This must indicate where is installed

Default value is: C:/Perl/bin


.pl script. The name of the script MUST be equal

the argument testcaseIndexThis allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:


tions, it MUST create an empty asynchronous. This mechanism allows the launcher


during its execution. This file MUST describe all the actions med by the test as well as the result of each action. This file will be parsed by the launcher

and all the information will be passed/stored automatically in line MUST include the strin

on this information, the


This must indicate where are located all theThis is a root path. Each test in XStudiopath that will be appended to this path.This path MUST not include an ending slash

C:/my_perl_scripts

es the maximum time the system will wait

This must indicate where is installed Perl

Perl/bin

aign session from XStudio

script. The name of the script MUST be equal

testcaseIndex passed during interpretatThis allows the script to execute different routines depending on the testcase


tions, it MUST create an empty test_completed.txtasynchronous. This mechanism allows the launcher



and all the information will be passed/stored automatically in the XStudio line MUST include the strings “[Success]



This must indicate where are located all the .pXStudio has a canonical

his path. ending slash.

_scripts


Perl on the host.

XStudio.


passed during interpretattestcase index.


test_completed.txtasynchronous. This mechanism allows the launcher

to know when the test is completed. A timeout of 10 minutes is predefined. If the .pl script did not within the first 10 minutes, then the launcher considers the test has


database. The [Success]", "[Failure]

testcase will be flagged as

.pl scripts. has a canonical


on the host.




test_completed.txt file. asynchronous. This mechanism allows the launcher

script did not within the first 10 minutes, then the launcher considers the test has


The log.txt [Failure]" or

will be flagged as

6.1.5 TCL Launcher (tcl.jar)The TCL launcher allows interfacing with It has been


The tcl.xml Parameter



Tcl > Tcl install path



1) Each test in to the name of the test. 2) The .tcl script This allows the script to execute different routines The interpreter is executed by the launcher using this syntax: tclsh85.exe <testRo 3) When the Indeed, the to know when the test is completed. A timeout of 10 minutes is predefined. If the create the test_completed.crashed and skip 4) the .tcl actions performed by the test as well as the result of each actionlauncher and all the information will be passed/stored automatically in log.txt MUST respect a specific format: Each"[Failure]" or "flagged as passed or failed.

TCL Launcher (tcl.jar)launcher allows interfacing with

It has been tested with TCL

Configuration

xml file allows pre



install path


Requirements

1) Each test in XStudio must have his dedicated to the name of the test.

script must be able to parse This allows the script to execute different routines The interpreter is executed by the launcher using this syntax:

.exe <testRootPath>/<testPath>/<testName>.tcl

3) When the .tcl has executed all its ache executions of the TCL

to know when the test is completed. A timeout of 10 minutes is predefined. If the test_completed.

crashed and skips it.

script must generate a actions performed by the test as well as the result of each actionlauncher and all the information will be passed/stored automatically in

MUST respect a specific format: Each" or "[Log]" or the line w

flagged as passed or failed.

TCL Launcher (tcl.jar)launcher allows interfacing with

TCL 8.5.

Configuration





Requirements


be able to parse This allows the script to execute different routines The interpreter is executed by the launcher using this syntax:

otPath>/<testPath>/<testName>.tcl

has executed all its acexecutions of the TCL scripts are asynchronous. This mechanism allows the launcher

to know when the test is completed. A timeout of 10 minutes is predefined. If the test_completed.txt within the first 10 minutes, then the launcher considers the test has

script must generate a log.txtactions performed by the test as well as the result of each actionlauncher and all the information will be passed/stored automatically in

MUST respect a specific format: Each" or the line will not be treated. Based

flagged as passed or failed.

TCL Launcher (tcl.jar) launcher allows interfacing with TCL (.tcl)


Description

This must indicate where are located all theThis is a root path. Each test in path that will be appended to This path MUST not include an ending slash Default value is:

This must indicates the maximum time the system will wait for the test to Default value is:



must have his dedicated .tc

be able to parse the argument This allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:

otPath>/<testPath>/<testName>.tcl

has executed all its actions, it MUST create an emscripts are asynchronous. This mechanism allows the launcher

to know when the test is completed. A timeout of 10 minutes is predefined. If the within the first 10 minutes, then the launcher considers the test has

log.txt during its execution. This file MUST describe all the actions performed by the test as well as the result of each actionlauncher and all the information will be passed/stored automatically in

MUST respect a specific format: Eachill not be treated. Based

l) scripts.


Description

This must indicate where are located all theThis is a root path. Each test in path that will be appended to This path MUST not include an ending slash





Default value is: C:/Tcl/bin


tcl script. The name of the script MUST be equal

the argument testcaseIndexdepending on the

The interpreter is executed by the launcher using this syntax:

otPath>/<testPath>/<testName>.tcl /debug /testcaseIndex=<testcaseIndex>

tions, it MUST create an emscripts are asynchronous. This mechanism allows the launcher


during its execution. This file MUST describe all the actions performed by the test as well as the result of each actionlauncher and all the information will be passed/stored automatically in

MUST respect a specific format: Each line MUST include the strings “ill not be treated. Based on this



C:/my_tcl_scripts


This must indicate where is installed Tcl

/bin



testcaseIndex passed during interpretation. depending on the testcase

/debug /testcaseIndex=<testcaseIndex>

tions, it MUST create an empty test_completed.txtscripts are asynchronous. This mechanism allows the launcher


during its execution. This file MUST describe all the actions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be passed/stored automatically in the XStudio

line MUST include the strings “on this information, the


This must indicate where are located all the .tclXStudio has a canonical

his path. This path MUST not include an ending slash.


Tcl on the host.

XStudio.


passed during interpretation. testcase index.


test_completed.txtscripts are asynchronous. This mechanism allows the launcher

to know when the test is completed. A timeout of 10 minutes is predefined. If the .tcl script did not within the first 10 minutes, then the launcher considers the test has

during its execution. This file MUST describe all the . This file will be parsed by the

XStudio database. line MUST include the strings “[Success]


.tcl scripts. has a canonical


on the host.




test_completed.txt file. scripts are asynchronous. This mechanism allows the launcher

script did not within the first 10 minutes, then the launcher considers the test has

during its execution. This file MUST describe all the . This file will be parsed by the


testcase will be

6.1.6 AutomatedQA(testcomplete7.jar)The AutomatedQA

6.1.6.1 Configurati

The testcomplete7 Parameter

TestComplete7path

TestComplete7 > TestComplete log directory path



The tests are runConsoleGUI.cmd /u:<testPath> /routine:<testName> /tcIndex:<testcaseIndex> /sutName:<SutName> The test will be marked as passed or failed depending on the return code of the execution.The TestComplete xml log is also attached to the testcase execution in XStudio.

AutomatedQA(testcomplete7.jar)

AutomatedQA® TestComplete v7

Configuration

testcomplete7.xml

TestComplete7 > TestComplete

TestComplete7 > TestComplete log directory path


Requirements

tests are executed by the launcher using this syntax:

runConsoleGUI.cmd /u:<testPath> /routine:<testName> /tcIndex:<testcaseIndex> /sutName:<SutName>

st will be marked as passed or failed depending on the return code of the execution.The TestComplete xml log is also attached to the testcase execution in XStudio.

AutomatedQA® (testcomplete7.jar)

TestComplete v7

on

file allows pre

Complete install

TestComplete7 > TestComplete log


Requirements

executed by the launcher using this syntax:

runConsoleGUI.cmd /u:<testPath> /routine:<testName> /tcIndex:<testcaseIndex>


TestComplete v7 Launcher

TestComplete v7 launcher allows interfacing with


Description

install This must indicate where are located all theTestCompleteXStudio this path. This path MUST not include an ending slash Default value is:

TestComplete7 > TestComplete log Default value is:






launcher allows interfacing with


Description

This must indicate where are located all theTestComplete scripts. This is a root path. Each test

has a canonical path that will be appended to

This path MUST not include an ending slash

Default value is: C:/Automation/Runner

Default value is: C:/Automation/Tests/TestProject/Log






launcher allows interfacing with TestComplete


This must indicate where are located all thescripts. This is a root path. Each test


This path MUST not include an ending slash

Automation/Runner

Automation/Tests/TestProject/Log





TestComplete tests.


This must indicate where are located all thescripts. This is a root path. Each test


This path MUST not include an ending slash.

Automation/Runner


XStudio.




tests.


This must indicate where are located all the scripts. This is a root path. Each test in



st will be marked as passed or failed depending on the return code of the execution.

6.1.7 CompuwareThe Compuware


The testpartner Parameter

TestPartner

TestPartner

TestPartner

TestPartner

TestPartner

TestPartner

These values can be changed while creating the campaign session fr


The tests are C:\Program Files<testRootPath> The test will be marked as passed or failed dependiThe xml file is parsed by the launcher. XStudio.

CompuwareCompuware® TestPartner

Configuration

testpartner.xml file allows pre

TestPartner > Test root path

TestPartner > projectName

TestPartner > username

TestPartner > password

TestPartner > dsn

TestPartner > detailedLogPath


Requirements

The tests are executed by the launcher using this syntax:

Program Files\TestPartner<testRootPath>/<testName>

The test will be marked as passed or failed dependiThe xml file is parsed by the launcher.

Compuware® TestPartner Launcher (testpartner.jar)TestPartner launcher al

Configuration


Description

> Test root path This must indicate where are located all thea root path. Each test in be appended to This path MUST include an ending slash Default value is:

projectName Default value is:

me Default value is:

password Default value is:

Default value is:

detailedLogPath Default value is:


Requirements


TestPartner\tc.exe -<testName>

The test will be marked as passed or failed dependiThe xml file is parsed by the launcher.

TestPartner Launcher (testpartner.jar)launcher allows interfacing with


Description

This must indicate where are located all thea root path. Each test in be appended to This path MUST include an ending slash

Default value is:

Default value is:

Default value is:

Default value is:

Default value is:

Default value is:



-d <dsn> -u <username>

The test will be marked as passed or failed dependiThe xml file is parsed by the launcher. The xml log is also attached to the testcase execution in

TestPartner Launcher (testpartner.jar)lows interfacing with


This must indicate where are located all thea root path. Each test in XStudiobe appended to this path. This path MUST include an ending slash

Default value is: C:/tests_repository/

Default value is: myProject

Default value is: JohnDoe

Default value is: myPassword

Default value is: dsn

Default value is: C:/logs/log.xml



u <username> -

The test will be marked as passed or failed depending on the log file generated by TestPartnerThe xml log is also attached to the testcase execution in

TestPartner Launcher (testpartner.jar)lows interfacing with TestPartner


This must indicate where are located all theXStudio has a canonical path that will

This path MUST include an ending slash.

tests_repository/

assword

logs/log.xml


-p <password>

the log file generated by TestPartnerThe xml log is also attached to the testcase execution in

TestPartner Launcher (testpartner.jar)TestPartner scripts.


This must indicate where are located all the test scripts.has a canonical path that will

XStudio.

p <password> -r <projectName>

the log file generated by TestPartnerThe xml log is also attached to the testcase execution in

TestPartner Launcher (testpartner.jar)

scripts. This is has a canonical path that will

r <projectName> -s

the log file generated by TestPartner. The xml log is also attached to the testcase execution in

6.1.8 MicrosoftThe Microsoft


The visualstudio Parameter


General > Library name

VisualStudio

VisualStudio



The tests are <runnerPath>/resultsfile:<results And this is executed from the working directory The test will be marked as passed or failed depending on the log file generated by VisualStudio. The xml file is parsed by the launcher. The xml log and the execution talso attached to the testcase execution in XStudio.

Microsoft®Microsoft® VisualStudio

Configuration

visualstudio.xml file allows pre

> Test root path

Library name

VisualStudio > Runner path

VisualStudio > results file path


Requirements


Path> /testcontainer:<resultsFilePath>

And this is executed from the working directory

The test will be marked as passed or failed depending on the log file generated by VisualStudio. The xml file is parsed by the launcher. The xml log and the execution talso attached to the testcase execution in XStudio.

® VisualStudio Launcher (visualstudio.jar)VisualStudio launcher allows inte

Configuration


Description

> Test root path This must inpath. appended to This path MUST not include Default value is:

Library name Default value is:

Runner path This must Default value is:C:/PrograMSTest.

results file path This must indicate where Default value is:


Requirements


/testcontainer:<libraryName> /test:<testPath>



VisualStudio Launcher (visualstudio.jar)launcher allows inte


Description

This must indicate where are located the testspath. Each test in appended to this path.This path MUST not include

Default value is: C:/

Default value is: my_tests

This must indicate where is the Visual Studio executable

Default value is: rogram Files

MSTest.exe

This must indicate where




Name> /test:<test

And this is executed from the working directory <testRootPath>


VisualStudio Launcher (visualstudio.jar)launcher allows interfacing with VisualStudio


dicate where are located the testsEach test in XStudio has a canonical path that will be

his path. This path MUST not include an

C:/my_test_repository

my_tests.dll

indicate where is the Visual Studio executable

m Files/Microsoft Visual Studio/

This must indicate where is located

C:/my_test_rep



Name> /test:<testPath>.<testName>

<testRootPath>


VisualStudio Launcher (visualstudio.jar)VisualStudio


dicate where are located the testshas a canonical path that will be

an ending slash

my_test_repository


Microsoft Visual Studio/

located the results text file

my_test_repository /testResults


.<testName>

The test will be marked as passed or failed depending on the log file generated by VisualStudio. The xml file is parsed by the launcher. The xml log and the execution trace of the command are

VisualStudio Launcher (visualstudio.jar)VisualStudio scripts.


dicate where are located the tests. This is a root has a canonical path that will be

ending slash.


Microsoft Visual Studio/Common7/IDE/

the results text file

testResults.trx

XStudio.

The test will be marked as passed or failed depending on the log file generated by VisualStudio. race of the command are

VisualStudio Launcher (visualstudio.jar)

. This is a root has a canonical path that will be


ommon7/IDE/

trx

The test will be marked as passed or failed depending on the log file generated by VisualStudio. race of the command are

6.1.9 Beanshell Launcher (beanshell.jar)The BeanshellIt is provided with an additional module that first download and instaeasily remove this part and recompile the launcher).It has been


The beanshell Parameter

General > Te

Beanshell > Beanshell install path

Installers > installers

Installers >

Installers >



The launcher starts by downloading a s<installerTemplateNcopied in <folderContainingtheInstallers>with the option 1) Each test in equal to the name of the test. 2) The .bshThis allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax: The tests are java -cp <beanshel<testcaseIndex> <sutVersion> And this is executed from the working directory 3) When the Indeed, the to know when the test is completed. 4) the .bshactions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be passed/stored automatically in log.txt MUST respect a specific format: Each

Beanshell Launcher (beanshell.jar)Beanshell launcher allows interfacing with

It is provided with an additional module that first download and instaeasily remove this part and recompile the launcher).It has been tested with Beanshell 2.0

Configuration

beanshell.xml file allows pre



Installers > Folder containing the

Installers > Download server U

Installers > Installer template name


Requirements

The launcher starts by downloading a sTemplateName

folderContainingtheInstallers>with the option /S (This is supposed that the installer is a NSIS installer).

1) Each test in XStudioequal to the name of the test.

bsh script must be able to parse This allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:


<beanshellInstallPath><testcaseIndex> <sutVersion>


3) When the .bsh has executed all its ache executions of the TCL

now when the test is completed.

bsh script must generate a formed by the test as well as the result of each action. This file will be parsed by the

launcher and all the information will be passed/stored automatically in MUST respect a specific format: Each

Beanshell Launcher (beanshell.jar)launcher allows interfacing with

It is provided with an additional module that first download and instaeasily remove this part and recompile the launcher).

Beanshell 2.0

Configuration


st root path


Folder containing the

Download server URL

Installer template name


Requirements

The launcher starts by downloading a same> (using the SUTVersion)

folderContainingtheInstallers>(This is supposed that the installer is a NSIS installer).

XStudio must have his dedicated equal to the name of the test.

be able to parse This allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:


lInstallPath> bsh.Interpreter<testcaseIndex> <sutVersion>


has executed all its acexecutions of the TCL scripts are asynchronous. This mechanism allows the launcher

now when the test is completed.

script must generate a log.txtformed by the test as well as the result of each action. This file will be parsed by the


Beanshell Launcher (beanshell.jar)launcher allows interfacing with beanshell


Beanshell 2.0b4


Description

This must indicate where are located all thescripts. This is a root path. Each test in canonical path that will be appended to This path MUST not include an ending slash Default value is:

This must indicate where is the Beanshell jar file Default value is:

Default value is:

Default value is:

Default value is:


The launcher starts by downloading a setup program and install the product. The product (using the SUTVersion)

folderContainingtheInstallers>. Then the product is installed by running the executable (This is supposed that the installer is a NSIS installer).


be able to parse the testcaseIndexThis allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:


bsh.Interpreter <testRootPath>/<testPath>/<testName>.bsh

And this is executed from the working directory <testRootPath>/<testPath>

has executed all its actions, it MUST create an empty scripts are asynchronous. This mechanism allows the launcher

log.txt during its execution. This file MUST describe all the formed by the test as well as the result of each action. This file will be parsed by the


Beanshell Launcher (beanshell.jar)beanshell test scripts.



This must indicate where are located all thescripts. This is a root path. Each test in canonical path that will be appended to This path MUST not include an ending slash

Default value is: C:/beanshell/clie

This must indicate where is the Beanshell jar file

Default value is: C:/tools/beanshell

Default value is: C:/products

Default value is: //NAS/Builds/trunk

Default value is: product-


etup program and install the product. The product (using the SUTVersion) is downloaded from

Then the product is installed by running the executable (This is supposed that the installer is a NSIS installer).

must have his dedicated .bsh script. The name of the script MUST be

testcaseIndex argument pThis allows the script to execute different routines depending on the The interpreter is executed by the launcher using this syntax:


<testRootPath>/<testPath>/<testName>.bsh

<testRootPath>/<testPath>

tions, it MUST create an empty scripts are asynchronous. This mechanism allows the launcher

during its execution. This file MUST describe all the formed by the test as well as the result of each action. This file will be parsed by the

launcher and all the information will be passed/stored automatically in MUST respect a specific format: Each line MUST include the st

Beanshell Launcher (beanshell.jar) test scripts.

It is provided with an additional module that first download and install the product but you can


This must indicate where are located all thescripts. This is a root path. Each test in canonical path that will be appended to This path MUST not include an ending slash

beanshell/client


C:/tools/beanshell-2.0b4/bsh

products

//NAS/Builds/trunk

-setup-%version%.exe


etup program and install the product. The product is downloaded from <downloadServerURL>

Then the product is installed by running the executable (This is supposed that the installer is a NSIS installer).


argument passed during interpretation. This allows the script to execute different routines depending on the testcase


<testRootPath>/<testPath>

tions, it MUST create an empty test_compscripts are asynchronous. This mechanism allows the launcher


launcher and all the information will be passed/stored automatically in the XStudioline MUST include the st

ll the product but you can


This must indicate where are located all the Beanshellscripts. This is a root path. Each test in XStudiocanonical path that will be appended to this path. This path MUST not include an ending slash.


2.0b4/bsh-2.0b4.jar

%version%.exe

XStudio.

etup program and install the product. The product <downloadServerURL>

Then the product is installed by running the executable


assed during interpretation. testcase index.


test_completed.txtscripts are asynchronous. This mechanism allows the launcher


XStudio database. line MUST include the strings “[Success]

ll the product but you can

Beanshell XStudio has a

2.0b4.jar

etup program and install the product. The product <downloadServerURL> and

Then the product is installed by running the executable


assed during interpretation.


leted.txt file. scripts are asynchronous. This mechanism allows the launcher



"[Failure]" or "flagged as passed or failed.

" or "[Log]" or the line will not be treated. Based flagged as passed or failed.

" or the line will not be treated. Based flagged as passed or failed.

" or the line will not be treated. Based " or the line will not be treated. Based on thison this information, the information, the testcasetestcase will be

6.1.10 FroglogicThe FroglogicIt has been


The squish Parameter


Squish > Squish install path

Squish > Squish lib

Advanced > snooze factor

Advanced > squishrunner/_squishrunner processes after each testcase

Advanced > squishserver/_squishserver processes after each test

Advanced > webhook/_webhook processes after each testcase (Squish for web)

Advanced > process after each testcase (Squish for web)

Advanced > process after each testcase (Squish for web)


FroglogicFroglogic® Squish

It has been tested with Squish

Configuration

squish.xml file allows pre



Squish > Squish libraries

> snooze factor

Advanced > Force kill squish squishrunner/_squishrunner

ocesses after each testcase

Advanced > Force kill squish erver/_squishserver

processes after each test

Advanced > Force kill squish webhook/_webhook processes after each testcase (Squish for web)

Advanced > Force kill iexplore process after each testcase (Squish

Advanced > Force kill ieuser process after each testcase (Squish


Froglogic® Squish Squish launcher allows interfacing with Squish

Squish-3.4.4.

Configuration




raries path

> snooze factor

Force kill squish squishrunner/_squishrunner

ocesses after each testcase

Force kill squish erver/_squishserver

processes after each test

Force kill squish webhook/_webhook processes after each testcase (Squish for web)

Force kill iexplore process after each testcase (Squish

Force kill ieuser process after each testcase (Squish


Squish Launcher (squishlauncher allows interfacing with Squish


Description



This must indicate where are located the used by all squish test. This parameter is optional. Default value is:

This must (hence affecting the “time to replay”)30% means that a snooze of 1 second in the script will actually last 300 ms. Default value is:

Force kill squish If set to Trueby the launcher after the execution of each testcase.should not be used in normal conditions. Default value is:

Force kill squish If set to Trueby the launcher after the execution of each all testcases)conditions. Default value is:

Force kill squish webhook/_webhook processes after

If set to True(if still alive) by the testcase. This should not be used in n Default value is:

Force kill iexplore process after each testcase (Squish

If set to Truestill alive) by the testcase. This sh Default value is:

Force kill ieuser process after each testcase (Squish

If set to Truealive) by the This should not be used in normal conditions. Default value is:


Launcher (squishlauncher allows interfacing with Squish


Description

This must indicate where are located all theis a root path. Each test in

path that will be appended to This path MUST not include an ending slash



Default value is: C:/tools/squish

This must indicate where are located the used by all squish test. This parameter is optional.

Default value is: C:/src/s

must indicate the fa(hence affecting the “time to replay”)30% means that a snooze of 1 second in the script will actually last 300 ms.

Default value is: 30 (%)

True, the squish runner will be killed (if still alive) launcher after the execution of each testcase.

should not be used in normal conditions.

Default value is: False

True, the squish server will be killed (if still alive) launcher after the execution of each

all testcases). This should not be used in normal


True, the squish (if still alive) by the launcher after the execution of each

This should not be used in n


True, all the iexplorestill alive) by the launcher after the execution of each

This should not be used in normal conditions.


True, all the ieuseralive) by the launcher after the execution of each This should not be used in normal conditions.



Launcher (squish.jar)launcher allows interfacing with Squish tests.


This must indicate where are located all theis a root path. Each test in XStudio

path that will be appended to this path.This path MUST not include an ending slash

This must indicate where is installed squish

C:/tools/squish-web_win32

This must indicate where are located the used by all squish test. This parameter is optional.

C:/src/squish/lib

indicate the factor applied to all snooze calls (hence affecting the “time to replay”)30% means that a snooze of 1 second in the script will

, the squish runner will be killed (if still alive) launcher after the execution of each testcase.


, the squish server will be killed (if still alive) launcher after the execution of each

This should not be used in normal

, the squish webhook processeslauncher after the execution of each

This should not be used in n

iexplore processeslauncher after the execution of each

ould not be used in normal conditions.

ieuser processeslauncher after the execution of each



.jar)


This must indicate where are located all the SquishXStudio has a canonical


squish/

web_win32

This must indicate where are located the script commonly used by all squish test. This parameter is optional.

ctor applied to all snooze calls (hence affecting the “time to replay”). The default value of 30% means that a snooze of 1 second in the script will

, the squish runner will be killed (if still alive) launcher after the execution of each testcase.


, the squish server will be killed (if still alive) launcher after the execution of each test (including


processes will be killed launcher after the execution of each


processes will be killed (if launcher after the execution of each


processes will be killed (if still launcher after the execution of each


XStudio.

Squish tests. has a canonical

script commonly used by all squish test. This parameter is optional.

ctor applied to all snooze calls The default value of

30% means that a snooze of 1 second in the script will

, the squish runner will be killed (if still alive) launcher after the execution of each testcase. This

, the squish server will be killed (if still alive) test (including


will be killed launcher after the execution of each

ormal conditions.

will be killed (if launcher after the execution of each


will be killed (if still launcher after the execution of each testcase.


1) Each testbe equal to The tests are First of all the squish server is run:<squishInstallPath>/bin/squishserver.exe Then, the test are executed:<squishInstallPath>tst_<testName> The launcher set an environment variable that all libraries necessary for the ma

6.1.10.3 Tutoria

In this tutorial, we will learn to run some can be applied for any other squish application (Java, Qt, Web et

6.1.10.3.1

Install Squish for JavaCreate a file

function global

}

Using Squish IDEcalled suite_fake In this directory, edit shared/scripts/objects.js and add the following content:

function

}

Add to the testsuite, 2 tests: tst_failure which contains the following code:

function main() {

} tst_success

function main() {

Requirements

1) Each testcase in XStudiobe equal to tst_<testName>

The tests are executed by the launcher using the following

First of all the squish server is run:<squishInstallPath>/bin/squishserver.exe

Then, the test are executed:<squishInstallPath>/bin/squishruntst_<testName> --snoozeFactor <snoozeFactor>

The launcher set an environment variable that all libraries necessary for the ma

Tutorial: Creating and executing Squish


6.1.10.3.1 Prerequisites

Squish for Java in the folder Create a file utils.js in the folder

function globalLog() {

test.log("Global

Using Squish IDE create a new test suite (using javascript languagesuite_fake in C:\src

In this directory, edit shared/scripts/objects.js and add the following content:

function localLog() {

test.log("Log example"

test.warning("Warning example", "Some warnings to highlight");

Add to the testsuite, 2 tests:

which contains the following code:

function main() {

source(findFile("scripts", "utils.js"));

source(findFile("scripts", "objects.js"));

globalLog();

localLog();

test.compare(1, 1);

test.compare(2, 2);

test.compare(3, 4);

tst_success which contains the following code:

function main() {

source(findFile("scripts", "utils.


globalLog();

localLog();

Requirements

XStudio must have his dedicated <testName>.

cuted by the launcher using the following

First of all the squish server is run: <squishInstallPath>/bin/squishserver.exe

Then, the test are executed: /squishrunner.exe

snoozeFactor <snoozeFactor>

The launcher set an environment variable that all libraries necessary for the main script to be executed are in the path.

l: Creating and executing Squish


Prerequisites

in the folder C:in the folder C:\src

Log() {

test.log("Global Log example

create a new test suite (using javascript languagesrc\squish\testsuites


Log() {

test.log("Log example", "Some useful information");


Add to the testsuite, 2 tests:


function main() {


ndFile("scripts", "objects.js"));

();

test.compare(1, 1);

test.compare(2, 2);

test.compare(3, 4);


function main() {

source(findFile("scripts", "utils.


();


cuted by the launcher using the following

<squishInstallPath>/bin/squishserver.exe

ner.exe --testsuite <snoozeFactor <snoozeFactor> --

The launcher set an environment variable SQUISH_SCRIPT_DIRin script to be executed are in the path.


In this tutorial, we will learn to run some Squish test scripts.can be applied for any other squish application (Java, Qt, Web et

C:\tools\squishsrc\squish\lib

Log example", "Traces");

create a new test suite (using javascript languagetestsuites.


, "Some useful information");








must have his dedicated squish script. The name of th

cuted by the launcher using the following syntax

testsuite <testRootPath>/<testPath> --reportgen xml,_tmp.xml

SQUISH_SCRIPT_DIRin script to be executed are in the path.


test scripts. We will use Squish for Java but this can be applied for any other squish application (Java, Qt, Web et

squish-3.4.4-java-win32lib the following content:

", "Traces");

create a new test suite (using javascript language






js"));


script. The name of th

syntaxes:

testRootPath>/<testPath> reportgen xml,_tmp.xml

SQUISH_SCRIPT_DIR set to <squishLibin script to be executed are in the path.

tests

We will use Squish for Java but this can be applied for any other squish application (Java, Qt, Web etc.)

win32 the following content:

create a new test suite (using javascript language, with no AUT application




script. The name of the script MUST

testRootPath>/<testPath> --testcase

<squishLibrary

We will use Squish for Java but this

, with no AUT application


e script MUST

e

raryPath> so

We will use Squish for Java but this

, with no AUT application)

} After these operations, the

AUT

CLASS

CLASSPATH

CWD

ENVVARS

HOOK_SUB_PROCESSES

LANGUAGE

NAMINGSCHEME

TEST_CASES

USE_WHITELIST

WRAPPERS

You have now some very basic squish testsfailure.

6.1.10.3.2

• create a category

• under this category, create (somewhere in the tree) failure

6.1.10.3.3

• create a campaign including the tests

test.compare(1, 1);

test.compare(2, 2);

test.compare(3, 3);

After these operations, the

CLASS

SSPATH

ENVVARS

HOOK_SUB_PROCESSES

LANGUAGE

NAMINGSCHEME

TEST_CASES

USE_WHITELIST

WRAPPERS

You have now some very basic squish tests

6.1.10.3.2 Create a dedicated category for

create a category

under this category, create (somewhere in the tree) failure with a canonical path set to

6.1.10.3.3 Creating a test campaign

create a campaign including the tests

test.compare(1, 1);

test.compare(2, 2);

test.compare(3, 3);

After these operations, the suite.conf

=

=

=

=

= envvars

HOOK_SUB_PROCESSES = 1

= JavaScript

= MULTIPROP

= tst_

= 1

= Java

You have now some very basic squish tests

Create a dedicated category for

create a category Squish associated to the launcher

under this category, create (somewhere in the tree) with a canonical path set to


create a campaign including the tests

suite.conf file should contain:

= envvars

= JavaScript

= MULTIPROP

= tst_success tst_

= Java

You have now some very basic squish tests: one returning a

Create a dedicated category for

associated to the launcher

under this category, create (somewhere in the tree) with a canonical path set to suite_fake


create a campaign including the tests success

file should contain:

tst_failure

ne returning always a

Create a dedicated category for Squish tests and

associated to the launcher squish

under this category, create (somewhere in the tree) twosuite_fake.

success and failure

lways a success and

Squish tests and create two

squish.jar

two tests with name

failure

cess and the other one

create two test

with names success

the other one a

tests

success and

• create a campaign session with the default configuration settings.

6.1.10.3.4


create a campaign session with the default configuration settings.

6.1.10.3.4 Run a campaign session







create a campaign session with the default configuration settings.create a campaign session with the default configuration settings.

6.1.11 JUnit v3 Launcher (junit3.jar)The Junit v3It has been Refer to JUnit v4 for the details as these 2 launchers are very similar.

6.1.12 JUnit v4 Launcher (The Junit v4It has been


The junit4.xml Parameter


General > Additional classpath

JUnit > Java install path

JUnit > JUnit jar



The tests are <javaInstallPath>/org.junit.runner.JUnitCore And this is executed from the working directory The test will be marked as file is parsed by the launcher. The log and the execution trace of the command are also attached to the testcase execution in XStudio.

6.1.12.3 Tutorial: Creating and executing JUnit tests

TODO

JUnit v3 Launcher (junit3.jar)Junit v3 launcher allows interfacing with

It has been tested with JUnit3.0

Refer to JUnit v4 for the details as these 2 launchers are very similar.

JUnit v4 Launcher (Junit v4 launcher allows interfacing with

It has been tested with JUnit

Configuration

xml file allows pre


Additional classpath


JUnit > JUnit jar path


Requirements

The tests are executed by the launcher

Path>/bin/java.exe org.junit.runner.JUnitCore


The test will be marked as file is parsed by the launcher. The log and the execution trace of the command are also attached to the testcase execution in XStudio.


JUnit v3 Launcher (junit3.jar)launcher allows interfacing with

JUnit3.0


JUnit v4 Launcher (her allows interfacing with

JUnit 4.7

Configuration



Additional classpath



Requirements

executed by the launcher

bin/java.exe –classpath org.junit.runner.JUnitCore <testPath>.<testName>


The test will be marked as passed or failed depending on the log file generated by JUnit. The text file is parsed by the launcher. The log and the execution trace of the command are also attached to the testcase execution in XStudio.


JUnit v3 Launcher (junit3.jar)launcher allows interfacing with JUnit v3


JUnit v4 Launcher (junit4her allows interfacing with JUnit v


Description

This must indicate where are locThis is a root path. Each test in path that will be appended to This path MUST not include an ending slash Default value is:

This must indicatenecessary to test the SUT.separated by ‘;’. Default value is:

This must indicate the path to the java install. Default value is:

This must indicate the path to the JUnit library. Default value is:



classpath <junitJarPath<testPath>.<testName>


passed or failed depending on the log file generated by JUnit. The text file is parsed by the launcher. The log and the execution trace of the command are also attached to


JUnit v3 Launcher (junit3.jar) JUnit v3 tests.


junit4.jar) JUnit v4 tests.


Description

This must indicate where are locThis is a root path. Each test in path that will be appended to This path MUST not include an ending slash

Default value is: C:/build/classes

This must indicate potential additional jar classpath necessary to test the SUT.separated by ‘;’.

Default value is:

This must indicate the path to the java install.

Default value is: C:/Program Files/Java/jdk1.6.0

This must indicate the path to the JUnit library.

Default value is: C:/junit


using this syntax:

junitJarPath>;<additionalClassPath>;<testPath>.<testName>

<testRootPath>






build/classes

potential additional jar classpath necessary to test the SUT. This can contain several path


C:/Program Files/Java/jdk1.6.0


C:/junit-4.7/junit-4.7.jar


;<additionalClassPath>;




ated all the SquishXStudio has a canonical


potential additional jar classpath This can contain several path


C:/Program Files/Java/jdk1.6.0_06


4.7.jar

XStudio.

;<additionalClassPath>;<testRootPath


Squish tests. has a canonical

potential additional jar classpath This can contain several path

_06

testRootPath>


6.1.13 PyUnit Launcher (pyunit.jar)The PyUnitIt has been


The pyunit. Parameter


PyUnit > Python install path

PyUnit > PyUnit install path



The tests are <pythonInstallPath>/python.exe <pyunitInstallPath>/unittest.py <testPath>.<testName> And this is executed from the working directory The test will be marked as passed or failed depending on the log file generated by PyUnit. The text file is parsed by the launcher. The log and the execution trace of the command are also attachedthe testcase execution in XStudio.

6.1.13.3 Tutorial: Creating and executing PyUnit tests

TODO

PyUnit Launcher (pyunit.jar)PyUnit launcher allows interfacing with

It has been tested with PyUnit 1.4.1

Configuration

.xml file allows pre

l > Test root path




Requirements


<pythonInstallPath>/python.exe <pyunitInstallPath>/unittest.py <testPath>.<testName>

this is executed from the working directory

The test will be marked as passed or failed depending on the log file generated by PyUnit. The text file is parsed by the launcher. The log and the execution trace of the command are also attachedthe testcase execution in XStudio.


PyUnit Launcher (pyunit.jar)launcher allows interfacing with

PyUnit 1.4.1

Configuration


l > Test root path




Requirements



this is executed from the working directory

The test will be marked as passed or failed depending on the log file generated by PyUnit. The text file is parsed by the launcher. The log and the execution trace of the command are also attachedthe testcase execution in XStudio.


PyUnit Launcher (pyunit.jar)launcher allows interfacing with PyUnit


Description

This must indicate where are located all theThis is a root path. Each test in path that will be appended to This path MUST not include an ending slash Default value is:C:/Program Files

This must indicate the path to Python install Default value is:C:/Python26

This must indicate the path to PyUnit install Default value is:C:/Program Files/PyUnit/




this is executed from the working directory <testRootPath>

The test will be marked as passed or failed depending on the log file generated by PyUnit. The text file is parsed by the launcher. The log and the execution trace of the command are also attached


PyUnit Launcher (pyunit.jar) PyUnit tests.


Description


Default value is: Program Files/PyUnit/pyunit

This must indicate the path to Python install

Default value is: Python26

This must indicate the path to PyUnit install

Default value is: Program Files/PyUnit/




<testRootPath>





/PyUnit/pyunit-1.4.1/examples



Program Files/PyUnit/pyunit-1.4.1






This must indicate where are located all the PyUnitXStudio has a canonical


1.4.1/examples



1.4.1

XStudio.



PyUnit tests. has a canonical

1.4.1/examples

The test will be marked as passed or failed depending on the log file generated by PyUnit. The text file is parsed by the launcher. The log and the execution trace of the command are also attached to

6.1.14 NUnit Launcher (nunit.jar)The NUnitVisualBasic.NET

It has been


The nunit.xml Parameter


General > Assembly dll

NUnit > .NET version

NUnit > NUnit console path



The tests are <nunitConsolePa<testRootPath>/<assemblyName> And this is executed from the working directory The test will be marked as passed or failed depending on the log file generated by NUnit. Tfile is parsed by the launcher. The log and the execution trace of the command are also attached to the testcase execution in XStudio.

6.1.14.3 Tutorial: Creating and executing NUnit tests

TODO

NUnit Launcher (nunit.jar)NUnit launcher allows interfacing with

VisualBasic.NET). It has been tested with NUnit 2.

Configuration

xml file allows pre


General > Assembly dll

NUnit > .NET version



Requirements


<nunitConsolePath>/bin/net<testRootPath>/<assemblyName>


The test will be marked as passed or failed depending on the log file generated by NUnit. Tfile is parsed by the launcher. The log and the execution trace of the command are also attached to the testcase execution in XStudio.


NUnit Launcher (nunit.jar)launcher allows interfacing with

NUnit 2.5.2

Configuration





Requirements


th>/bin/net-<netVersion>/nunit<testRootPath>/<assemblyName>


The test will be marked as passed or failed depending on the log file generated by NUnit. Tfile is parsed by the launcher. The log and the execution trace of the command are also attached to the testcase execution in XStudio.


NUnit Launcher (nunit.jar)launcher allows interfacing with


Description

This must indicate where are located all theThis is a root path. Each test in path that will be appended to This path MUST not include an ending slash Default value is:C:/Program Files/NUnit 2.5.2/bin/net

Default value is:

Default value is:

Default value is:



<netVersion>/nunit-console.exe /run:<testPath>.<testName>


The test will be marked as passed or failed depending on the log file generated by NUnit. Tfile is parsed by the launcher. The log and the execution trace of the command are also attached to


NUnit Launcher (nunit.jar) launcher allows interfacing with .NET tests (


Description


Default value is: Program Files/NUnit 2.5.2/bin/net

Default value is: nunit.util.tests.dll

alue is: 2.0

Default value is: C:/Program Files/NUnit 2.5.2



console.exe /run:<testPath>.<testName>

<testRootPath>



tests (C#, J#, C++/CLI



Program Files/NUnit 2.5.2/bin/net

nunit.util.tests.dll

Program Files/NUnit 2.5.2





C++/CLI, Managed C++


This must indicate where are located all the SquishXStudio has a canonical


Program Files/NUnit 2.5.2/bin/net-2.0/tests

Program Files/NUnit 2.5.2

XStudio.



Managed C++,

Squish tests. canonical


The test will be marked as passed or failed depending on the log file generated by NUnit. The text file is parsed by the launcher. The log and the execution trace of the command are also attached to

6.1.15 TestNG Launcher (testng.jar)The TestNGIt has been


The testng. Parameter



TestNG > Java install path

TestNG > TestNG jar path



The tests are <javaInstallPath>/bin/java.exe org.testng.TestNG And this is executed from the working directory The test will be markeThe xml file is parsed by the launcher. The logcommand are also attached to the testcase execution in XStudio.

6.1.15.3 Tutori

TODO

TestNG Launcher (testng.jar)TestNG launcher allows inte

It has been tested with TestNG 5.10

Configuration

.xml file allows pre




TestNG jar path


Requirements

The tests are executed by the launch

<javaInstallPath>/bin/java.exe org.testng.TestNG –testclass <testPath>.<testName>


The test will be marked as passed or failed depending on the file is parsed by the launcher. The log

command are also attached to the testcase execution in XStudio.

Tutorial: Creating and e

TestNG Launcher (testng.jar)launcher allows interfacing with

TestNG 5.10

Configuration





TestNG jar path


Requirements


<javaInstallPath>/bin/java.exe –classpath <testNGJarPath>;<additionalClassPath>;<testRootPath> testclass <testPath>.<testName>


d as passed or failed depending on the file is parsed by the launcher. The log


al: Creating and e

TestNG Launcher (testng.jar)rfacing with TestNG


Description


This must indicate potential addnecessary to test the SUT. This can contain several path separated by ‘;’. Default value is:

This must indicate the path to the java install. Default value is:

This must indicate the path to the TestNG library. Default value is:


er using this syntax:

classpath <testNGJarPath>;<additionalClassPath>;<testRootPath> testclass <testPath>.<testName>


d as passed or failed depending on the file is parsed by the launcher. The logs, HTML reports


al: Creating and executing TestNG

TestNG Launcher (testng.jar) TestNG tests.


Description


Default value is: C:/build/classes

This must indicate potential addnecessary to test the SUT. This can contain several path separated by ‘;’.

Default value is:


Default value is: C:/Program Files/Java/jdk1.6.0_06

This must indicate the path to the TestNG library.

Default value is: C:/testing


er using this syntax:

classpath <testNGJarPath>;<additionalClassPath>;<testRootPath> testclass <testPath>.<testName>

<testRootPath>

d as passed or failed depending on the s, HTML reports


xecuting TestNG



build/classes

This must indicate potential addnecessary to test the SUT. This can contain several path


Program Files/Java/jdk1.6.0_06


testing-5.10/testing


classpath <testNGJarPath>;<additionalClassPath>;<testRootPath>

d as passed or failed depending on the xml log file generated by TestNG. s, HTML reports and the execution trace of the


xecuting TestNG tests


This must indicate where are located all the TestNGXStudio has a canonical


This must indicate potential additional jar classpath necessary to test the SUT. This can contain several path




5.10/testing-5.10-jdk15.jar

XStudio.


log file generated by TestNG. and the execution trace of the

estNG tests. has a canonical

itional jar classpath necessary to test the SUT. This can contain several path


jdk15.jar


log file generated by TestNG. and the execution trace of the

6.1.16 JalianThe Jalian®It has been


The marathon Parameter


Marathon > Marathon home

Marathon > Marathon classpath

Marathon > Java install path

These values can be changed while creating the c


The tests are <javaInstallPath>/bin/java.exe Dmarathon.home=”<marathonHome>” <marathonClassPa<testRootPath>/marathon_report.xml < And this is executed from the working directory The test will be marked as passed or failed depending on the xml log file generated by The xml file is parsed by the launcher. The logs and the execution trace of the command are also attached to the testcase execution in XStudio.

6.1.16.3 Tutorial: Creating and executing

TODO

Jalian® Marathon Launcher (marathon.jar)® Marathon launcher allows interfacing with

It has been tested with Marathon 1.2.1.1

Configuration

marathon.xml file allows pre


Marathon > Marathon home

Marathon > Marathon classpath

Marathon > Java install path


Requirements


<javaInstallPath>/bin/java.exe Dmarathon.home=”<marathonHome>” <marathonClassPath> net.sourceforge.marathon.Main <testRootPath>/marathon_report.xml <


The test will be marked as passed or failed depending on the xml log file generated by The xml file is parsed by the launcher. The logs and the execution trace of the command are also attached to the testcase execution in XStudio.

Tutorial: Creating and executing

Marathon Launcher (marathon.jar)launcher allows interfacing with

Marathon 1.2.1.1

Configuration

file allows pre-configuring the launcher w

Description

General > Test root path This must indicate where are located all theThis is a root path. Each test in that will be appended to This path MUST not inc Default value is:

Marathon > Marathon home This must indicate the install path of Marathon. Default value is:

Marathon > Marathon classpath This must indicate the classpath used by the tests. Default value is:C:/marathonC:/marathonC:/marathonC:/marathonC:/marathonC:/marathonC:/marathonC:/marathonC:/marathonC:/marathonC:/marathon

Marathon > Java install path This must indicate the path to the java install. Default value is:


Requirements


<javaInstallPath>/bin/java.exe –classpath <marathonClassPath>Dmarathon.home=”<marathonHome>”

th> net.sourceforge.marathon.Main <testRootPath>/marathon_report.xml <




Marathon Launcher (marathon.jar)launcher allows interfacing with

Marathon 1.2.1.1

configuring the launcher w

Description

This must indicate where are located all theThis is a root path. Each test in that will be appended to This path MUST not inc

Default value is:

This must indicate the install path of Marathon.

Default value is:

This must indicate the classpath used by the tests.

Default value is:C:/marathon-1.2.1.1/marathon.jar;C:/marathon-1.2.1.1/Support/vldocking_2.1.1.jar;C:/marathon-1.2.1.1/Support/rmiC:/marathon-1.2.1.1/Support/formsC:/marathon-1.2.1.1/SuppC:/marathon-1.2.1.1/Support/junit3.8.2/junit.jar;C:/marathon-1.2.1.1/Support/jythonC:/marathon-1.2.1.1/Support/looksC:/marathon-1.2.1.1/Support/jeditC:/marathon-1.2.1.1/SC:/marathon-1.2.1.1/Support/vldocking_2.1.5C.jar


Default value is:



classpath <marathonClassPath>Dmarathon.home=”<marathonHome>” -Dpython.home=”<marathonHome>”

th> net.sourceforge.marathon.Main <testRootPath>/marathon_report.xml <testRootPath




Marathon Launcher (marathon.jar)launcher allows interfacing with Marathon


This must indicate where are located all theThis is a root path. Each test in that will be appended to this path.This path MUST not include an ending slash

Default value is: C:/marathon


Default value is: C:/marathon

This must indicate the classpath used by

Default value is: 1.2.1.1/marathon.jar;1.2.1.1/Support/vldocking_2.1.1.jar;1.2.1.1/Support/rmi1.2.1.1/Support/forms1.2.1.1/Supp1.2.1.1/Support/junit3.8.2/junit.jar;1.2.1.1/Support/jython1.2.1.1/Support/looks1.2.1.1/Support/jedit1.2.1.1/Support/jline1.2.1.1/Support/vldocking_2.1.5C.jar


Default value is: C:/Program Files/Java/jdk1.6.0_06

ampaign session from


classpath <marathonClassPath>Dpython.home=”<marathonHome>”

th> net.sourceforge.marathon.Main -batch -xml RootPath>

<testRootPath>

The test will be marked as passed or failed depending on the xml log file generated by The xml file is parsed by the launcher. The logs and the execution trace of the command are also

Tutorial: Creating and executing Marathon

Marathon Launcher (marathon.jar)Marathon tests.

ith some default values:

This must indicate where are located all theThis is a root path. Each test in XStudio

his path. lude an ending slash

marathon-1.2.1.1/examples


marathon-1.2.1.1

This must indicate the classpath used by

1.2.1.1/marathon.jar; 1.2.1.1/Support/vldocking_2.1.1.jar;1.2.1.1/Support/rmi-lite.jar;1.2.1.1/Support/forms-1.0.7/forms1.2.1.1/Support/jaccess-1.3/jaccess.jar;1.2.1.1/Support/junit3.8.2/junit.jar;1.2.1.1/Support/jython-2.2/jython.jar;1.2.1.1/Support/looks-2.0.4/looks1.2.1.1/Support/jedit-textArea.jar;

upport/jline-0.9.93.jar;1.2.1.1/Support/vldocking_2.1.5C.jar



ampaign session from XStudio

classpath <marathonClassPath> -Dpython.home=”<marathonHome>”

xml


Marathon tests

Marathon Launcher (marathon.jar)

ith some default values:

This must indicate where are located all the MarathonXStudio has a canonical path

lude an ending slash.

1.2.1.1/examples


This must indicate the classpath used by Marathon to execute

1.2.1.1/Support/vldocking_2.1.1.jar; lite.jar;

1.0.7/forms-1.0.7.jar;1.3/jaccess.jar;

1.2.1.1/Support/junit3.8.2/junit.jar; 2.2/jython.jar;

2.0.4/looks-2.0.4.jar;textArea.jar; 0.9.93.jar;

1.2.1.1/Support/vldocking_2.1.5C.jar



XStudio.

Dpython.home=”<marathonHome>” -classpath


Marathon tests. has a canonical path

Marathon to execute

1.0.7.jar; 1.3/jaccess.jar;

2.2/jython.jar; 2.0.4.jar;


The test will be marked as passed or failed depending on the xml log file generated by Marathon. The xml file is parsed by the launcher. The logs and the execution trace of the command are also

6.1.17 ExecutableThe Executable


The exe.xml Parameter


General > Synchronous executable

General > seconds)



1) Each test in equal to the name of the test. 2) The .exeallows executing d The test is executed by the launcher using this syntax:<testRootPath>/<testPath>/<testName>.exe /debug /testcaseIndex=<testcaseIndex> 3) In asynchronoustest_completed.A timeout is predefined for this. If thethe timeout value then the launche 4) In synchronousreturned code equals to failure. 5) In asynchronousMUST describe all the actions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be XStudio database. strings “[Success]the testcase

ExecutableExecutable launche

Configuration

xml file allows pre


Synchronous executable

Asynchronous timeout (in


Requirements

1) Each test in XStudio equal to the name of the test.

exe file must be able to parse allows executing different routines depending on the

The test is executed by the launcher using this syntax:<testRootPath>/<testPath>/<testName>.exe /debug /testcaseIndex=<testcaseIndex>

asynchronous mode, when the test_completed.txt file. This mechanism allows the launcher to know when the test is completed. A timeout is predefined for this. If thethe timeout value then the launche

synchronous mode, the returned code equals to

asynchronous mode, MUST describe all the actions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be

database. The [Success]", "[Failure]

testcase will be flagged

Executable Launcher (launcher allows interfacing with any executable.

Configuration



Synchronous executable

Asynchronous timeout (in


Requirements

must have his dedicated equal to the name of the test.

be able to parse ifferent routines depending on the


mode, when the file. This mechanism allows the launcher to know when the test is completed.

A timeout is predefined for this. If thethe timeout value then the launcher considers the test has crashed and skip

mode, the returned code is used to determine if the test passed or failed:returned code equals to 0 will be understood as a success, any other value will be interpreted as a

mode, the executable must generate a MUST describe all the actions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be

The log.txt MUST respect a specific format: Each[Failure]" or "[Log]

will be flagged as passed or failed.

Launcher (exer allows interfacing with any executable.


Description

This must indicate where are located all theThis is a rootpath that will be appended to This path MUST not include an ending slash Default value is:

This must indicate where is installed AutoIt on the host Default value is:

Asynchronous timeout (in This must indicates the maximum time the system will wait for the test to complete. Default value is:



be able to parse the argument ifferent routines depending on the


mode, when the .exe has executed all its action, file. This mechanism allows the launcher to know when the test is completed.

A timeout is predefined for this. If the executable did not create the r considers the test has crashed and skip

returned code is used to determine if the test passed or failed:will be understood as a success, any other value will be interpreted as a

he executable must generate a MUST describe all the actions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be

MUST respect a specific format: Each[Log]" or the line will not be treated. Based

as passed or failed.

exe.jar) r allows interfacing with any executable.


Description



This must indicate where is installed AutoIt on the host

Default value is: true




must have his dedicated .exe file. The name of the executable MUST be

the argument testcaseIndexifferent routines depending on the testcase index.

The test is executed by the launcher using this syntax: <testRootPath>/<testPath>/<testName>.exe /debug /testcaseIndex=<testcaseIndex>

has executed all its action, file. This mechanism allows the launcher to know when the test is completed.

executable did not create the r considers the test has crashed and skip


he executable must generate a log.MUST describe all the actions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be

MUST respect a specific format: Each" or the line will not be treated. Based

r allows interfacing with any executable.


This must indicate where are located all thepath. Each test in XStudio

path that will be appended to this path.This path MUST not include an ending slash

C:/my_executables




file. The name of the executable MUST be

testcaseIndex passed during execution. index.

<testRootPath>/<testPath>/<testName>.exe /debug /testcaseIndex=<testcaseIndex>

has executed all its action, it MUST create an empty file. This mechanism allows the launcher to know when the test is completed.

executable did not create the test_completed.r considers the test has crashed and skips


log.txt during its execution. This file MUST describe all the actions performed by the test as well as the result of each action. This file will be parsed by the launcher and all the information will be passed/stored automatically in

MUST respect a specific format: Each line MUST include the " or the line will not be treated. Based


This must indicate where are located all the .exeXStudio has a canonical


executables


This must indicates the maximum time the system will

XStudio.


passed during execution.

<testRootPath>/<testPath>/<testName>.exe /debug /testcaseIndex=<testcaseIndex>

it MUST create an empty file. This mechanism allows the launcher to know when the test is completed.

test_completed.txt s it.


during its execution. This file MUST describe all the actions performed by the test as well as the result of each action. This file

passed/stored automatically in line MUST include the

" or the line will not be treated. Based on this information,

.exe files. has a canonical


This must indicates the maximum time the system will


passed during execution. This

it MUST create an empty file. This mechanism allows the launcher to know when the test is completed.

txt file within

returned code is used to determine if the test passed or failed: a will be understood as a success, any other value will be interpreted as a

during its execution. This file MUST describe all the actions performed by the test as well as the result of each action. This file

passed/stored automatically in the line MUST include the

information,

6.1.18 Simulation The random launcher is for demo purposes only. It basically simulates timeand generates random results.

6.1.19 Simulation The success launcher iand generates only success results.

6.2 Custom LaunchersLet’s take a basic example: you have two different types of tests:

• native executablesthe console, exit code gives the result of the test),

• java class filesthe TestClass class. You usually run them by calling the java interpreter on .bat or .sh scripts).

With a very minimum effort, you can make all these tests (maybe several thousands of tests) manageable by XStudio. To do this, you just have to develop 2 lau

TestsDatabase

XStudio

Simulation The random launcher is for demo purposes only. It basically simulates timeand generates random results.

Simulation The success launcher is for demo purposes only. It basically simulates timeand generates only success results.

Custom LaunchersLet’s take a basic example: you have two different types of tests:

native executablesthe console, exit code gives the result of the test),

java class files the TestClass class. You usually run them by calling the java interpreter on .bat or .sh scripts).


TestsDatabase

XStudio

run(testId

testPath

testName

testcaseIndex

Simulation Random Launcher (random.jar)The random launcher is for demo purposes only. It basically simulates timeand generates random results.

Simulation Success Launcher (success.jar)s for demo purposes only. It basically simulates time

and generates only success results.

Custom LaunchersLet’s take a basic example: you have two different types of tests:

native executables (you currently just have to run the executthe console, exit code gives the result of the test),

(these are java class file with a main entry point; all classes inherit from the TestClass class. You usually run them by calling the java interpreter on .bat or .sh scripts).


Lau

nch

er In

terfa

ce

testId,

testPath,

testName,

testcaseIndex)

Figure

Random Launcher (random.jar)The random launcher is for demo purposes only. It basically simulates time

Success Launcher (success.jar)s for demo purposes only. It basically simulates time

Custom Launchers Let’s take a basic example: you have two different types of tests:

(you currently just have to run the executthe console, exit code gives the result of the test),

(these are java class file with a main entry point; all classes inherit from the TestClass class. You usually run them by calling the java interpreter on


Custom

Executable

Launcher

Class

Launcher

Lau

nch

er In

terfa

ce

public CReturnStatus

String[] command = new String[] {

Runtime

run.exec

int exitValue

int result

return new

}

public CReturnStatus

Class class

Object instance =

int javaResult

int result

return new

}

Figure 12 – Custom



Let’s take a basic example: you have two different types of tests:

(you currently just have to run the executthe console, exit code gives the result of the test),



Custom

xecutable

Launcher

Class

Launcher

CReturnStatus run

String[] command = new String[] {

Runtime run = Runtime.getRuntime

run.exec(command);

exitValue = p.waitFor

result = ((exitValue

return new CReturnStatus

CReturnStatus run(

class = Class.forName

Object instance = class.newInstance

javaResult = ((TestClass

result = ((javaResult

return new CReturnStatus

Custom Launchers



Let’s take a basic example: you have two different types of tests:

(you currently just have to run the executables, logs are printed out on


With a very minimum effort, you can make all these tests (maybe several thousands of tests) manageable by XStudio. To do this, you just have to develop 2 launchers (10 lines of code each).

run(int testId,

String testPath

String testName

int testcaseIndex

String[] command = new String[] {testPath

Runtime.getRuntime();

p.waitFor();

exitValue == 0) ? RESULT_SUCCESS: RESULT_FAILURE);

CReturnStatus(result, null

(int testId,

String testPath

String testName

int testcaseIndex

Class.forName(testPath

class.newInstance();

TestClass)instance).main();

javaResult == 0) ? RESULT_SUCCESS: RESULT_FAILURE);

CReturnStatus(result, null

Launchers

Random Launcher (random.jar) The random launcher is for demo purposes only. It basically simulates time-consuming operation

Success Launcher (success.jar) s for demo purposes only. It basically simulates time-consuming operation

ables, logs are printed out on

(these are java class file with a main entry point; all classes inherit from the TestClass class. You usually run them by calling the java interpreter on each test using

With a very minimum effort, you can make all these tests (maybe several thousands of tests) nchers (10 lines of code each).

Test 1

Test 2

Test 3

Test 4

Test 1

Test 2

Test 3

Test 4

,

testPath,

testName,

testcaseIndex) {

testPath + testName

();

== 0) ? RESULT_SUCCESS: RESULT_FAILURE);

null);

testPath,

testName,

testcaseIndex) {

testPath + testName);

();

)instance).main();


null);

consuming operation

consuming operation

ables, logs are printed out on

(these are java class file with a main entry point; all classes inherit from each test using

With a very minimum effort, you can make all these tests (maybe several thousands of tests) nchers (10 lines of code each).

executables

java classfiles

testName};


);


executables

class



These launchers will have the responsibility to:

• translate the abstract and execute it),

• return result Of course, the launcher interfaceprincipal one. I’m currently working on the Developer’s Guide that will explain in detail how to develop you own launcher.


translate the abstract and execute it),

return results to

e, the launcher interfaceprincipal one.

I’m currently working on the Developer’s Guide that will explain in detail how to develop you own


translate the abstract execution

XStudio.

e, the launcher interface/API



execution orders from

/API is wider than just a


orders from XStudio to real operations (instantiate the test

than just a run()


to real operations (instantiate the test

method but the



method but the run() method is the



method is the


7. Memory ProfilingThe application is rrobustness of the application. Latest measurements showed the following results:

7.1 Browsing treesThese measurements were taken while stress testing hundreds of times:

XStudio

7.2 Running manual tests on XAgentThese measurements were taken while running several times some manual test campaign in a specific agent. Memory

Memory ProfilingThe application is regularly profiled to check any possible memory leak. This is to maintain a good robustness of the application. Latest measurements showed the following results:

Browsing treesThese measurements were taken while stress testing hundreds of times:

XStudio needs between

Running manual tests on XAgentThese measurements were taken while running several times some manual test campaign in a specific agent. Memory profiling was done on

XAgent

Memory Profilingegularly profiled to check any possible memory leak. This is to maintain a good

robustness of the application. Latest measurements showed the following results:

Browsing trees These measurements were taken while stress testing

needs between 20

Running manual tests on XAgentThese measurements were taken while running several times some manual test campaign in a

profiling was done on

Agent needs between

Memory Profiling egularly profiled to check any possible memory leak. This is to maintain a good

robustness of the application. Latest measurements showed the following results:

These measurements were taken while stress testing

and 150 Mbytes


profiling was done on XAgent

needs between 5 and

egularly profiled to check any possible memory leak. This is to maintain a good robustness of the application. Latest measurements showed the following results:

These measurements were taken while stress testing XStudio

Mbytes to run smoothly (less than Firefox


XAgent.

and 10 Mbytes to run smoothly.


XStudio by selecting any item

to run smoothly (less than Firefox

Running manual tests on XAgent These measurements were taken while running several times some manual test campaign in a

to run smoothly.


by selecting any item in any tree

to run smoothly (less than Firefox!).

These measurements were taken while running several times some manual test campaign in a

to run smoothly.

egularly profiled to check any possible memory leak. This is to maintain a good

in any tree

!).

These measurements were taken while running several times some manual test campaign in a

FiguresFigure 1 - User TreeFigure 2 - CalendFigure 3 - Calendar HalfFigure 4 - SUT TreeFigure 5 - Agent TreeFigure 6 - Requirement TreeFigure 7 - Specification TreeFigure 8 - Project TreeFigure 9 - Test TreeFigure 10 - Figure 11 - Figure 12 –

TableTable 1 - EntitiesTable 2 - Tree ButtonsTable 3 - Overlay IconsTable 4 - Requirements StatusTable 5 - Specification StatusTable 6 - Sprint StatusTable 7 - Defect StatusTable 8 - Unique Identifier TemplatesTable 9 – XStudio’s Default Launchers

Acronyms

Acronym

SUT

A more complete glossary is available online at

Figures User Tree ................................Calendar Monthly ViewCalendar Half-SUT Tree ................................Agent Tree ................................Requirement TreeSpecification TreeProject Tree ................................Test Tree ................................ Campaign Tree Defect Tree ................................ Custom Launchers

Tables Entities ................................Tree Buttons................................Overlay Icons ................................Requirements StatusSpecification StatusSprint Status................................Defect Status ................................Unique Identifier TemplatesXStudio’s Default Launchers

Acronyms

Meaning

System Under Test


................................ar Monthly View ................................

-Yearly View ................................................................

................................Requirement Tree ................................Specification Tree ................................

................................................................

Campaign Tree ................................................................

Custom Launchers ................................

................................................................

................................Requirements Status ................................Specification Status ................................

................................................................

Unique Identifier Templates XStudio’s Default Launchers

Meaning

System Under Test


................................................................................................

................................................................................................

................................................................................................................................................................................................

................................................................................................................................

................................................................................................................................

................................

................................................................................................................................

................................................................................................

................................................................................................................................................................................................

................................XStudio’s Default Launchers ................................

System Under Test

A more complete glossary is available online at http://www.xqual.com

................................................................................................................................

................................................................................................................................

................................................................................................................................

................................................................................................

................................................................

................................................................

................................................................................................

................................................................................................

................................................................................................

................................................................................................................................

http://www.xqual.com

................................................................................................

................................................................

................................................................................................................................................................

................................................................................................

................................................................................................................................

................................................................

................................................................................................

................................................................................................................................

................................................................................................................................................................................................

................................................................

http://www.xqual.com

.........................................................................................

....................................................................................................................

.....................................................................................................................

..........................................................................................................

..............................................................................................

................................

....................................................................................................................

....................................................................................

.......................................................................................................................................

......................................................................................................................

......................... 9

.................................. 12

............................. 13

....................... 14

..................... 16

.......................................... 18

.......................................... 21

................... 23

....................... 29

............ 32

.................. 39

.................................... 107

.............................. 7

...................... 7

.................... 8

....................................... 20

......................................... 22

.................... 25

................... 40

............................ 63

.......................... 77

user's manual

Documents

sut tree

user tree

requirement tree

agent tree

sut inheriting requirements

necessary hosts

new absence

xqual cidex