Manual testing services
Manual testing services for web, mobile and desktop software: functional testing of new features, regression testing before every release, exploratory testing, test case design and documentation, cross-browser and cross-device testing, and user acceptance testing support, with dedicated manual QA engineers for your team or testing projects delivered end to end.
Manual testing we do
Functional testing of new features
Each story checked against its requirements and acceptance criteria as soon as it reaches a test environment, through positive, negative and edge cases, with defects filed in Jira, Azure DevOps or Linear with steps, expected and actual results, logs and a screen recording.
Regression testing
A regression suite kept current as the product changes and run before every release, weighted towards the areas a change touches, and a short smoke test after each deployment to production.
Test case design and documentation
Test plans and test cases written from the requirements with boundary values, equivalence classes, decision tables and pairwise combinations, kept in TestRail, Xray, Zephyr, Qase or Azure Test Plans and traced to the requirement each one covers.
Exploratory testing
Time-boxed sessions with a written charter that look for what the test cases did not foresee: unusual data, interrupted flows, slow networks, two tabs open at once, the back button pressed halfway through a payment.
Cross-browser and cross-device testing
Web applications checked in Chrome, Safari, Firefox and Edge on desktop and mobile, on real devices or in BrowserStack, Sauce Labs or TestMu AI (formerly LambdaTest), with the browser and device list taken from your analytics.
Data and integration checks
Results checked where they land: rows queried with SQL, messages in the queue, emails in a test inbox, payments in the provider’s sandbox and records in the CRM or ERP the product feeds.
User acceptance testing support
UAT planned with your business users: scenarios written in their language, test data and environments prepared, sessions run alongside them, and sign-off recorded against each requirement.
Requirements and design review
Stories, specifications and Figma designs read before development starts, with gaps, contradictions and criteria nobody could test raised while they are still cheap to fix.
Localisation testing
Translations checked in context for truncated and untranslated text, date, number and currency formats per locale, plural forms, right-to-left layouts, and the emails and notifications sent in each language.
Hire manual QA engineers
Dedicated manual QA engineers
Manual QA engineers who join your team full time, work in your tools and process, and report to your lead. You interview them; we carry the Ukrainian contract, payroll, invoicing and leave.
Manual testing projects
A defined piece of manual testing with a scope, a fixed plan and a named lead on our side who owns the result and reports progress in your channels.
Ongoing manual testing
Manual testing as a continuing service: the same people every month, a backlog you prioritise, and hours you can see in our portal and on the invoice.
The dedicated team page explains how specialists join your team, and the outsourcing page covers project delivery, take-overs and how we charge.
Who works on your manual testing
Manual QA engineers
Test design, exploratory and regression testing
QA leads
Test strategy, release sign-off and reporting
Test automation engineers
Stable checks moved into automated suites
Business analysts
Requirements and acceptance criteria
How we run manual testing
Testing starts before the code: a QA engineer reads the story and the design, agrees the acceptance criteria with the product owner and writes test cases while the feature is being built. Every defect report carries steps a developer can follow from the first read, the build and environment, logs and a recording, and a severity agreed with you.
Manual time goes where judgement is needed. Checks that stay stable from release to release are handed to automation, so manual testing covers new features, exploratory sessions and the flows that change too often to script. Test cases live in your test management tool, so what the testers know stays with you.
Other software testing services
Test automation
Test automation services: Playwright, Selenium, Cypress and WebdriverIO suites, SDET work, API and visual tests, and CI integration, with dedicated test automation engineers or project delivery.
Mobile app testing
Mobile app testing services: iOS and Android testing on real devices and device farms, Appium, Espresso, XCUITest and Maestro automation, and store release checks, with dedicated mobile QA engineers or project delivery.
API testing
API testing services: REST, GraphQL and gRPC tests in Postman, REST Assured and code, contract testing with Pact, OpenAPI validation and service mocks, with dedicated API test engineers or project delivery.
Performance testing
Performance and load testing services: load, stress and soak tests in k6, JMeter, Gatling and Locust, bottleneck analysis, capacity planning and Core Web Vitals, with dedicated performance engineers or project delivery.
Accessibility testing
Accessibility testing services: WCAG 2.2 audits, screen reader and keyboard testing, axe checks in CI, remediation support and conformance reports, with dedicated accessibility testers or project delivery.
Questions about manual testing
Which industries do your manual QA engineers work in?
Mostly e-commerce and retail, with checkout, payments and promotions tested before each sale; fintech and banking, where every transaction path and limit needs a record of how it was tested; enterprise SaaS and ERP, with many roles, permissions and long business processes; healthcare, with patient data and clinical workflows; media and consumer apps released to many devices; and connected devices, where the app, the web portal and the hardware are tested together.
Do we still need manual testing if our tests are automated?
Yes, for different work. Automation repeats checks someone has already designed; manual and exploratory testing finds the problems nobody designed a check for, judges whether a flow makes sense to a user, and covers features that change too often to script. Most teams run both, and automate the stable regression paths over time.
Can you test without written requirements?
Yes. Testing starts from the product as it is: exploratory sessions map what it does, questions go to your team, and the answers become test cases and a list of open decisions about behaviour, which often becomes the first written specification.
How quickly can manual QA engineers start?
When the right manual QA engineer is available, the start is gated only by your interview and the NDA and IP assignment. Otherwise we run a search, which typically produces candidate profiles within two to three weeks, and nobody starts until you have said yes.
How do we hire manual QA engineers through BigTree108?
Tell us the work, the seniority and the hours you need. We propose one or two people with their profiles, you interview them the way you would interview your own hire, and you sign one agreement with BIG TREE 108 LLC and receive one invoice a month.
Who owns the work they produce?
You do. Every specialist has a signed contract with BigTree108 that assigns all work product to the company, and our agreement with you assigns it onward. Code, designs and documents are delivered into your own repositories and tools, not kept where only we can change them.
Need testing before your next release?
Tell us what the product does, how often you release and where bugs reach your users. You get an answer within one business day: a test plan, candidate profiles, or a scope for a first round of testing.