|
FRM v1.4.2 |
||||||||
PREV SCRIPT NEXT SCRIPT | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | FUNCT | DETAIL: FIELD | CONSTR | FUNCT |
CompiledModule | +--emos_std_list_lib
This library contains alternative implementations of standard functions that operate on list objects (list_x() functions). Reasons for alternative implementations can be various. They should be carefully documented with each function. Another sort of functions in this library are functions that implement some additional functionality that would probably fit into Mercury's logic for list_x() functions.
Function Summary | |
String |
list_item_exists(in obj,
in regex,
out pos,
in soft)
Checks whether the list contains a particular item. |
String |
list_select_item1(in obj,
in item)
This function was created as an attempt to solve a particularly ugly bug in WR 6.0 / 6.02. |
Function Detail |
public String list_item_exists(in obj, in regex, out pos, in soft)
list
contains a particular item. You can search for
items that must exactly match the search string str1
or contain the
searched substring.
obj
- (in) list object to be searchedregex
- (in) string to search forpos
- (out) item number in case soft
- (in) (optional)
TRUE = matches a substring
FALSE = exact match [default: FALSE]
public String list_select_item1(in obj, in item)
PROBLEM DESCRIPTION:
Hier and then we had the problem that after restarting WinRunner, list objects wouldn't work properly. For some reason list_select_item() would suddenly not work although the item was still there and neither application nor the test (that's what we thought) changed. GUI editor would show no problems whatsoever with any of the list objects. Only the selecting would not work. The only way to "solve" the problem was to re-install WinRunner. Finally, after days of searching,, we have discovered, that after some WinRunner crashes, the default timeout value (saved in wrun.ini, where else) had a value of 10 instead of 10000. This has explained why this problem only occurs in WR 6.0. It is 6.0 when timeout was changed from seconds to miliseconds. Obviously, somewhere deep in some WinRunner dll there is still a peace of logic that thinks in seconds instead of miliseconds. Since we know what Mercury could claim, we have checked our test scripts - they are deffinitely fine. It is WinRunner who causes problems.
PROBLEM SOLUTION:
There are several solutions for this problem:
obj
- (in) name of the list objectitem
- (in) item which is to be selected
|
FRM v1.4.2 |
||||||||
PREV SCRIPT NEXT SCRIPT | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | FUNCT | DETAIL: FIELD | CONSTR | FUNCT |