Skip to content

Demonstration Videos#

Original Author Ville Purhonen
Last Checked By Ville Purhonen
Last Updated 25.01.2025

Going through some demonstration scripts in the embedded videos.

GUI install#

If you are installing prestashop manually on an Apache server, the graphic UI portion has to be clicked through on the browser. This script automates that portion of the installing process. The demonstration has the database credential variables in plaintext inside the script, but in actual production code you should always just reference some kind of external source to minimize the risk of exposing passwords and such.

Account creation#

Automated test to create an account. Important takeaway here is that you need to do both the correct steps like filling the info and also do a confirmation at the end, in this case checking that the Log out box appears in the main screen. If you don't add a confirmation such as an element or text appearing at the end of a test, there is a risk of the test giving a false positive which is more harmful than a false negative from production standpoint. A false negative (reported failure even though it really passed) will be noticed quickly and the test can usually be done manually to double check it. A false negative (reported success while in reality failing) gives no information to the developer team, which in the worst case scenario can mean a critical bug ending up in code delivered to a client.

GUI colour check#

A fairly trivial test, just checking if background element colours are what they should be. The point is to demonstrate something Browser library is capable of doing that Selenium can't do. In actual production use Browser is preferred mainly due to much quicker execution, which matters when you are running regression tests with possibly hundreds of individual tests. But in smaller scope the differences between Selenium and Browser are negligible.