Manual Testing

Some things are just better tested manually...

Manual testing

Manual testing is a process that does not use any automated tool or any script. To ensure the completeness of testing, we use the test plan, test cases or test scenarios on the software.

Manual testing also includes exploratory testing. This is running adhoc, pre-scripted tests/checks across a product or in a focused area of the product. This is often mentioned in a session-based Test Charter.

Use cases for manual testing

  • When a site is responsive, we need to test how visual elements of the site respond to different screen sizes and devices, both landscape and portrait views.
  • Company logo/branding is not lost.
  • Navigation is not lost, it's clear and well organised.
  • Content is consistent on all platforms.
  • All pages are accessible. We use tools like Link Checker to explore any dead or broken links.
  • Style and colours are not lost.
  • Images are clear.
  • Site does not take too long to load on different platforms.

Our approach

  • Prepare the test plan: a high level plan noting the type of testing that will be done, number of cycles, and the testers who will be involved browsers and devices that will be tested.
  • Prepare test cases and a checklist: a document listing the steps to test and expected results
  • Execute the test cases: tester executes the test cases on different platforms.
  • Log defects: tester logs defects in JIRA and assigns it to an engineer.
  • Prepare a test report: tester sends daily test report to the project team highlighting the areas and browsers covered, and also highlighting the defects reported or any other issues/concerns.

Browsers and devices tested

We have a default list of desktop browsers and devices where we perform our manual testing.