Web applications
Functional, end-to-end and cross-browser testing of the journeys your users depend on, with manual and automated accessibility checks.
QA & software testingKnow what you’re shipping.
QA and software testing across web, mobile and APIs. We combine manual and exploratory testing with automation, using the framework and tools that fit your product.
- Regression testing takes days, so releases wait or go out without it.
- Automated tests fail at random, and the team has stopped trusting them.
- The same kinds of defects keep reaching production.
- A mobile release is due and nobody is sure how it behaves on Android and iOS.
- APIs change without tests that would catch a breaking change.
- Nobody can give a clear answer to “is this ready to release?”
WHAT WE TEST
Web, mobile and API testing
HOW WE TEST
Testing matched to the risk
Testing effort goes where a defect would cost you the most. Each engagement uses the mix of testing your product needs, not every type of testing by default.
Manual and exploratory testing. A person works through the product the way your users do, looking for the problems scripts miss.
Regression testing. Confirms that existing features still work after a change.
Smoke and sanity testing. Quick checks that a build is stable enough to test further or to release.
End-to-end testing. Complete user journeys, across the interface, APIs and data.
Cross-browser testing. Consistent behavior across the browsers and screen sizes agreed in scope.
Accessibility testing. Manual and automated checks for barriers that make the product harder to use. Each finding explains where the barrier occurs and why it matters.
Performance testing. JMeter tests that show how key parts of your application behave under load, reported with findings and recommendations.
TEST AUTOMATION
Automation that fits your stack
We automate the stable, high-value journeys that are slow or repetitive to test by hand, and keep people on new features and exploratory work. The tooling is chosen to fit your product.
- Web automation with Playwright or Selenium
- Mobile automation with Appium
- Automated API tests
- Test code in JavaScript or TypeScript, structured with the Page Object Model
- Automated tests running in GitHub Actions or Bitbucket Pipelines
- Stabilizing flaky or unreliable automated tests
- Working with, and improving, your existing test framework where that makes sense
- Selenium to Playwright migration, when it suits the project
What we automate, and what we don’t
Automation pays off for journeys that are important, stable and tested often. Features that change every week, one-off checks and testing that depends on judgment usually stay manual until they settle.
When automation is part of the engagement, tests can be developed within your existing repository or agreed project environment, with ownership and access agreed as part of the scope.
HOW IT WORKS
How a QA engagement works
- 01
Understand the product
Your environments, existing tests, release process and known problem areas.
- 02
Identify the risks
The user journeys, platforms and integrations where a defect would cost the most.
- 03
Agree the coverage
A test plan stating what will be tested, how, on which platforms, and what is out of scope.
- 04
Test and automate
The agreed testing and automation, with findings reported according to the agreed engagement.
- 05
Hand over
A summary of the results, any automation with instructions for running it, and recommended next steps.
WHAT YOU RECEIVE
Deliverables you can act on
- 01A test plan: scope, coverage, platforms and known limitations
- 02Bug reports with steps to reproduce, expected and actual results, severity, environment and supporting evidence
- 03Automated tests, where included, with instructions for running and maintaining them
- 04CI/CD integration for automated tests, where included
- 05A test summary: what was tested, what failed, what remains untested, and what that means for your release
- 06Recommendations for the next most useful improvement
Example bug reportILLUSTRATIVE EXAMPLE · NOT CLIENT WORK
- Severity
- High
- Environment
- Staging, desktop browser
- Steps
- 1. Add an item to the basket. 2. Apply a valid discount code. 3. Change the delivery address at checkout.
- Expected
- The discount stays applied.
- Actual
- The discount is removed without a message, and the total increases.
- Why it matters
- Customers may abandon checkout or dispute the charge.
TOOLS AND TECHNOLOGIES
Tools we work with
The tools follow your product and your existing setup. If your stack needs something else, we agree it during scoping.
WAYS TO START
Start with an audit or a defined piece of work
Scope, pricing and timelines are agreed in writing before work begins.
Forthline’s QA work draws on experience across enterprise web platforms and complex business applications, covering manual testing, automation, regression, API testing and release validation.
You work directly with the person doing the testing, alongside your developers and any existing QA team. Capacity and responsibilities are agreed during scoping.
BEFORE WE START
What we need from you, and what’s outside scope
Testing reduces uncertainty. It does not remove it.
QUESTIONS
QA & software testing questions
What access and materials do you need?
We need access to a test or staging environment, test accounts and test data, mobile test builds where relevant, a product contact, and any existing tests or documentation. Do not send passwords or confidential material through the inquiry form.
What do we receive at handover?
Deliverables include the agreed test plan, reproducible bug reports, a test summary with known limitations and recommendations. Where automation is included, you receive the tests with instructions for running and maintaining them. Repository ownership and access are agreed as part of the scope.
What does a QA audit include?
A QA audit is a paid, scoped review of your current testing. It looks at what is covered, where the risks and gaps are, and how well any existing automation works. You receive actionable findings and recommendations. The scope is agreed in writing before the audit begins.
Do you test mobile apps as well as web apps?
Yes. We test web applications and mobile applications on Android and iOS, including native, hybrid and React Native apps. Mobile testing can be manual, automated with Appium, or both.
Which testing tools do you use?
The tools depend on your product and your existing setup. We work with Playwright, Selenium, Appium and JMeter, in JavaScript and TypeScript, with CI/CD in GitHub Actions or Bitbucket Pipelines.
Can you work with our existing test framework?
Yes, where it makes sense. We can extend and improve your existing setup rather than replace it. If moving from Selenium to Playwright suits the project, we can plan and carry out the migration.
Is test automation worth it while our product is still changing?
Often, for the parts that are stable. Critical journeys that are tested frequently are usually worth automating early. Features that change every week are usually better tested manually until they settle.
Do you work with our developers and in-house team?
Yes. We work directly with your developers and any existing QA team. Capacity and responsibilities are agreed during scoping.
Do you provide accessibility and performance testing?
Yes. Accessibility testing includes manual and automated checks. Performance testing uses JMeter. Both produce findings and recommendations. Neither is a certification or a guarantee of results.
Is security testing included?
Security and penetration testing are outside the normal QA scope.
How is this different from the AI-built app audit?
QA and software testing focuses on how your product behaves and how it is tested. The AI-built app audit reviews an AI-generated application more broadly, including code, architecture and deployment, before repairs are scoped.
How is a QA engagement priced?
Pricing depends on scope, platforms and complexity. You receive a written scope and proposal before any work begins.
CONNECTED SERVICES
THE NEXT STEP
Something to build.
Something to make better.
Tell us where your business is today and what you want to improve. We’ll help you find a practical next step.
Speak directly with the person planning your engagement.