Allgemeine Fragen/en: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Ani (Diskussion | Beiträge) |
Ani (Diskussion | Beiträge) |
||
| Zeile 4: | Zeile 4: | ||
==== Why is my HTTPS page or page with frames not loaded correctly? ==== |
==== Why is my HTTPS page or page with frames not loaded correctly? ==== |
||
:A test can be executed in different browser types (firefox, iexplore, chrome, iehta). You can find this setting in the variable environment of the execution definition. For HTTPS pages or pages with frames, use iehta and chrome instead of iexplore and firefox. These have lower security settings |
:A test can be executed in different browser types (firefox, iexplore, chrome, iehta). You can find this setting in the variable environment of the execution definition. For HTTPS pages or pages with frames, use iehta and chrome instead of iexplore and firefox. These have lower security settings |
||
==== After a click event on a link, the system does not wait until the corresponding page is loaded ==== |
|||
:If you do not wait for the corresponding page to appear during playback, replace the click event with a clickAndWait event. |
|||
:However, this only works if the click actually triggers a page load operation. Especially in modern web applications the click only triggers a JavaScript function, which creates new elements or makes them visible. In this case it is better to wait for the element to appear before the next interaction with a "waitForElementPresent". But beware: if an element with this locator was already there before, you might have to do both: "waitFor-Reload the page" plus "waitForElementPresent". |
|||
Version vom 11. April 2019, 13:53 Uhr
Why can't pages be loaded?[Bearbeiten]
- Check whether the URL of the website to be tested is correctly specified as the urlToTest environment variable in the corresponding step, test plan or test-suite.
Why is my HTTPS page or page with frames not loaded correctly?[Bearbeiten]
- A test can be executed in different browser types (firefox, iexplore, chrome, iehta). You can find this setting in the variable environment of the execution definition. For HTTPS pages or pages with frames, use iehta and chrome instead of iexplore and firefox. These have lower security settings
After a click event on a link, the system does not wait until the corresponding page is loaded[Bearbeiten]
- If you do not wait for the corresponding page to appear during playback, replace the click event with a clickAndWait event.
- However, this only works if the click actually triggers a page load operation. Especially in modern web applications the click only triggers a JavaScript function, which creates new elements or makes them visible. In this case it is better to wait for the element to appear before the next interaction with a "waitForElementPresent". But beware: if an element with this locator was already there before, you might have to do both: "waitFor-Reload the page" plus "waitForElementPresent".
