I am struggling with AutoIt regression tests. AutoIt was chosen because the requirement is 100% black box GUI testing (without interfering with the test project). This solution still has some problems that I need help with.
Change tabs in the application . Since the GUI class is not SysTabControl32, but SWT_Window, the sample code from GUITab.au3 UDF does not work. The current solution focuses on the component, and then moves through the tabs using the arrow keys. This affects the performance of the test badly (and I don’t even want to assume that the future possibility of disabling some tabs).
Timeouts . When the tabs change, the tests must be delayed before they can continue. The shorter the delay, the greater the likelihood of a test failure (the application was not ready to continue the test). This leads to large delays before actions.
Instance numbers . Identifying control instances is a problem. When I wrote the OK test button, she had instance number 9. When some buttons were added to the form, I had to rewrite the test because this changed the instance number of the OK button.
These three are the most important.
Changing the testing technology would be difficult due to the large number of tests already written. But I'd rather write a new test. Sikuli has problems getting text from the screen, and SWTBot has dependencies in the tested projects.
Our tests run for 20 hours, and when changing the layout of the GUI I need to edit almost every test (problem with the instance number). Can anyone suggest a solution or workaround for the highly reliable Blackbox testing?
source share