Forum Discussion
budiaraf_ex
10 years agoOccasional Contributor
Thanks for the answer Marsha.
I agree that closing those extra windows would be ideal, but our application is so big at this point that it would be unreasonable and unrealistic to try to catch all the instances of this happening.
I find that I can get around this by calling Sys.Refresh() and then some_dialog.RefreshMappingInfo() just before some_dialog gets used, but this solution is not at all ideal as this adds an extra manual step to the automated testing procedure (QA has requested we keep to keyword tests).
I don't think the index would work for us as we are working with short, incremental tests and can't guarantee the order the tests will be executed. Windows might appear before their index.
At this point I'm wondering/looking into if there is some way we can write a script to call those two methods before each step, or set of steps in a keyword test.
I agree that closing those extra windows would be ideal, but our application is so big at this point that it would be unreasonable and unrealistic to try to catch all the instances of this happening.
I find that I can get around this by calling Sys.Refresh() and then some_dialog.RefreshMappingInfo() just before some_dialog gets used, but this solution is not at all ideal as this adds an extra manual step to the automated testing procedure (QA has requested we keep to keyword tests).
I don't think the index would work for us as we are working with short, incremental tests and can't guarantee the order the tests will be executed. Windows might appear before their index.
At this point I'm wondering/looking into if there is some way we can write a script to call those two methods before each step, or set of steps in a keyword test.
Related Content
- 12 months agomtsapa
Recent Discussions
Name Mapping Issue
Solved2 hours agokgreger1- 2 days agodhundley