Automated Website Testing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
== Notes == | == Notes == | ||
=== See also === | === See also === | ||
* [Selenium browser drivers | * [Selenium browser drivers https://github.com/dbarchowsky/bfhweb-tests/wiki/Selenium-and-browser-drivers] - `bfhweb-tests` wiki | ||
* [https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Cross_browser_testing/Automated_testing Introduction to Automated Testing] - developer.mozilla.com | * [https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Cross_browser_testing/Automated_testing Introduction to Automated Testing] - developer.mozilla.com | ||
[[Category:Web Development]] | [[Category:Web Development]] | ||
Revision as of 16:46, 7 May 2022
Running tests on localhost
If .htaccess forces https redirects, make sure to make exceptions for host.docker.internal and the web app's Docker container.
If .htaccess defines authorization rules, make sure there are exceptions for requests coming from containers within the local Docker network.
AuthType Basic AuthName "Restricted area" AuthUserFile "/path/to/passwd" require ip 172.16.0.0/255.240.0.0 require ip 192.168 require valid-user
See bfhweb-tests and Selenium browser drivers.
Notes
See also
- [Selenium browser drivers https://github.com/dbarchowsky/bfhweb-tests/wiki/Selenium-and-browser-drivers] -
bfhweb-testswiki - Introduction to Automated Testing - developer.mozilla.com