Damien at work

gistfile1.txt

almost always run in QA00, rarely runs in QA03

-  Documentation of framework
-	Manual test case examples to help get familiar with iSeries processes
	
-	Explanation of folder structures
-	Overview of XML environment files
	-mainly use QA00, SOX and SPS
	-others are for special cases, rarely used
-	Explanation of driver script and related scripts that are called
	-Driver, OEActions, CDWAction
	-Driver loads up all of hte test data and determines if OEActions call is necessary
	-CDWAction handles all of the calls for the OrderActivityItem which then gets into into the function libraries, calls BPAction
-	Overview of test flows


use General.qfl for ineracting with the screen, provides records of what happens. Handles logins and other 

importing data from datasheets is handled by the driver scripts, not the qfls.

need to know 

3 test groups: iSeries, EDI, SOX

use template iSeries.CAF in QC
	populate excel file and BusinessProcessName(test case name)
	
Only one ObjRepo for all areas/tests
	-needs to be checked out if changes are made
	
Check out the Wiki for basics of how to interact with iSeries
itwiki


========================
#Persistent
Menu, Tray, NoStandard ; remove standard Menu items
Menu, Tray, Add , &Change, Change ;add a item named Change that goes to the Change label
Menu, Tray, Add , E&xit, ButtonExit ;add a item named Exit that goes to the ButtonExit label
Return

Change:
MsgBox Hello
Return

ButtonExit:
ExitApp