24 Common Mistakes You Made In Website Testing

Image for post
Image for post

Website testing sounds simple, yet is complex, based on the nature of the website. Testing a single webpage is simple and can be done manually. But with the nature of web applications becoming complex day by day, especially in the current age of robust, dynamic single page applications that are developed using Angular or React, the complexity of testing is also increasing.

As website testers we are bound to make mistakes, after all we are only human! The pressure of working under Agile environment for coping up with fast-paced delivery for go to market launch. There have been some common areas that we end up forgetting as we test a website or a web application. Today, I am going to share some key notes to avoid mistakes in website testing. These notes would help you ensure a robust delivery irrespective of whether you are testing the web application manually or in an automated environment. Without further ado, let’s get started.

1. You Forget To Test Accessibility

Imagine you are launching a website that targets the audience in China. For a large demographic region like China, where the population is more than 1.38 billion, even if 4% people are physically challenged and have trouble going through your site using a screen reader or any other device, that means, your site loses almost 50 million audience.

Moreover, to get ranking in the search engine results, Google demands that your website must abide by WCAG guidelines that state that a site should be accessible by everyone, especially by people who are disabled. Hence, this is something that you must not forget and pay special attention to, while the testing phase of your website or webapp is executed.

2. Is Your Stage Environment Perfectly Configured?

3. Did You Chalk Out Everything According to the Deadline

Image for post
Image for post

Once I worked in a project that involved us creating a cross browser compatible web application. Agile methodology was not that popular at that time. While the development team was doing their work, the testing team, instead of going through the business documents and figuring out a plan for starting and executing the test cases, waited for the developers to complete their work. Development team took a little more time than anticipated but they completed their part. However, that delay caused a lot of stress among the testing team, the testers were in a rush since a huge load of work came on their shoulder all of a sudden.

To avoid such mistakes in website testing , it’s better to chalk out a plan earlier, so that once the development is done, without any waste of time, testing begins immediately. The shift left testing approach came into the application with the intent of minimizing the time required for testing by implementing a methodology where writing the test cases begins even before development starts.

4. You Forget About Selenium’s Limited Reporting

5. Slipping Out On Hyperlinks

Also, do remember to check via browser compatibility testing. Often it has been observed that “a href” works in one browser and does not work in another, especially if the browser is a lower version of IE.

6. Missing Out On Cross Browser Testing

Image for post
Image for post

7. You Forget About Responsiveness Across Various Devices

LambdaTest offers a feature of responsive testing for you to test your RWD(Responsive Web Design) on 44 desktop and mobile devices in a single test session.

Image for post
Image for post

8. Not Paying Attention To Page Loading Speed

You can test the speed of a webpage using Google PageSpeed Insights.

9. Not Bringing The Appropriate Candidates For Usability Testing

10. Using Playback & Record For Automated Scripts

11. That 404 Is Always A Headache

Image for post
Image for post

It is the designer’s duty to brilliantly design a 404 page which ensures that the user will keep on guessing how excellent the actual site can be once its up. In fact, the requirement of most new sites demands a customized 404 page as well. As a tester, check if the 404 error page is displaying the customized one or the general blank page. As a tester, you need to commit for a thorough validation of 404 errors to avoid any mistake in website testing.

12. Did You Test All Your CTAs?

Image for post
Image for post

13. Company Logo Must be Clickable

14. Stop Daydreaming About 100% Automation

15. Always Keep An Eye Out On Analytics

Image for post
Image for post

16. Hacker Alert! Does Your Website Pass All Security Checkpoints?

Read our blog, if you are curious about finding the influence of Microservice architecture in Security testing.

17. Did You Check How it Performs Under Heavy Traffic On Stage Environment?

Although, we keep load testing in our checklist but we restrict it to only our production environment. We should not! You should also perform load testing on Stage environment so you could get an estimate of how the code would respond to an excessive number of queries. Here are 13 reasons why Staging environment is failing for your organization.

Image for post
Image for post

18. Does The Site Comply To All Mandatory Compliances?

19. Did You Check The Security Of All Data Entry Points For User Confidential Information?

20. Are You Relying Too Much On Hardcoded Data ?

21. Have You Checked The SSL Certificates?

Image for post
Image for post

22. Depending Too Much On Selenium WebDriver Alone? Beware Of Scalability Issue

23. Did You Perform Website Testing Through Various Geo-Locations?

With LambdaTest, you can use tunnel for testing your locally hosted website or webapp through various geolocations using a VPN. Here is a blog to help you perform Geolocation cross browser testing through VPN on LambdaTest.

Image for post
Image for post

24. Are All Web Elements Having Well Defined IDs?

Although there is a myth in the industry that testing is a boring job, the best thing about being one is that every day you get to learn something new. Especially when the current software testing trends are shifting more towards
automation testing through machine learning and AI, testers will get the opportunity to learn to code as well. So make mistakes, you will make lots of them. But the important thing is whether you are learning from them and make sure not to repeat them. Hopefully, the mistakes I’ve listed above will help you a lot in avoiding them while testing a website. Do let me know if you faced any other common mistake during your career.

Arnab Roy Chowdhury is a UI developer by profession and a blogging enthusiast. He has been writing content for about 5 years and has strong expertise in technical blogs, travelogues, and content in the latest programming languages.

Originally published at LambdaTest

Author Arnab Roy Chowdhury

Image for post
Image for post

Written by

Product Growth at @lambdatesting (www.lambdatest.com)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store