Here comes July and hopefully the rains of June are over. This month we decided to dive down into our roots and explore our functional testing services. Along with some security tips and tricks, we look into what happens when functional testing goes wrong and how to avoid a blunder.
Your digital fix
While scouring Nike’s website for some new gym clothes, one of our team members noticed a defect on their main landing page. None of the main advertisement pictures were loading on I.E. This might not be seen as a big issue but given that Nike’s main text is white, users were shown a blank landing page with white text on top. Not good right?
You can’t see it on this image but in the bottom left corner, there’s a header saying ‘Hear us roar’ in celebration of the Women’s world cup. Naturally, we wanted to test this a bit just in case one of our devices was slow. But after multiple tries on different devices, the images still failed to load. What’s odd about this is that it shouldn’t have happened, let alone be seen by a user. Nike has prepared for situations like this and joined together with a web testing partner, who should prevent any defects from being seen by users.
Given that this defect was on the front page of their site, it’s questionable as to how their partner company didn’t discover the defect before one of our team members did while online shopping. This is a prime example of ensuring your third parties are actually reporting back findings and not just skimming your website.
Of course, now the bug has been fixed once we made a little noise about it, but it’s still unknown how long the defect was live for and how many customers turned away after being thrown off by a defective website. Especially given Nike’s prestigious position.
Our highlight of the month explores the bread and butter of our company. Functional testing. This type of web testing often gets a bad rap for being mundane and a bit boring, meaning many companies perform functional testing but don’t actually do it.
What I mean by this is often team members are unaware of functional testing’s scope and how it actually improves your website in the real world. So, using real-world situations we go through three examples of how functional testing improves your website, along with its limitations and the big debate surrounding manual versus automatic testing.
In general, our highlight of the month is a good read just to get a deeper understanding about functional testing, without all the jargon and terminologies designed to make it seem more complex than it actually is.
The Big Hits
Functional testing in a nutshell by Max Buster: “[…] it’s best to have the tests defined before development starts and after product requirements are defined but often they are created after the product is created and simply written to mimic the current state of the product. While this may prevent future regressions, it is not driven by the software development process and thus, can cause issues with QA and development.”