Accessnavigator logo
Accessnavigator
Manual Testing Mentorship

About.

Accessnavigator is a mentorship practice built around one idea — that manual software testing is a craft, not a checklist. We work with people who want to understand it properly.

Mentor working through a structured test plan at a desk, focused environment

Testing is specific work


01

Founded in 2023, Accessnavigator grew from a straightforward observation: most testing resources teach syntax and skip judgment. Knowing how to write a test case is not the same as knowing which cases matter.

02

We run online mentorship sessions that follow a client's actual work — not a generic curriculum. If you're testing a payment flow, that's what we examine. Real context produces useful feedback.

03

Progress here is measured in decisions, not certificates. The goal is a mentee who can look at an unfamiliar system and know where to start — and why.

Mentorship format

1-on-1

Every session is private and structured around the mentee's current project or role.

Delivery

Online

Clients from any region, consistent session quality regardless of time zone.

Focus area

Manual QA

Test planning, exploratory testing, defect reporting, and validation strategy.

The people behind the sessions

Practitioners, not presenters

Portrait of Dorian Kessler, senior testing mentor

Dorian Kessler

Senior Mentor — Test Strategy

Dorian spent eleven years in QA across fintech and logistics software before moving into mentorship full-time. He's particularly focused on boundary analysis and how teams decide what not to test.

Currently accepting new mentees
Portrait of Callum Osei, testing mentor specialising in defect lifecycle

Callum Osei

Mentor — Defect Lifecycle & Reporting

Callum's background is in enterprise CRM testing where defect communication was as important as defect discovery. He works with mentees on writing reports that developers actually read.

Available for new engagements

How we work

Three things that don't change

Continuity over cohorts

We don't run batches or intakes. Each mentee has a continuous relationship with one mentor — same person, same context, session after session.

Specificity as a standard

Generic advice is easy to give and hard to use. Every recommendation we make is tied to something the mentee is actually working on — a test plan, a bug report, a conversation with a developer.

Honest progress tracking

We tell mentees when something isn't working. That includes our own approach. If a session format isn't producing useful outcomes, we change it — without waiting to be asked.

Close-up of annotated test documentation on a workbench, practical testing environment
Working through real test artefacts, not hypothetical examples
Testing session in progress, screen showing structured test case review
Each session builds on the one before it