Table of Contents

1. Introduction.......................................................................................................2 2. The automation process...................................................................................3 3. QTP Functional Testing Methodology..............................................................5 4. Create In rastructure.......................................................................................1! 5. Functions "i#rary............................................................................................12 $. %uild &utomated 'cripts.................................................................................15 (. QTP ) Connection to Quality Centre..............................................................31 *. Maintenance &pproach...................................................................................33 +. ,oles - ,esponsi#ilities.................................................................................35 1!. .n/ironmental ,e0uirements.......................................................................3$ 11. 1lossary........................................................................................................3(

1.
1.1.

Introduction
Purpose
This Strategy and Coding standards document serves as a high level plan that specifies the overall approach to Quick Test Professional (QTP) Automation. It is for use y oth IT and !usiness testing and re"uires a colla orative approach y all stakeholders. This document specifies ho# to convert the manual Test Cases (as detailed in Quality Centre (QC)) to automated tests in QTP. It #ill descri e the process of accessing manual Test Cases in Quality Centre$ generating a QTP script from Quality Centre and then maintaining that QTP script from #ithin QTP. It #ill document Quick Test Professional Coding Standards that #ill apply to Quality Centre Test cases and Quick Test Professional %unctions and & 'ect (epository)s. All test cases #ill e uilt using an Automated %unction !ased Testing *ethodology and y identifying tasks re"uired to uild an automated testing solution. This document is ased on the automation of the *ail (edirection Service (*(S) and the SAP %i+ed Assets scripts.

1.2.

Objectives
The design of this document is aimed at an automated test engineer and any tester #ith a sound understanding of test automation using the QTP tool. This document #ill identify ho# to create QTP testing infrastructure such as & 'ect (epository entries$ create QTP %unctions$ make test cases data independent y calling data creation scripts and the reuse of QTP infrastructure from other pro'ects. This document #ill detail the follo#ing steps, !uilding infrastructure (unning different releases - QTP against code releases

1.3.

Intended Audience
This material is intended to e a living document and delivered to, .e# automated testing staff (as a training aid and on-the-'o first reference)/ All automated testing staff (e+perienced or other#ise as a reference0template for the setting up of an automated testing pro'ect)/ and Completed pro'ects to e updated #ith appropriate kno#ledge.

2.

The automation process

The follo#ing sections descri e in detail the process re"uired to create automated scripts to regression test e+isting pro'ects #ith maintenance releases.

2.1. Automation Wor flo!

Create In rastructure %uild &utomated 'cripts .2ecute &utomated 'cripts ,eport on .2ecution ,esults

The diagram a ove depicts the process in #hich e+isting applications re"uire automation for regression testing.

2.1.1.

Pre"re#uisites for $TP Automation Process

The follo#ing are pre-re"uisites or dependencies for QTP automation, 1no#ledge and hands-on e+perience #ith the use of QTP/ Quality Centre (QC) and QTP installed and configured/ QC and QTP are integrated/ QTP Add-Ins are installed (if re"uired)/ QC user groups are defined and granted access to Quality Centre pro'ects/ The application or product is in a sta le state/ Creation of ne# automated scripts re"uires e+isting manual test cases to have een e+ecuted successfully. This task is performed y the application tester or usiness representative and is performed prior to handover to QTP automation. The manual test cases must have een e+ecuted successfully and that there are no other changes in the application. 2+isting automated scripts can e updated directly to reflect the changes as part of maintenance releases. All test cases must start and end at the same point. This is normally the %irst screen of the application. This allo#s for test cases to e atched together into a test suite. All environment$ soft#are or data ta le changes must e advised to the automated testing team. There #ill potentially e an impact on the running of automated test cases #ith the introduction of these changes. The test cases must not e data dependant. All data re"uired in the test case must e created in the test case. In the event that data cannot e created and the test case is data dependant$ the data must e a le to e restored$ or manipulated ack to the initial state after a test case updates the data. This then allo#s for any test case to e rerun at anytime

2+isting manual test cases e+ist in QC in the standard format (see the QC user guide) and a copy of the test case to e automated are placed in the regression folder alongside any e+isting automated scripts. (efer to Section 3.4 for further information regarding *anual Test Cases.

3.

$TP %unctional Testin& 'ethodolo&(

2ach Test case is uilt using a series of Quick Test Professional %unctions. 2ach function e+ecutes Quick Test Professional code to input data onto a screen. 2ach o 'ect in the Quick Test Professional %unction resides in the & 'ect (epository$ thus allo#ing Quick Test Professional to identify all fields in the application. 2ach test case uses functions. 2ach function is either an applet on a screen or a #hole screen depending on the amount of fields. 2ach function is named A5T6Screen .ame e.g. *(S6Close6Application 2very field0o 'ect on the screen or applet must e learnt into the o 'ect repository and renamed #here re"uired to a more meaningful screen name. 2ach function li rary must reside as .v s file All functions are accessi le via the step generator.

%unction is placed into testcase via the step generator. The rc value is passed ack to Quality Centre via the (eporter. (eport2vent rc command. Quality Centre accepts 7 for a pass$ 4 for a fail and 8 as done. Al#ays try to pass 4 or 7.

The testcase function call invokes the function as displayed a ove. This is the actual v scipt that drives QTP. 2ach function uses a function template. 9efine in the function$ the varia les to uni"uely identify the screen and any fields on the screen.

The function displayed a ove selects links via a parameter link6name. The links have een learnt into the o 'ect repository. .otice the ro#ser$ page and frame name are the same as #hat has een learnt into the o 'ect repository.

3.1.

Initial Condition
Automated test scripts must egin from the same starting point. It is est practise to end all open ro#sers and start the Application under Test from the eginning. This ensures that all scripts can run ack to ack in an unattended atch mode.

3.2.

)tart *p )cript
The start up script #ill copy all functions from the :A. and load them on the C 9rive of the PC e+ecuting the test case. It #ill also uild the infrastructure li raries if they don)t e+ist.

3.3.

Test case %ailure + ,-ception condition handlin&

All Quick Test Professional functions must use an e+ception handling frame#ork. This allo#s any Quick Test Professional function to fail$ report the failure and ackout of the application. The e+ception handling frame#ork is uilt y, An 2nvironment ;aria le set in the Quick Test Professional startup6script set as 2.;I(&.*2.T(2<C2PTI&.6C&.9)=>.>. The *(S6:ogon function sets the 2.;I(&.*2.T(2<C2PTI&.6C&.9) to a value of ?.>. If any function has a failure y not finding the screen is should e on$ or any kno#n e+ception condition is triggered$ the 2<C2PTI&.6C&.9 value is set to ?@>. The application is shutdo#n and all functions in that testcase flush. The ne+t use of a *(S6:ogon function #ill reset the 2<C2PTI&.6C&.9 to ?.>. The follo#ing diagram demonstrates the e+ception handling process,

The 2+ception6Cond if e"ual to ?.> #ill run this function. &ther#ise thefunction #ill report that the testcase has flushed.

..

Create Infrastructure
Infrastructure li raries are created to store QTP functions$ utilities$ documentation and o 'ect repository files The Infrastructure li raries are created for each release of the soft#are. 5nder each release folder (eg (2:8A) the folders elo# must e+ist$ other#ise QTP #ill fail in the startup script. 2+amples of the li raries for releases are as follo#s, BBCC&P(&9DBQSABEroupBQTP6*(SB(2:8AB9ocumentation BBCC&P(&9DBQSABEroupBQTP6*(SB(2:8AB%unctions BBCC&P(&9DBQSABEroupBQTP6*(SB(2:8AB(epository BBCC&P(&9DBQSABEroupBQTP6*(SB(2:8ABTestcase BBCC&P(&9DBQSABEroupBQTP6*(SB(2:8ABT+tfiles BBCC&P(&9DBQSABEroupBQTP6*(SB(2:8AB5tilities

The follo#ing diagram displays the directory structure for the (el8A li raries. They are as follo#s

..1.

/ibrar( 0efinitions for each 1elease

The application under test must have a QTP release specific directory$ i.e. (2:44$ (2: 48 and Sandpit 2ach of the release directories hold release specific infrastructure code or release specific infrastructure o 'ects that QTP re"uires in order to run the application under test. Therefore the (2:44 functions folder #ill hold all functions that e+ecute on the (el44 application code and the (2:48 functions folder #ill hold any ne# application screen functions and modified (el44 functions.

..2.

)andpit /ibraries
Sandpit li raries are for use on the test automator)s pc to develop or modify QTP code. !y saving in these li raries$ data is not over#ritten #ith the aseline code after a restart of QTP. The sandpit li raries remain empty on the BBCC&P(&9DBQSA drive. The sandpit li rary on the C drive is #here changes can e made or ne# functions can e created. &nce tested$ they can e appended to the end of the %unction or 5tility ;!S files on the BBCC&P(&9DBQSA drive under the appropriate (elease %older. The function and utility Sandpit li raries must contain a template function. If not$ these li raries cannot e e+ecuted via an e+ecutefile command.

..3.

0ocumentation
The 9ocumentation directory holds Ford or 2+cel documents #hich reference the application.

2.

%unctions /ibrar(
The %unctions :i rary contains QTP functions. These are ased on one function per screen. This li rary is a se"uential file of all the QTP functions for that application release. As more than one soft#are release can e tested at any one time$ the QTP function li rary can e concatenated in QTP #ith as many prior function li raries as re"uired. The follo#ing sho#s a li rary concatenation of rel4A$ rel48 and rel44 Sandpit FunctionABC %unction92% (2:48 Function XYZ (2:44 %unction 48A %unction AD3 FunctionABC

The a ove sho#s that Sandpit function %unctionA!C #ould e a modified version of (2:44 %unction A!C and a ne# function function92% as the sandpit li rary #ould override the rel44 function li rary. As each application release gets tested$ only the ne# functions and functions that re"uire modification are held in the Sandpit function li rary. All %unctions that are not changed are still accessed via the concatenation of ne# and old release function li raries in the QTP Startup The QTP startup script #ill copy all availa le (elease folders to the C,9rive or 9,9rive of each test machine. At the end of each ;!S file$ an 2.;I(&.*2.T li rary varia le #ill e used to load other li raries if re"uired.

1eith to add more detail

2.1.

%unction Creation
Fhen creating a ne# function$ the follo#ing steps must e follo#ed, 4. :earn & 'ect (epository entries into the BBCC&P(&9DBQSA drive & 'ect (epository. 8. (ename & 'ect (epository entries to meaningful names.

A. Create function y copying the template function into your sandpit0function li rary D. Add the field names of the screen to the parameter list of the function. G. Add the ne# & 'ect (epository entry names into the function$ as AP6#e edit$ AP6#e list$ etc. This #ill allo# the function to communicate to the o 'ect repository and play data into each field 3. Save the function and test change H. &nce satisfied that ne# function is ok$ append it to the BBhcoprodDB"sa drive function li rary.

2.2.

Object 1epositor(
The & 'ect (epository li rary holds all the application o 'ects for the application under test. This li rary is not concatenated as only one & 'ect (epository$ #ith the same entries in it$ can e opened at any time. Fhen creating a ne# release of the & 'ect (epository$ a ?save as> must e done on the old & 'ect (epository to the ne# release li rary. Any su se"uent changes can then e done in the ne# & 'ect (epository li rary. Fhen a QTP script is e+ecuted$ a copy of the & 'ect (epository is taken and saved to C,BApplicationB(eleaseB(epository. This is done to ensure no corruption occurs on the master that is held on the BBCC&P(&9DBQSA drive. If changes are re"uired$ they must e done directly to the BBCC&P(&9DBQSA drive copy of the o 'ect repository. This is ecause #hen merging t#o o 'ect repositories$ QTP sees like defined o 'ects as the same. !y learning ne# o 'ects into the BBCC&P(&9DBQSA drive & 'ect (epository a rename on o 'ects can e done and the & 'ect (epository can e resaved onto the BBCC&P(&9DBQSA drive. 2nsure that a ackup of the o 'ect repository is done first. If the & 'ect (epository gets corrupted$ then QTP #ill not run. 2.g. *(S uses BBCC&P(&9DBQSABEroupBQTP6*(SB(2:8AB(epositoryB*(S.tsr .The & 'ect (epository is copied from the BBCC&P(&9DBQSA,BEroupBQTP6*(SB(2:8AB(epositoryB*(S.tsr folder #hen the test case starts to C,BEroupBQTP6*(SB(2:8AB(epositoryB*(S.tsr.

2.2.1.

Object 1epositor( 3amin& )tandards

Any o 'ect placed into the & 'ect (epository should e named according to the field name on a screen. As #e E5I entries #ill e captured as the html programming name$ rename this to an understanda le name such as Customer.ame or CustomerPhone.um er. This #ill then mean the E5I entry is sho#n in functions and test scripts as something understanda le. A E5I entry in the format %7A8f#fn is not accepta le. Any E5I entries that are non #e ased must also have an understanda le name.

2.3.

Testcase %older
This li rary holds reusa le actions that #e can use for data loading. i.e. creating a piece of data that #e can reuse in the test script later. Any data that is created must e saved as an 2nvironment varia le. This li rary also contains the startup script and template script.

2...

T-tfiles %older
This li rary holds files that are created at run time. This can also e used for transient data that is used et#een test scripts. This practice is not recommended as test cases should e data independant.

2.2.

*tilities %older
This li rary holds non specific functions that can e used in any test script. %unctions may include reading and #riting from files$ utton press$ edit sets$ list selects etc.

4.
4.1.

5uild Automated )cripts

'anual Test Cases
2ach Test Case must e #ritten into Quality Centre. %rom Quality Centre$ login to your pro'ect and select the test case. The 9etails ta of Quality Centre descri es the tests Purpose$ Test Conditions$ Pre re"uisites$ 9ependencies$ 2nvironments and post-test Cleanups. ;ie# your manual steps y clicking on the ta $ Design Steps. 2nsure that manual Test Cases have een #ritten and e+ecuted #ithout error and are therefore verified as correct before automating. !efore any test case is automated it must pass the follo#ing criteria,

2ach script has een #ritten so that each application screen in the test case flo# is a ne# test step and each verification point is a ne# step. Test cases are stand alone$ non data dependant$ logon to the application under test at the start and logoff or shutdo#n the application at the end of each test case. All data re"uirements are defined in the details ta of Quality Centre.

Appendi+ A of this document contains e+amples of a #ell #ritten and a poorly #ritten test case.

4.2.

6enerate $TP )cript

@ou can no# convert this manual Test Case in to a Quick Test Professional script. To do this$ click on the Generate Script utton and select the QUICKTEST_TEST option.

Quality Centre has no# generated Quick Test Professional code and has attached it to this manual Test Case. This can e vie#ed y clicking on the ta Test Script. This generated code is nothing more than a series of comments and reporter events. The Quality Centre manual Test Case has een copied in to Quick Test Professional and each step has een placed in as comments.

4.3.

6enerated $TP )cript

After generating a Quick Test Professional script from Quality Centre all the Step details are placed into comments in the Quick Test Professional script

4...

Test )ettin&s and Options

2ach ne# script re"uires test settings$ record and run settings$ associate repositories and options to e set.

4...1.

Test )ettin&s
Click on %ile and select Settings. Click on (un ta . 2nsure that I(un on all ro#s) is selected. At field, Fhen error occurs during run session, select Iproceed to ne+t step). 2nsure that the t#o tick o+es are also ticked.

Click on (esources ta . Click on IJ) to add resource li rary and utilities. 2nsure that functions are associated to local C,B or 9,B and that sandpit li raries are listed first.

4...2.

1ecord and 1un )ettin&s

Select Automation$ then (ecord and (un Settings. Fhen using a Findo#s ased application$ set as per e+ample elo#,

Fhen using SAP application$ set as per e+ample elo#,

Fhen using a Fe application$ set as per elo#,

4...3.

Associate 1epositories
In QTP$ click on (esources and then select Associate (epositories. Click on IJ) to create repository association. Click on IK) to associate IAction4).

4.....

Options
Click on Tools$ select &ptions. Click on (un ta . 2nsure (un *ode is set to I.ormal). As displayed in diagram a ove$ ensure the follo#ing are ticked, ;ie# results #hen run session ends Allo# other *ercury products to run tests and components Save still image captures to results. Select I%or errors) from drop list

4.2.

)tep 6enerator
All Quick Test Professional functions are #ritten and stored in :i raries and are added to the Step Eenerator (%H) in Quick Test Professional. To access these functions$ click on Insert$ then Select Step Eenerator or press %H from #ithin QTP. The functions have een sorted alpha etically to make it easier to find the function that matches your Application screen. &nce you have found the function that #ill perform the functionality matching the Application screen$ you can fill in the value column #ith appropriate arguments that #ill e set to the function.

2very parameter must have an argument value specified. The return value o+ needs to e ticked each time a ne# function call is set. Insert another step to e ticked as re"uired. Fhen creating a function you must enter data into every field of the function to verify it can run the function correctly.

The return value (rc = return code) stores #hether the function has passed or failed. The rc is then passed to the report and decides #hether the particular step has passed or failed.

4.4.

,ditin& $TP )cripts

.o# edit and uild the Automated Test Script via Quick Test Professional. To make the script #orka le$ #e egin adding in to the Test Script the functions or Test conditions that #ill perform the automated tests$ thus uilding up a test scenario. The idea here is to match the manual Test Case steps to the appropriate Quick Test Professional %unction. 2ach test case should have one or more Quick Test Professional functions per step. This function #ill relate to each screen of the tested application$ as per the Automated %unctional Testing *ethodology. The Automated %unctional Testing *ethodology gives the advantage of modular programming/ it ena les an easy and fast #ay to create reusa le test cases. &ther advantages of this methodology are$ ease of maintenance of scripts and a ility to run scripts in any environment due to no data dependencies. 2nsure that you add the follo#ing te+t at the top of the Quick Test Professional script to identify #ho has #ritten the script and #hen,

E.g. # Revision

istor!"

$nitia% &ersion

'()(*)(+

,RS version -.-.*>

@ou are no# ready to edit0create the Automated Test Script. To do this$ start up Quick Test Professional and access the test script that #as created in Quality Centre via the .pen command. There are t#o areas #here Test Scripts can reside. They can reside #ithin Quality Centre or in the %ile System (PC or .et#ork folders). If #e have created the Test Script via Quality Centre then the script #ill reside #ith in Quality Centre. Lust follo# the same path you used #hen accessing the *anual Test Script$ to find the Automated Test Script.

Select Test Script from QC.

4.7.

$TP Add"Ins
Fhen Quick Test Professional scripts are created from Quality Centre$ Quality Centre sets the script default addin setting to lank. &nce you have started up the Quick Test Professional script you have to add all the A//0 ins for the application under test. To do this$ go to Fi%e ) 1est 2roperties3 and click on the A//0ins ta . %rom here you can select all the add-ins that #ill e needed y clicking on appropriate items then pressing Enter. $f t4is is not /one$ Quick Test Professional #ill e forced to shutdo#n and the script #ill not run at all$ due to Fe test commands eing e+ecuted in the functions #hile the Fe Test addins have not een started #hen Quick Test Professional is invoked.

Select add-ins here y clicking on appropriate item. Alternatively$ any add-ins can e selected during opening QTP application.

4.8.

$TP Template )cript

2ach test case #ill use a template script at the start. This script #ill copy all functions from the :A. and load them on the C 9rive of the PC e+ecuting the test case. It #ill also uild the infrastructure li raries if they don)t e+ist. It #ill then e+ecute a function.v s file so at run time these functions #ill override the function li rary associated at uild time. The template script #ill e administered y QSA. The location of the template is, BBhcoprodDBEroupB QTP6*(SB(2:8ABTestcaseBActionTemplate.mst The PC that #ill e running the automated scripts #ill reference the a ovementioned Action template. A copy of this template is placed in C,BProgram %ilesB*ercury InteractiveBQuickTest ProfessionalBdat

4.9.

Completed Testcase
2ach test case should have one or more QTP functions per step. The function should pass a return code ack to the test case$ therefore allo#ing QTP to pass Quality Centre the step status. At the start of each test case$ pre re"uired data can e added. *ost pre re"uired data for *(S can e created using a test case that uses varia les$ e.g. first name and surname. A glo al varia le is created #hich can e addressed any#here else in the test case. Any pre re"uired data scripts e+ist in QTP6*(S0(el8A0Testcases. These testcases are reusa le actions. The line (unAction denotes a called action. The tester should ensure they have a good understanding of #hat is availa le. If ne# data scripts are re"uired$ it is est to model them off e+isting scripts. A test case #ill appear as per the follo#ing e+ample,

7.
7.1.

$TP : Connection to $ualit( Centre

Connection
)erver Connection %rom Quick Test Professional$ select Tools/ Quality Centre Connection and on the Quality Centre Connection page enter the follo#ing, Server ur%" http,00postapps0"c in ,.&. Project Connection Domain" P(&L2CTQC 2ro5ect" *(S 6ser 7ame" QC6*(S 2ass8or/" Mpass#ordK Other (econnect at startup, check this o+. Save pass#ord for reconnection on startup, check this o+. Click on utton Connect Click on utton Connect

8.

'aintenance Approach
To ensure that release changes of soft#are can e accommodated y QTP$ some tasks must e completed efore running any tests.

8.1.

1e&ression Test Chan&es

Fhen a ne# release of soft#are causes old functions to perform incorrectly$ changes need to e done to these functions and o 'ect repositories to allo# for testing to continue. These changes may e due to a ne# screen$ a screen change or an o 'ect eing seen differently in QTP$ e.g. a change in a utton name.

8.2.

3e! Infrastructure
Fhen uilding a ne# release of QTP Infrastructure$ the first thing to do is uild the infrastructure li raries as documented previously. This #ill give you the a ility to make release dependant changes to old functions$ scripts and & 'ect (epositories in the ne# li raries. Copy the QC folder #ithin the pro'ect to a ne# version. This #ill allo# for test cases changes in the ne# version of the QC folder and also keep the old QC folder as is. This #ill allo# for easier reporting of the testing effort in the ne# release.

8.2.1.

5uildin& a ne! $TP ,nvironment

As each ne# release of soft#are is placed into an application testing environment$ the QTP environment #ill need to e updated to allo# for ne# functions$ and the a ility to run regression tests against the old soft#are. The follo#ing tasks need to e performed to uild the environment, The release specific infrastructure li raries must e created for the ne# release$ as documented earlier in Section D. The & 'ect (epository for the current release must e ?saved as> into the ne# release (epository folder The %unction :i rary re"uires 'ust a comment in it$ so it does not appear as an empty file. The C,BT2*PBQTP6Start65p.v s file must e modified #ith the correct version of the application you #ish to test #ith. 9epending on the (elease or Pro'ect$ this is to e updated accordingly.

&nce this is completed$ restart QTP and ensure you are a le to run a script through to completion. Any function changes can then e done y copying the function from the previous release)s function li rary and placing it into the ne# function li rary. %rom this ne# function li rary$ you are then a le to make the appropriate changes.

The follo#ing steps outline the uild for ne# environment, 4. &pen Findo#s e+plorer. 8. &n net#ork BBhcoprodDB"sa$ open QTP6*(S folder A. Create ne# folder e.g. (2:A4 and then create folders as per previous release, 9ocumentation (to e empty) %unctions (to contain lank function.v s file) (epository (to contain empty repository file) Testcase (Copy Startup and QTP Startup from previous release) T+tfiles (to e empty) 5tilities (to contain lank utilities.v s)

D. Cighlight the Testcase folder. - &pen up QTP Startup.v s. 5pdate release num er in path - &pen up Startup.v s. 5pdate 9im (elease J4 (8) and Add (elease (8) - Add (evision comments. 5pdates to e made in ne# function.v s.

9.

1oles ; 1esponsibilities
1oles 1esponsibilities

&utomation 'pecialist

&utomation Test &nalyst ,egression Tester

Create Functions and esta#lish li#raries or ne3 or e2isting pro4ects Create automated tests "iaise 3ith ,egression Tester Pro/ide training and assistance to &utomation Test &nalysts. Create Functions and esta#lish li#raries or ne3 or e2isting pro4ects Create automated tests "iaise 3ith ,egression Tester Create automated tests "iaise 3ith &utomation 'pecialist and Test &nalyst ,aise de ects in Quality Centre

1<.

,nvironmental 1e#uirements
Administrative access to PC is re"uired to run QTP automated tests #ithout errors. Alternatively$ (emote 9esktop Connection can e used to access virtual PC)s. Click on Start$ then click on (un. Type Imstsc). Click &1. Type PC .o. e.g. hcodev'GH8$ click Connect. A ;irtual Server is re"uired if virtual PC is to e accessed. Steps for virtual pc set up are as follo#s, 5ser must e logged in #ith same Administrative account on oth Controller (Server) and ;irtual pc)s. *ap to "sa - hcoprodD ;irtual must e ma+imised to operate. This can e done for more than one at the same time.

In addition$ to the a ovementioned$ the Automation Specialist$ Automation Test Analysts and (egression Tester should all have the minimum specifications as re"uired for Quality Centre and Quick Test professionall

How many Controllers? Servers? Will there be multiple virtuals on Servers?

1<.1.

Test )ite
Test ed location is at 8404G7 :onsdale St and also on (egression Testers PC)s located at their #orkstation.

1<.2.

1ecordin& of Test 1esults

Test records #ill e recorded #ithin Quality Centre. Completed copies of Test Cases #ill e filed for Audit purposes. 9iscrepancies et#een e+pected and actual results during the e+ecution of Test Cases #ill e recorded on the Test Cases. The tester involved #ill raise a 9efect for the discrepancy.

11.

6lossar(
To find the meaning of #ords that are not included in this glossary$ try the PostIT Elossary. Click here to access the PostIT glossary

1erm
Q'& QC QTP &9T

Description
Quality 'o t3are &ssurance. This team is part o Integration and 5e/elopment 'er/ices and is responsi#le or specialist testing competencies and testing go/ernance. Quality Centre. This is a 6P so t3are pac7age used to store test re0uirements8 test cases8 de ects and test e2ecution results. Quic7 Test Pro essional. This is a 6P so t3are product used to automate manual tests. &pplication 9nder Test

1est Case E9amp%es E9amp%e of goo/ test case : Create and Approve Standard Purchase &rder
Purpose, Create a Standard Purchase &rder for A stock items. %or each item of the stock$ the re"uester is different. 9ata (e"uired, - Supplier 9etails - A stock item num ers - (e"uester name and #here to deliver to Prere"uisites, .one )teps= Step 7ame Step 4 Description :og into the %*IS Application. 2nter your user name in the N5sernameN field. 2nter your pass#ord in the NPass#ordN field. Click on the N:oginN utton. Select the NMagencyK Purchasing Super 5serN menu item. Then select NPurchase &rders - Purchase &rdersN menu item.
.nter :'tandard Purchase ;rder: in the :Type: ield. .nter the supplier name in the <'upplier: ield. .nter the site name in the :'ite: ield. .nter the ship to name in the :'hip=To: ield. .nter the #ill to name in the :%ill=To: ield. .nter a description or the purchase order in the :5escription: ield. In the "ine ta#8 enter :1: in the >um column o the irst ro3. .nter :1oods: in the :Type: ield. .nter the item num#er ?e.g. 1!43*@ in the :Item: ield. .nter 0uantity ?e.g. 5@ in the :Quantity: ield. .nter the price o the item ?e.g. 15@ in the :Price: ield. .nter a uture date in the :Promised: ield.

E9pecte/ Resu%t The Come page appears.

Step 8

The Purchase &rders #indo# appears.

'tep 3

&ll the details entered a#o/e appear.

'tep 4

&ll the details appear in the irst ro3 o the ta#le.

Step 7ame
'tep 5

Description
In the "ine ta#8 enter :2: in the >um column o the second ro3. .nter :1oods: in the :Type: ield. .nter the item num#er ?e.g. 1!54*@ in the :Item: ield. .nter 0uantity ?e.g. 5@ in the :Quantity: ield. .nter the price o the item ?e.g. 1$@ in the :Price: ield. .nter a uture date in the :Promised: ield. In the "ine ta#8 enter :3: in the >um column o the third ro3. .nter :1oods: in the :Type: ield. .nter the item num#er ?e.g. 1!5$2@ in the :Item: ield. .nter 0uantity ?e.g. 5@ in the :Quantity: ield. .nter the price o the item ?e.g. 1(.5!@ in the :Price: ield. .nter a uture date in the :Promised: ield. Place your cursor in the item ield o line 1 and then clic7 on the :'hipments: #utton. Clic7 on the :5istri#utions: #utton. .nter the re0uester name in the :,e0uester: ield. .nter the deli/er to name in the :5eli/er=To: ield. .nter the su# in/entory name in the :'u#in/entory: ield. 'a/e your 3or7 #y clic7ing on the :'a/e: #utton on the tool#ar. Close the 5istri#ution 3indo3. Close the 'hipments 3indo3.

E9pecte/ Resu%t
&ll the details appear in the second ro3 o the ta#le.

'tep $

&ll the details appear in the third ro3 o the ta#le.

'tep (

The 'hipments 3indo3 appears displaying the details o the item. The 5istri#utions orm appears. Aour 3or7 is sa/ed. & note appears ad/ising you that your 3or7 is sa/ed.

'tep * 'tep +

'tep 1! 'tep 11

The 'hipments 3indo3 appears. The Purchase ;rders 3indo3 appears displaying your purchase order. The 'hipments 3indo3 appears. The 5istri#utions 3indo3 appears Aour 3or7 is sa/ed. & note appears ad/ising you that your 3or7 is sa/ed.

'tep 12 'tep 13 'tep 14

Place your cursor in the item ield o line 2 and then clic7 on the :'hipments: #utton. Clic7 on the :5istri#utions: #utton. .nter the re0uester name in the :,e0uester: ield. .nter the deli/er to name in the :5eli/er=To: ield. .nter the su# in/entory name in the :'u#in/entory: ield. 'a/e your 3or7 #y clic7ing on the :'a/e: #utton on the tool#ar. Close the 5istri#utions 3indo3. Close the 'hipments 3indo3.

'tep 15 'tep 1$

The 'hipments 3indo3 appears. The Purchase ;rders 3indo3 appears displaying your purchase order. The 'hipments 3indo3 appears. The 5istri#utions 3indo3 appears. Aour 3or7 is sa/ed. & note appears ad/ising you that your 3or7 is sa/ed.

'tep 1( 'tep 1* 'tep 1+

Place your cursor in the item ield o line 3 and then clic7 on the :'hipments: #utton. Clic7 on the :5istri#utions: #utton. .nter the re0uester name in the :,e0uester: ield. .nter the deli/er to name in the :5eli/er=To: ield. .nter the su# in/entory name in the :'u#in/entory: ield. 'a/e your 3or7 #y clic7ing on the :'a/e: #utton on the tool#ar.

Step 7ame
'tep 2! 'tep 21

Description
Close the 5istri#utions 3indo3. Close the 'hipments 3indo3.

E9pecte/ Resu%t
The 'hipments 3indo3 appears. The Purchase ;rders 3indo3 appears displaying your purchase order. The &ppro/e 5ocument 3indo3 appears. The Purchase ;rder 3indo3 appears. ,ecord the purchase order num#er. &pplication shut do3n.

'tep 22 'tep 23

Clic7 on the :&ppro/e...: #utton. Chec7 the :'u#mit or appro/al: #o2. Clic7 on the :;B: #utton. Close the application.

'tep 24

E9amp%e of inade#uate test case :

2%an" 0escription= 2urpose" 2rere;uisites" Data Re;uire/" (e"uisitioning an asset re"uires the use of a specific account code (<<<<<<<<<<<<<) )teps=

)tep 3ame 'tep 1 'tep 2 'tep 3 'tep 4 'tep 5 'tep $ 'tep (

0escription ?>oteC .nter an Internal ,e0uisition and &dd items to the shopping cart@ 9se the Internet Procurement responsi#ility to log into applications >a/igationC C '6' Internet Procurement .nter 2222 in 'earch Full Internal Catalogue ield. Press the #utton D1;E 'elect the lin7 :Clic7 here to select source: .nsure that the radio #utton or the Internal 'ource FFFFFF is selected8 and that the su#in/entory sho3s FFFFFF Press the #utton D&dd To CartE Press the #utton DGie3 Cart ad Chec7outE 'ystem displays the orm :'hopping Cart Contents: 'elect DChec7outE #utton The <Chec7out ,e0uisition In ormation: page is displayed. Clic7 on the lashlight ne2t to the :5eli/er to "ocation: ield. Clic7 on the lashlight ne2t to the :5eli/er to "ocation: ield. The :'earch &nd 'electC 5eli/er To "ocation: page 3ill #e displayed. &ccept the de ault 5eli/ery To location or search or ne3 "ocation Press the #utton D1;E "ocation ound as FFFFFFF< Clic7 on the <'elect< #utton against the location named <<FFFFFFFF<. Aou 3ill #e returned to the <.nter 5eli/ery In ormation< page. Press the #utton D'electE Press the #utton D>.FTE :,e/ie3 Charge &ccounts: page is displayed

,-pected 1esult

Item FFFFFF ound

'tep * 'tep + 'tep 1! 'tep 11 'tep 12 'tep 13 'tep 14 'tep 15 'tep 1$ 'tep 1( 'tep 1* 'tep 1+

'tep 2! 'tep 21 'tep 22

%uild &utomated 'cripts

.2ecute &utomated 'cripts

,eport on .2ecution ,esults

)tep 3ame 'tep 23 'tep 24 'tep 25 'tep 2$ 'tep 2( 'tep 2*

0escription Press the #utton Dedit "inesE Clic7 on &ccounts = ,eturn <.nter >otes and &ttachments< Clic7 attachments. ,eturnH,eturn Press the #utton D>.FTE ,e/ie3 appro/er list - enter 4usti ication and note to #uyer The <,e/ie3 and 'u#mit ,e0uisition< page is displayed. >e2t Ta7e note o the re0uisition num#er. 'elect D'u#mitE #utton The :'u#mit Con irmation: page is displayed. Clic7 on ,e0uisition ta# to /ie3 the status o the re0uisition created in the last step Clic7 on the upper right corner and "og out.

,-pected 1esult & re0uisition re0uiring appro/al is created.

'tep 2+ 'tep 3! 'tep 31 'tep 32 'tep 33