Let’s look at the process of clicking a link. Whether it’s navigating a menu, following a link, or filling out a form, many people will click elements in order to use web pages. Either way, most people do this hundreds of times per day. One of the most common actions a user can take is clicking or tapping, depending on your device. The test concludes by reporting: PASS 4 tests executed in 8.855 seconds, 4 passed, 0 failed, 0 dubious, 0 skipped.
The tests report that this blog post was loaded, navigation via mouse to was successful, navigation via keyboard to the Contact form was successful, and the form was filled with our test data. A preview of the testĪs with each of these articles, let’s start with the successful test output so you’ll know what we’re working toward: The image depicts console output displaying four successful Casper JS tests. In this article we will simulate user behavior in order to change the state of the interface. However, both of these examples were only using Casper to read data from the page, instead of interacting with the user interface.
#CASPERJS BENCHMARK TESTING CODE#
In part two we explored Casper’s ability to execute any JS code you write as if you did it within the browser console. In part one we ran functional tests on Picturefill by measuring the behavior of the script in response to the browser’s viewport width changing.
0 kommentar(er)
