Test format specs
PC Requirements
1. Outlook express should be the default emailing program
2. PC Date format should be: dd.mm.yyyy
3. PC Time format should be: HH:mm:ss
4. PC decimal separator should be “.” (dot (t o c h k a)!)
5. PC format and standards / location should be English (United Kingdom)
6. Root of all BST code can be located everywhere (and folder, any drive)
7. BST is working on S drive only
8. In order to have all drives required for correct working of BST you have to run SUBS_THIS_SILK.BAT located in BST root
9. SilkTest should have Options / General / Save Outline set as “Collapse All”
10. BST code is located on VSS : $/_Misc/Testing
11. You should have FIELDPRO client installed.
12. Install R:\Work\Visual Source Safe 2005\setup.exe
14. If you are using movie recording during test cases you have to install camstudio
15. For some tests you should install Adobe Acrobat 8 Professionnal Full (wkgn)
16. For some tests you should install WinRar (see key)
Test format requirements
1. Each test should formed as separate .t file and separate folder on s:\ drive
2. Each test should be derived from CDBTest* and should have next methods overwritten:
A. virtual string GetTestName()
B. virtual void DoTestCase()
C. virtual string GetTestGUID() (after this method is implemented – corresponding guid with name should be inserted into the statistics database)
D. virtual string GetTestCaseName()
E. virtual string GetTestCaseOutFldr()
F. virtual string GetDSNName()
G. virtual string GetFiPUserName()
Command line mode
Example of running test from command line:
"C:\Program Files\Segue\SilkTest\partner.exe" -q -r S:\FIP_WILI_JAKIRA\FIP_WILI_JAKIRA.t "noinstall"
Command line switches for tests:
1. "noinstall" – indicates that no FIELDPRO installation script will be launched
2. “fieldpro@resnet.com” – any argument passed with “@” symbol is treated as email to which final report should be sent
3. “nodbrestore” – indicates that no FIELDPRO database will be restored
4. “dbtaccess” – indicates that test will be performed on MS Access database type
5. “dbtoracle” – indicates that test will be performed on Oracle database type
6. “dbtsql” – indicates that test will be performed on MS SQL Server database type
7. “version#x” – indicates which version will be used for testing. Example “version#e”
8. “debug” – indicates the test is under debug (no emails will be sent to fieldpro@resnet.com and output logs will be placed to W:\DEBUG\OUTPUTS\ instead of W:\OUTPUTS\)
9. "recordmovie" – indicates that during Testcase a movie will be recorded (.avi file with the same name as test log will be placed along with the log file)
10. “netsend:” – indicates that after test is finished it will send net send message. This parameter format: “netsend:svan test is finished”. Here svan is the host name; all the other characters after space are the message itself.
11. “dbtype:” – indicated which db type should be used for test. Available values: “msaccess”, “mssql”, “oracle”. It is used only in tests supporting this option.
12. “step:” – indicated which step should be used for test. It is supported by some scripts that consist of several stages. Available values: “1”…. Example: “step:3” – means only step 3 will be performed.
12. “startstep:” – indicated which step the test should be started from. It is supported by some scripts that consist of several stages. Available values: “1”…. Example: “startstep:3” – means the test will start from step 3 and continue to the number steps.
General Requirements
1. When you are awaiting for some screen to appear after specific action – use WaitForWindow function located in s:\cmnutils\cmnutils.inc. Example:
MainScreen.File.Pick()
WaiForWindow(OpenDialog, 3)
1. Usually you should have the latest Fieldpro version installed each day morning to be sure the latest updates are tested / worked out.
2. All the changes put on vss must be accompanied by TT ID or chat with request to do the changes.
3. Code should be separated by blocks when you are working with different screens, next example is not acceptable:
Scrceen1.SetActive()
Scrceen1.PressButton()
Scrceen2.SetActive()
Scrceen2.PressButton()
It should be formatted as:
Scrceen1.SetActive()
Scrceen1.PressButton()
Scrceen2.SetActive()
Scrceen2.PressButton()
Installations and local versions
In normal mode test are supposed to be working each day for local version at approximately 16:00.
Each morning at 6:00-7:00 tests are run on the Acton installations.
If you need to run tests on Minks installations instead of Acton installations next line should be changed in START_UP.BAT:
CALL "%CD%\SUBS_THIS_SILK.BAT"
by
CALL "%CD%\SUBS_THIS_SILK_BEL.BAT”
