Looking for a quick introduction into the different types of web testing options, which isn’t bombarded with tec savvy jargon? Yes? Then you have come to the right place.
Let’s start with the first ground-level type of testing.
This type of testing has been adopted by many companies as their primary testing technique because it’s relatively quick, easy and doesn’t require any additional internal aid.
Exploratory testing is all about letting the animals free on your site. Testers are allowed to casually surf through your site, picking up any defects which they come into contact with along their merry way.
There’s a huge amount of personal freedom associated with exploratory testing and it’s generally regarded as a more ‘relaxed‘ type of testing. Of course, exploratory testing does have its strengths. Using this type of testing to routinely check through your site, it hugely decreases the risk of any users coming to contact with defects which will prevent conversions from being completed.
The key thing to remember is: exploratory testing shouldn’t be used as your core testing method during new releases. Mainly because it doesn’t provide a detailed analysis of your site while updates are being made.
Scenario Testing (or exploratory +1)
Scenario testing is the next step up from exploratory and offers something a little different. Unlike exploratory testing, scenario testing follows real user journeys and ensures that any updates are functioning correctly end-to-end. Testers do still have some freedom but it’s more regulated than exploratory.
Testers are generally given a brief outline of the type of user journey they are to perform (for example, search for brown shoes and add a size 10 pair to the cart). They then have the choice of which brand and style they want to buy.
Scenario testing is primarily used when a company knows a certain part of their website isn’t performing correctly and wants to ground down the defect to its specific details.
If you want to know more about scripted testing email us at email@example.com or call 0330 088 0880.
Improv or scripted? Script testing
Scripted testing is the highest level and most detailed testing method we are going to cover today. It requires a large amount of time to perform and uses written test scripts. Before we dive into test scripts, I should firstly state that unlike the other forms of testing we have covered, scripted testing has a pass or fail quantifier. This is what makes scripted testing so different from the others.
Test Scripts: A test script is a set of instructions, written in code, to be followed under a testing environment and used to verify if a system performs as expected. If the system performs as expected it passes the test, if it doesn’t it fails.
Within a test script, are test cases. Test cases are the steps which ensure the system works as expected. For example, you have a test script which wants you to buy Nike black shoes in size 10. In this test script every stage of the buying process is documented (1. go onto Nike homepage, 2. hover over the shoes tab, 3. click on Mens shoes, etc) and these stages are known as test cases.
Scripted testing requires the most amount of effort as the test scripts and cases have to be written out and updated frequently, depending on your type of site. If you manage an eCommerce site with multiple uploads and updates happening most of the time, then your scripts will go out-of-date quickly and need to be rejuvenated frequently. The strength of scripted testing is that it precisely pin-points issues across browser and device combinations, meaning your internal teams don’t have to run around trying to find defects on every device and browser combination known to man.
All your eggs in one basket
Contrary to popular belief you don’t have to choose just one testing method and stick to it. Instead, view testing as a pick and mix where you can tailor testing to your needs. Not only does this mix and match method improve the quality of your digital performance internally but it also improves the online user experience.