Manual and exploratory testing
Automation comes first in our work, but some checks are better done by a person: a new feature that is still changing, a release on an unusual device, a flow that needs judgement. We cover those by hand and automate them once they settle.
$ ask about thiswhat you get
- Exploratory testing of new features, with findings reported as reproducible defects.
- Acceptance and regression passes before a release, where no automated coverage exists yet.
- Compatibility checks across browsers, devices and operating system versions.
- System integration testing across connected systems, APIs, message queues and databases.
- A list of the manual checks that should be automated next, ordered by how often they are repeated.
how we do it
Manual testing is planned, not improvised: we agree the scope, record what was covered and report in your tracker.
Every repeated manual check is a candidate for automation. We say which ones are worth it and which are not.
- Jira
- Azure DevOps
- Postman
- SQL
- BrowserStack
related services
describe › playwright
Test automation with Playwright
SDET work: end-to-end, API and visual regression suites in Playwright and TypeScript, engineered like production code.
describe › ci/cd
CI/CD test integration
Test stages in GitLab, Azure DevOps and GitHub Actions that run after every deployment, plus nightly runs.