Skip to content

Manual testing and exploratory testing

SDCLabs manual and exploratory testing puts experienced testers on your product to find what scripts miss: confusing flows, accessibility gaps and bugs between features. Senior QA engineers run charter-based sessions and release passes, with AI assistance for test ideas and reports.

Overview

What is Manual testing and exploratory testing?

Automated tests check what you already expect. Exploratory testing looks for what you did not expect: a flow that confuses new users, a form that breaks with a screen reader, a payment that fails when two tabs are open. A skilled tester learns the product, designs tests on the fly and follows the evidence, which is why exploration finds a different class of bugs than any suite.

We run structured sessions, not random clicking. Each session has a charter, a time box and notes you can read, and every serious finding comes with clear steps to reproduce. AI tools help us draft charters, generate test data and turn session notes into tidy bug reports; senior testers do the testing and the judgment. Findings that should never come back go to automation, written by the team that created Codeception and CodeceptJS.

What you get

What do you get from Manual testing and exploratory testing?

Bugs found before your users find them

Defects in real user journeys, edge cases and feature interactions, reported with steps, environment and evidence.

A release you can sign off

A focused pass before each release, with a clear go or no-go view of the risks that remain.

Feedback on how the product feels

Usability and accessibility issues that make users hesitate, drop off or call support, ranked by impact.

A smarter automation backlog

A list of the checks worth automating next, based on what exploration actually found.

Scope

What do we cover?

Exploratory testing sessions

Time-boxed sessions guided by charters, with session notes, coverage and findings recorded for each one.

Usability testing

Walkthroughs of key journeys from a new user's point of view, flagging unclear copy, dead ends and extra steps.

Accessibility checks

Keyboard navigation, screen readers, color contrast and form labels checked against WCAG success criteria.

Regression passes

Manual passes over the areas automation does not cover yet, focused on what the latest changes could affect.

Release and acceptance testing

Pre-release checks on staging, smoke tests after deploy and support for user acceptance testing.

Cross-browser and device testing

Your product on the browsers, operating systems and real devices your users have.

Challenges

Which challenges do we solve?

Automated tests pass, users still report bugs

We explore the gaps between scripted checks: unusual inputs, interrupted flows and features used together, and report what we find with reproducible steps.

Every release is a gamble

We run a risk-based release pass on what changed and what it touches, so you ship with known risks instead of hopes.

Nobody has checked accessibility

We test with keyboard, screen readers and automated scanners, and report each issue against the WCAG criterion it fails, with a suggested fix.

Manual testing is slow and undocumented

Charters, time boxes and session notes make manual work visible and repeatable, and AI-assisted reporting keeps the paperwork short.

The team cannot decide what to automate

We use exploration results to pick the checks that pay off as automated tests and hand them over as a prioritized list.

Why SDCLabs

Why choose SDCLabs, and what are the benefits?

Testers who also automate

We are the founders of Codeception and CodeceptJS, so we know where manual testing adds value and where a script does the job better.

Structured exploration

Charter-based sessions with notes and coverage, so you see what was tested, not only what was found.

AI-assisted, human-tested

AI drafts charters, test data and reports; experienced testers explore, judge severity and decide what matters.

Bug reports developers like

Clear steps, expected and actual results, environment details, screenshots or recordings: ready to fix.

Flexible capacity

Add testers for a release or keep them as part of your team. Engagement starts in 1 to 2 weeks.

Deliverables

What is included?

Process

What is our process?

  1. 01

    Learn the product and its risks

    We walk through the product with your team, map critical journeys and note recent changes and known problem areas.

  2. 02

    Write charters

    Each session gets a mission, a scope and a time box, drafted with AI help and reviewed by a senior tester.

  3. 03

    Explore and record

    Testers run the sessions, follow anything suspicious and record notes, coverage and evidence as they go.

  4. 04

    Report and debrief

    We file clear bug reports in your tracker and review the findings with your team, ranked by impact.

  5. 05

    Feed automation and repeat

    Findings worth guarding become automated tests, and the next release gets a pass focused on what changed.

Tools and tech

Which tools and technologies do we use?

Test management and tracking

  • TestRail
  • Xray
  • Zephyr
  • Jira

Accessibility

  • axe DevTools
  • WAVE
  • Lighthouse
  • NVDA
  • VoiceOver

Browsers and devices

  • BrowserStack
  • Sauce Labs
  • Chrome DevTools
  • Android Emulator
  • iOS Simulator

Session support

  • Postman
  • Charles Proxy
  • Proxyman

Automation handover

  • CodeceptJS
  • Codeception
  • Playwright

From the blog

What is the state of manual testing and exploratory testing in 2026?

Frequently asked questions

What is exploratory testing?

Exploratory testing is testing where the tester learns the product, designs tests and runs them at the same time, guided by a charter instead of a fixed script. It finds bugs that scripted tests do not anticipate.

Is manual testing still needed if we have test automation?

Yes. Automation is best at repeating known checks quickly; manual and exploratory testing finds new problems, usability issues and accessibility gaps. The two work best together, with exploration feeding the automation backlog.

What is a test charter?

A test charter is a short mission for an exploratory session: what to explore, with which resources, and what information to look for. It keeps sessions focused and makes the results easy to review.

Do you test accessibility?

Yes. We check keyboard use, screen readers, contrast and forms, and report each issue against the WCAG success criterion it fails.

Can you test a release before it goes live?

Yes. We run a release pass on staging focused on what changed, a smoke test after deploy, and give you a clear summary of the remaining risks.

Get a fresh pair of expert eyes on your product

Tell us what you are about to release or what keeps breaking. Write to ask@sdclabs.com; the first response comes within 2 hours on business days.

Related services