As you know, each site is unique and although usually the same navigation and implementation principles apply, you still have to do a lot of manual work to reverse-engineer it, so that you can successfully simulate the user actions. Matters get much simpler if you know how the site is built and don't have to guess. In this example check we're going to build a script that navigates to the BBC UK web site at http: //news. bbc. co.uk/, selects the top front-page story, and follows that link.
This check is a good example of a monitor that simulates one of the user behavior patterns and also tests the internal web site logic for at least two functions: the ability to generate the front page and the ability to generate the top story content. We'll also monitor the execution time, and if it exceeds the preconfigured threshold, we'll alert on that as well.
Was this article helpful?