So, how should we use Selenium within our overall strategy? Simply put, Selenium takes the commands that you ask it to execute on the browser and performs that task. A mutual misnomer is that Selenium is running trial direct on your package, the world is that it is actually interact directly with the browser that is running your software.

The package development lifecycle is a process that runs from the gathering of requirements and design all the way to release. You actually want to be focusing on Selenium during that part of the process that we are testing code and making sure it behaves the way we require it to execute in order to render the best possible user experience. From that mentality, we truly want to think of Selenium as a UI fact-finding tool. Clearly, this is just one part of your testing mechanization journey, the overall strategy is much more in deepness.

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Check out this picture for more on how I think we should approach Selenium.

video

Come back future week when I discourse the departure between testing APIs and testing UI.