© Telcordia Technologies 2004 – All Rights Reserved AETG Web Service Advanced Features AETG is a...

© Telcordia Technologies 2004 – All Rights Reserved

AETG Web Service Advanced Features

AETG is a service mark of Telcordia Technologies.Telcordia Technologies - Licensed MaterialAccess to this tutorial is provided solely to the registered users who have agreed to access and use the AETG Web Service according to the terms of the “Click-on license agreement” accepted during the registration process.

Page – 2


Recap of Example Scenario from Intro tutorial

Call Processing– Consider testing telephone-switch software that

processes calls – A call has the following characteristics:

Call Type: one of Local, Long Distance, International Billing: one of Caller, Collect, 800 Access: one of Loop, ISDN, PBX Result: one of Success, Busy, Blocked

– This scenario uses 4 input parameters, each with 3 possible values

Just using valid values in this example All combinations are valid.

Page – 3


Extensions to the Example Scenario

Call Processing– A call has the following characteristics:

Call Type: one of Local, Long Distance, International Billing: one of Caller, Collect, 800, 888 Access: one of Loop, ISDN, PBX, Internet Result: one of Success, Busy, Blocked Start Time: one of 8:00, 9:00, 15:00 Stop Time: one of 8:10, 9:01, 16:45

Times must be paired as shown

Page – 4


Constraints in the Example

Rules that state which values can or cannot occur together

– If the call is an international call, the billing can’t be for an 800 or an 888 number

– If the call is from the internet, the call type can’t be international

Page – 5


Steps in this tutorial

In this advanced tutorial you will– Extend an existing Test Specification

Specify additional fields Specify relations (field interactions) Specify valid and invalid values Specify constraints Specify a compound Specify field order

– View the test specification (plain-text version)– Validate the test specification– Set generator properties– Generate test sets– View, download, and print test sets

Page – 6


Click on “Log In”underRegisteredUsers

Access to user documentation requires login.

Please checkthe news page occasionally.

Home Page

Page – 7


Enter your user name & password to start a new session.

Please do not bookmark this page.

Note the “lock” icon in the browser.

Login Page

Page – 8


Bookmark this page!

Welcome Page

Page – 9


Steps to extend the test specification

1. Copy the basic spec to a new name and open for edit

2. Add comments to the spec

3. Add new values to existing fields

4. Add new fields to the spec

5. Enter constraints on fields

6. Create a compound

7. Add fields and field values to the compound

8. Add the compound to the relation

9. Select compound labels for use in the relation

Page – 10


Copy a Specification

Make a copy of the spec from the basic tutorial:

1. Click on “calls” in the list of test specifications

2. Enter the name “calls_plus” in the text box

3. Click on the “Copy” link

Page – 11


Select the newly created specification, then click on the “Edit” link to open it.

Open the copied specification for edit

Page – 12


Click on the “Edit” link in the Comments area.

Add comments to the specification

Page – 13


Enter your comments in the text area, then click “Submit” to save your changes.

Edit comments in the specification

Page – 14


Click on the relation name, then on the “Edit Values” link.

Add new values to existing fields in the relation

Page – 15


Valids: enter “Internet” for the Access field, and “888” for the Billing field.

Invalids: enter some bad values.

Then click on “Submit Values” to save changes.

New values for the advanced example

Page – 16


Enter each field name, and click on the “Add” link.

Additional field names in the example:

Start_TimeStop_Time

Add new fields to the test specification

Page – 17


Fields added to the test specification

Scroll the selection box down to seeboth Start_Time and Stop_Time

Marked as unused (*) because these fields are not currently used in any compound or relation.

Page – 18


Constraints

Constraints control how values are combined Constraints are written in a constraint language Can have multiple constraints for a relation Example constraints:

– If the call is an international call, the billing can’t be for an 800 or an 888 number. In AETG spec language: if Call_Type = “International” then Billing != 800 888

– If the call is from the internet, the call type can’t be international. In AETG spec language:if Call_Type = “International” then Access != “Internet”

Page – 19


Select the relation, then click on the “Edit constraints” link.

Select relation to receive constraints

Page – 20


The constraints should read:

if Call_Type = “International” then Billing != 800 888

if Call_Type = “International” then Access != “Internet”

Quotes are required around string values.

Also see value list at bottom (scroll down).

After entering the constraints, click on the “Submit Entries” link to continue.

Enter constraints among field values

Page – 21


Compounds

A compound contains fields that have some relationship

Want only particular values of compound fields to appear with other compound field values

Generator should not attempt to cover interactions between values of the compound fields

Consider these a convenience feature that reduces the need for post-processing on generated test sets

Page – 22


Motivating the Use of Compounds (1)

Need to model Start_Time and End_Time– Start_Time must be earlier than End_Time– Want only these pairs: 8:00 & 8:10, 9:00 & 9:01,

15:00 & 16:45– Do not want pairwise coverage (e.g., 8:00 & 9:01)

First possible approach: model fields individually– Start_Time has 8:00, 9:00, 15:00; End_Time has

8:10, 9:01, 16:45– Constraints say “If Start_Time = 8:00 then End_time =

8:10” etc.

Page – 23


Motivating the Use of Compounds (2)

Second possible approach: use composite values – StartStopTime has 8:00_8:10, 9:00_9:01,

15:00_16:45– Post-process the generated output to split up the

values Best approach: use a compound

– Value sets are passed through, split automatically into tuples

– Next slides show how to enter this example in the GUI

Page – 24


Enter a compound name, then click on the “Add” link.

Create a compound in the test specification

Page – 25


Next, click on the “Select Fields” link to add fields to the compound.

Empty compound created in the test specification

Page – 26


Select the two time fields (control key plus two clicks with left-mouse button), click on the “>>Add>>” link, then click on “Submit selections” to save your work.

Select fields for the newly created compound

Page – 27


Note that the two time fields are no longer marked as unused.

Click on the “Edit values” link next.

Compound now has fields

Page – 28


Enter labels for the pairs along with the paired values in the text boxes:8:00 and 8:10, 9:00 and 9:01, 15:00 and 16:45.

Click on the “Save and add rows” link to save changes.

Enter valid values for fields in the compound

Page – 29


Enter a label and an invalid pair: 6:44 and 6:23

Invalid because the end time is before the start time.

Click on the “Submit values” link to save changes.

Enter invalid values in the compound

Page – 30


The next step is to extend the existing relation. You will add the compound first.

Click on the relation name, then on the link “Select Components”

Relation gets the new compound

Page – 31


Select the compound name, click on the “>>Add>>” link, then click on “Submit selections” to save your changes.

Select the compound and add it to the relation

Page – 32


The relation now says “4f, 1c” which means it has 4 fields and 1 compound.

Note that the compound is no longer marked as unused.

Next, click on the “Edit Values” link to pick compound labels.

Relation now has a compound

Page – 33


Scroll the window down.

Select compound labels “eight”, “nine”, and “three” for use as valid tuples.

Select tuple “invalid” for use as an invalid tuple.

Click on “Submit values” to save changes.

To pick multiple entries in a selection box, either click and drag, or use control-click.

Select compound labels for use in the relation

Page – 34


Field order

The order in which fields appear in the GUI controls the order in which they appear in test results

– Relative orderings in compounds and relations is not material

User controls field order

Page – 35


Select fields and use the links appropriately to order the list.

Click “Submit” to save changes.

Setting field order

Page – 36


View the test specification to see all the information in one place.

View the test specification

Page – 37


Fields, compounds, relations, values, constraints, etc. – it’s all here.

This version is processed by the generation tools.

Plain-text version of the test specification

Page – 38


Check the specification for various properties, like not using a field twice in a relation.

Validate the test specification

Page – 39


All is well.

Click on the “Edit spec” link to continue.

Output from validation

Page – 40


These parameters affect the generator’s performance.

It is not necessary to change them for most cases. Use large numbers if a relation has a large number of constraints, or if the output from the generator indicates trouble with covering pairs.

Generator properties

Page – 41


Click on the “Generate tests” link to start the generator.

Generate tests (finally!)

Page – 42


Scroll the window down, then click on the “View test cases” link to continue.

Output from test generator

Page – 43


Valid cases use only valid values; combinations honor all constraints.

Invalid cases use one invalid value per tuple.

Overview of generated tests (1)

Page – 44


Scroll down to see the invalid constraint cases.

These have combinations that violate a constraint.

Overview of generated tests (2)

Page – 45


Exercise

Modify the test specification to use two relations instead of a constraint

– Drop the seed and the constraints from the relation “Switch”

– Copy the “Switch” relation to create two new relations: Domestic: same fields as before, but only values

appropriate for domestic calls International: same fields again, only values appropriate for

international calls

– Generate tests and compare the result

Page – 46


End your session when you’re done.

Logout

© Telcordia Technologies 2004 – All Rights Reserved AETG Web Service Advanced Features AETG is a...

Documents

Transcript of © Telcordia Technologies 2004 – All Rights Reserved AETG Web Service Advanced Features AETG is a...