SeeTestAutomation - Slow Launch
Please note that this tool is classified as a Legacy tool. We recommend transitioning to our updated solutions to maintain optimal performance and security in your workflows. For more information on this matter, please reach out to technical support .
General explanation:
-
Some applications take a longer period of time to launch. This might result from a need to connect to a network at start-up. If the network conditions are poor, the application will take longer to launch. Other reasons exist as well, like the sheer size of the application being significantly large. This means that not every failure of the launch command is due to a failure of the application. Sometimes SeeTest will stop waiting due to a slow launch and give an error. Before concluding that the application fails to launch, one should try the slow launch option.
-
Warning: You should make sure you remove the app property that is described in the following section of this page once you are done using this option. If you don't, then the slow launch will take place whenever you use the launch command.
Recognizing a possible failure due to a slow launch:
- In the logs the following message will appear:
The app was not found. This might be due to extensive launch time or total failure to launch
Solution:
The waiting period of SeeTest can be prolonged by changing the app.properties file.
- Open the app.properties file (How To Open app.properties File).
- Add the following parameter:
Name: launch.wait.for.app.in.milliseconds
Value: time (in milliseconds)
For example:
launch.wait.for.app.in.milliseconds=18000
3. Save the file, and rerun your test. SeeTest will prolong the waiting period for your app by the amount of time you inserted in the app.properties file.