One of the more fun meme & # x27; s on the internet is the & # x27;correlation does not mean causing& # x27;. One of my favourite examples of this ishalt globular warming: become a pirate. Application development, and society at large, are full of these[fun]problems. So what have we incorrectly correlated in the browser automation niche? The number of browser-based handwriting and a lessening in tryout rhythm time. First off, the conclusion to be & # x27; do & # x27; quiz is reallyrather arbitrary. And though the input into that decision are often rather uniform, occasionally someone or something will throw a imp twist into the mix and people make a guess/take a hazard. Therefore, there is no correlation between the number of playscript and test cycle time. What people often mean by that & # x27; decrease in exam cycle clip & # x27; is that they are achieving a particular level of & # x27; quality & # x27; in less clip. I had one client whose testing time took 10 years and they desire it to be three with the & # x27; like quality & # x27;. The problem here is that as your application gets larger and more complex, that those & # x27; same quality & # x27; destination posts becomes across-the-board and wider. And writing more and more automation isn & # x27; t going to slow that gap nor shrink it. This motor us to the fundamental purpose of all this automation we publish and of quiz in general. And that isto provide info. Automation that achieves this goal state the consumer (s) of the information[the resultant]a status of the application / build. These things appear to act, these thing seem not to work.In a Continuous Delivery-esque workflow this means the manual testers can know they can focus on the new/changed/unautomated parts of the application largely ignore the others. This is truly where those savings come from. This also means that you need to approach how you decide what to automate differently. Again, there is no correlation with the volume of script execution and the value of the info provided. I & # x27; ll usually appreciate 20 different handwriting that broadly cater different tidbits of information versus 20 scripts that narrowly checks battlefield value permutations on a shape. So how do we reword the original statement to take the causation/correlation problem and increase its truthiness? It & # x27; s a little wordy, but how about this?The number of browser-based playscript can decrease the time squander by manual testers either exploring bad builds or re-checking thing by providing a base information set thusly decreasing examination rhythm clip.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.