| |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
Defines an interface for efficient creation of test cases unsing the FRM data tables.
A typical FRM test case defines its test data across columns. This is the plain oposite of the approach taken by Mercury and many other testers. The benefit of defining test data column-wise is the ability to define many, very many (up to 64k) test entries which makes very complex tests possible (accross rows the limit is 256) which are comparatively easy to maintain (no ugly right-left scrolling, you can see much more test data at once). Additionally, you can (hypothetically) "pack" up to 254 of such complex tests in a single Excel-file wich can greatly reduce the mess on your hard drive.
A single test case contains three important parts:
name
content of the cell in the first rowsequence
a single cell containing the list of test steps
which are to be executed in a sequencestep(s)
an indexed block of rows containing test dataIDX | Name | 1 | 2 | 3 |
---|---|---|---|---|
x | Testsequence | select_user user_data | select_user user_data | select_user |
x | select_user | |||
user list | dean | dean | ||
New/Edit/Delete | New | Edit | Delete | |
delete? (OK/Cancel) | OK | |||
x | user_data | CHK | ||
first name | dean | dean | ||
last name | rajovic | rajovic | ||
OK/Cancel | OK | Cancel |
Method Summary | |
int | FRM_STP_clear_steps(in tid, in test) Frees all references to the specified test. |
int | FRM_STP_get_next_step(in tid, in test, out step, out mode) Returns the next step. |
int | FRM_STP_has_more_steps(in tid, in test) Indicates whether there are steps to execute. |
int | FRM_STP_init_steps(in tid, in test, in idx) Initialises the step iterator. |
int | FRM_STP_is_dummy_step_mode() Indicates the dummy test mode. |
int | FRM_STP_set_dummy_step_mode(in mode) Turns dummy test mode on/off. |
Method Detail |
public int FRM_STP_clear_steps(in tid, in test)
public int FRM_STP_get_next_step(in tid, in test, out step, out mode)
LINK
executes a test in this or some other data table,
the test is atomatically loaded if necessaryLINA
same as LINK while loading ALL tests from the specified
table (sometimes impoves the overal performance)LINX
executes a specified test from an inverted data table
(table in which tests are organised/indexed horizontally)CALL
invokes an arbitrary WinRunner main testEVAL
invokes an arbitrary WinRunner functionEXEC
evaluates a block of WinRunner functions#
any step starting with # is treated as a commentLNK:script_name
links this test with another one
(loading only the specified tests)LNA:script_name
links this test with another one
(loading all tests in the referenced table)EXE:test step
exectutes all rows in the specified test block###:test step
comments out the given test step<<PAUSE>>
pauses the test execution in interactive modepublic int FRM_STP_has_more_steps(in tid, in test)
public int FRM_STP_init_steps(in tid, in test, in idx)
public int FRM_STP_is_dummy_step_mode()
public int FRM_STP_set_dummy_step_mode(in mode)
| |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |