Professional Documents
Culture Documents
Want to know how to test your website? Here you can find information about the
main website testing techniques. We will consider website testing checklist items to
go through for ensuring your site readiness for the launch.
ARTICLE CONTENT
Documentation testing
Website functionality testing
Usability testing
UI (User Interface) testing
Compatibility (Configuration) testing
Performance testing
Security testing
Change related testing
Mobile-friendly testing
Beta testing
How to test your website with EasyQA Chrome Extension
Testing, as the final stage of the development of the website, plays a vital role in the
process of creating high-quality software.
After the website testing, the customer is provided with a ready project without
errors, with good readability, perceived ease, convenience, and reliability.
The basic rules for testing of a website are steps that show the user how easy and
logical the project is, how easy and possible to find the required information.
The more complex the site, the more time it takes to test it and debug it. Depending
on the specifics of the project, up to 50% of the total budget and time resources can
be allocated to test a website.
Testing can occur in a variety of ways, but do not forget about the process itself and
the testing strategy. The sequence of your actions depends on it.
So, let’s consider the main stages you have to pass to test your site. Look at the
picture below. Here you can see them.
This is could be like some website testing tutorial for your site.
Documentation testing
We should start with the preparatory phase, testing the documentation. The tester
studies the received documentation (analyzes the defined site functionality, examines
the final layouts of the site and makes a website test plan for further testing).
The main artifacts related to the website testing are analyzed on this stage:
Requirements
Test Plan
Test Cases
Traceability Matrix.
Let’s try to create the checklist for you website functionality testing.
Links testing
Outbound links
Internal links correctness
There are no links leading to the same page
The links that are used to send e-mails to site admins
If there are pages that are not referenced
There are no broken links
You use forms for the interactive communication with your customers. So, the
following points should be checked:
Cookies testing
Cookies are small files that are stored on the user’s computer after visiting your web
page.
HTML/CSS validation
Follow this link, if you want to know more about functional testing
– https://geteasyqa.com/qa/software-testing-types/
Usability testing
Usability testing is aimed to evaluate your web page by testing it with representative
users. It helps to define user ability to learn to operate, prepare inputs for, and
interpret outputs of your site.
Content testing checklist:
Finally, to evaluate the usability of your web portal, just answer these questions:
OS Configuration
Browser Configuration
Database Configuration
Cross-browser website testing methods help to verify the correct work of the site
in different browser configurations: Mozilla Firefox, Google Chrome, Internet
Explorer, and Opera etc.
Database testing is performed to ensure the correct work of your site in different
database configurations: Oracle, DB2, MySql, MSSQL Server, Sybase.
Verify the fonts, page graphics, page alignment can be printed properly
Ensure all pages of your site fit the paper size and the size defined in the
printing option.
Performance testing
Performance testing is aimed to determine how a system performs in terms of
responsiveness and stability under a certain load. Sites must withstand high loads.
Perfomance website testing methods contain:
Useful tools for the different kinds of the perfomance testing: Apache JMeter, HP
LoadRunner, Silk Performer from Micro Focus, WebLOAD, and Gatling.
Want to know more about the best web testing tools for the evaluation your site
perfomance? Go to this link
Security testing
Security testing is performed to verify the information system protects data and
maintains functionality as intended.
You can simulate the malicious source attack to evaluate the security level of your
site (Penetration testing).
Ensuring all detected bugs have indeed been successfully fixed (Re-testing or
Confirmation testing). In a few words, you should run the test cases that
originally detected the bugs again and this time they pass without any
problems.
Ensuring new defects have not appeared after the changes (Regression
testing). Beside the detected bug test cases, it also contains test cases
checking all functionalities of your site.
Mobile-friendly testing
As you have read before some of the website verifications were concerned to the
mobile version of your site. Nowadays, the number of people, who use only mobile
devices for Internet access tends to the stable increasing. That is why it is quite
important to ensure if website site is mobile-friendly.
Beta testing
Beta testing – the final prerelease stage of testing. As a rule, it is done by end-users
and out stuff people.
Beta testing replaces your site in the hands of real users outside of your team to
discover any weak points from the user’s perspective that you would not want to
have in your final, released version of the application.
Now, when we have considered the main phases of the website test process, let’s try
to find the bug und report it with one of the real web testing tools, EasyQA Chrome
Extension.
Ability to report the bug directly from your website or web app
Bug reporting both for logged in users and users without login
Making screenshots
Video recording of the detected bugs
Preparing and sending bug reports in the description form