Website Testing 2017-10-16T12:55:53+00:00

website-testing-cross-browser-icon Website Testing

website-testing-cross-browser-icon Your next step – Contact Me

Contact Me

Contact me for freelance Website Testing & QA Services

I'm a freelance Website Tester, based in the London area.
Contact Me

My other testing services: iOS App Testing / Android App Testing

website-testing-cross-browser-icon How a Website Testing Project works

In some cases, a client will know exactly what they want from a website testing project and this will help to define the project from the start. On the other hand, a client may come to me and say ‘test my website’, in which case, further information is required to find out the required scope of the testing project.

In order to define the project, we can discuss requirements via email, phone call, Skype call, Slack chat, or, for a longer-term project in the London area, an onsite meeting.

The aim here is to agree what the testing should focus on and on what browsers and devices the testing should be carried out on.

Other factors to consider are where issues are to be raised and how test results are reported.

Also, scheduling of the testing date(s) is key and you can view my Bookings Calendar to check availability.

At this stage, the Website is tested, according to the Project definitions and the browser and device list agreed on. This will include all the testing types agreed on, plus the appropriate amount of Exploratory Testing to unearth bugs which may otherwise be left lurking in the website.

Issues are raised as they are found, in the method agreed: this could be in your own issue tracker – such as JIRA, DoneDone, RedMine etc – or within an Excel document, or perhaps a Google doc, or, where applicable, within my own hosted JIRA issue tracker.

Test results can be reported in many ways and the method used will often depend on the length of the test project. For example, a short half-day test could be reported on in an email that summarises all the results, whereas a longer test could be reported on in a full Test Summary Report.

A Test Summary Report includes sections such as Overview, Main Findings, Gap Analysis, Deliverables, Testing Types Performed, Test Browsers & Devices, Bugs Statistics and Summary of Main Bugs.

At this stage, we can discuss if any further testing is required.

This may include further focussed testing, retesting of fixed issues, regression testing after changes or any other type of testing.

Other testing types I perform: iOS App Testing, Android App Testing

Testing Stages

During the Development Stage, I can work with the Developers, Designers and Project Managers to effectively design and execute tests at the most cost-effective time.

    * Working with Developers, Designers, Project Managers.
    * Testing can be focussed on the most important functionality or can be generalised, to cover all areas of the website.
    * Testing can be added in phases, as new functionality is developed and available for testing e.g. on a sprint/iteration/release basis.
    * Most cost-effective time for testing.
During the Beta Stage, bugs can be found which otherwise would have been released to the public.

    * Find Bugs before website is released to the public.
    * All functionality can be tested at this stage, and emphasis can be given to certain functionality depending on priorities.
    * Still a cost-effective time for testing.
At the Release Stage, testing can be done at and around the go-live stage, to try and find any last-minute issues, and also when new features are added to the site, or when the site is enhanced with new technology, new features etc.

    * Testing at and around the go-live stage, to find any last-minute issues
    * Testing new Features and Functionality
    * Finding Bugs in enhanced websites

Some of the Website Testing Projects I’ve worked on

Desktop Platforms and Browsers I have tested websites on

iOS Devices I have tested on (more info)

Android & Other Devices I have tested on (more info)

Website Sectors I have tested in

  • Crowdfunding – Property, PropTech
  • Retail
  • Ecommerce
  • Diner, Restaurant
  • Architecture, Building, Property
  • Drinks Supplies
  • Auction
  • Telecoms
  • Newspaper
  • Video
  • Multimedia
  • Web Comics
  • Online Store
  • Auction (Property)
  • Fashion, Clothes
  • Hair & Beauty Products
  • Soft Drinks
  • Infographics
  • Management Consultancy
  • Local Government Information
  • Events
  • Conferences
  • Architecture
  • Digital Agencies
  • Cars
  • Sports
  • Vehicle Financing
  • Games
  • B2B Services
  • Online Storytelling
  • Language Learning
  • Transport Information
  • Finance
  • Insurance, Insurance Quotes
  • Charity Funding
  • Fitness Products
  • Pharmaceuticals
  • Engineering
  • Energy

Website Testing Project in Detail – Home Furniture Range

text-logo
  • Website Testing of the Home Furniture Range ecommerce retail website.
  • Working to a specific customer brief to test the sales process, from Google search results through to the website, including test orders and payments.
  • Testing performed included Functional Testing, End-to-End Testing, Cross-Browser Testing, Mobile Device Testing plus providing feedback on UX/UI/Usability and SEO.
  • Tested across all the main browsers on Windows and Mac platforms and on mobile devices (iOS and Android)
  • All issues tracked in my own JIRA issue tracker.
  • After the testing phase, HFR IT team began fixing the issues and I carried out some retesting, to check and close the issues in JIRA.

Website Testing related activities & technologies

Having some knowledge of web technologies such as HTML/HTML5, CSS and PHP can be very useful when testing websites, as it gives the tester an insight into how the website works and functions. I have some knowledge in these web technologies and this has proved useful during testing, especially when combined with tools such as Web Developer Tools in Firefox, enabling me to give detailed feedback when reporting bugs.
Creating detailed Bug Reports is an essential part of the testing process, allowing the developers to reproduce the bug and then attempt to fix it.
Sometimes a bug is best shown via a screenshot or a video – or both – especially when a text description doesn’t seem sufficient or would be too complicated to be useful. There are several different methods for getting screenshots and videos when testing websites. These include using the built-in screenshot tools on the computer or device you’re testing on and also software and tools specifically developed to capture screenshots and videos of the computer in use, such as Camtasia and Jing.
Maintaining and tracking issues in an Issue Tracking System is a vital way of managing the Test Process, so that progress in fixing issues can be monitored and updated.
Different projects require the use of different Issue Tracking Systems and methods. So far, I’ve used the specialist Jira system, the Redmine system, the DoneDone issue-tracking system, the issue-tracking features in the Codebase system, plus also using Excel spreadsheets and Google docs.
Gherkin provides a scripted way of describing how software works, without detailing how it is implemented. It’s written in a human-readable format and can be understood (and written) by those on the business side of a project plus the developers and testers. Gherkin can be used to provide both documentation and also can be used for automating testing, such as when used with Cucumber. I have so far used Gherkin when performing manual testing, as it’s an ideal way for developers to document how a feature is expected to work – and for a tester to then test against it.
Google Analytics can be used to obtain detailed statistics and analysis of website usage. These stats can then be analysed to find out key information – such as which browsers access the site the most, which operating systems access the site the most, which mobile devices and O/S are used to access the site. This information can then be used to prioritise the testing done on the website, based on usage. For instance, if the site is mainly accessed by iPad users, then priority needs to be given to testing the website on the iPad range of devices.
Sites such as BrowserStack.com and Sauce Labs can be used to increase the range of testing possibilities when testing websites. For instance, you can choose various devices and browsers to test on and then see how the website looks and acts in them. This can be useful for testing when you don’t have access to a certain device, type of hardware or operating system. I have used both BrowserStack.com and Sauce Labs and can recommend them.
There are many different types of websites, including Web Apps, Facebook Apps, HTML5 websites, CMS websites, Online Stores, Blogs and many more. I have tested across an extensive range of websites, including all of these and many more, even testing Emails where email content is linked to websites.
As more websites and web apps feature Facebook login and integration, the lines are starting to blur between the website/web app and the Facebook App. I’ve now worked on several Facebook app testing projects and each one has differed in the level of Facebook integration. Some have just used the Facebook login API, whereas some have been fully blown Facebook apps, sometimes ‘hiding’ in a website wrapper to appear like a website rather than a Facebook app. These Facebook app projects have their own complexities, such as Facebook user management and creation, Facebook photo and video library management etc.
Content Management Systems (CMS) are used to create many different types of websites, ranging from the more usual blogs to fully blown websites, some with an online store. I have tested websites created with all sorts of CMS, including WordPress, MS SharePoint and – most often – a custom CMS created by the website developers. Any CMS consists of both a back-end, admin system where the site content is added and maintained, plus also a front-end that the website user actually sees. CMS Testing, depending on client requirements, can consist of testing both the back-end and the front-end, though most often consists of testing the front-end only. Testing the back-end requires additional tests on areas such as access control, account maintenance, user management, media upload and management, image and video testing, plus some basic security testing. I have also tested several eCommerce sites, which use the Magento platform, which is an eCommerce CMS.
Testing tools help the testing process in many different ways and there are many different testing tools. Charles Proxy is a good example, which I sometimes use to test bandwidth throttling for apps and websites, to see how the product handles network connections with low bandwidth and varying stability and reliability. Other tools I’ve used include Postman, for API testing.

Featured Posts From The Blog

  • mdqcc

Mobile Device Quick Comparison Chart

Update - October 2017 - I've now added the latest devices to the list - iPhone 8, iPhone 8 Plus, iPhone X, Samsung Galaxy Note 8, Google Pixel 2, Google Pixel 2 XL Update - [...]

  • Sonos&Dot

Adding voice control to Sonos speakers

Later this year, it looks like Sonos will be announcing/releasing their own smart speaker - a Sonos Play speaker with Alexa voice control built in and probably compatibility with the other systems such as Google [...]

  • iPhoneX

News from Apple Special Event, 12 September 2017

The first ever event at the Steve Jobs Theatre was Apple's big set of announcements for the latest iPhones and other Apple gear. The main items were, as usual, saved until the end of the [...]

  • iOS-11-WWDC

iOS 11 info

Files app is brand new to iOS 11. Can view all files on the device, on your other iOS devices, in iCloud Drive and across other services including Dropbox, Box, OneDrive, Google Drive etc. On [...]