Our QA practice at a glance
- 14 testing services
- AI agentic testing
- Manual and automated
- Vendor-agnostic tooling
- Oracle & enterprise specialists
- QA sign-off for every release
Quality engineering and testing that prove your software is ready to release
Manual, automation, API, performance and security testing from one accountable QA/QC Practice. Every engagement runs under one test strategy, one traceability matrix and one reporting standard, and ends with a QA sign-off your management can act on.
One strategy, one standard
Every service runs manually, with automation, or both, under one strategy, one traceability matrix and one reporting standard.
- 6 Functional: manual, smoke and sanity, system integration, regression, user acceptance support, database
- 4 Non-functional: compatibility, usability and accessibility, performance, security
- 3 Technical: API and integration, test automation, AI agentic testing
- 1 Specialist: Oracle EBS, Fusion, APEX and OIC
One practice, 14 services, every kind of testing
Functional testing proves the business rules. Non-functional testing proves the system is fast, safe and usable. Technical services make testing repeatable, and specialists cover Oracle estates. You don't need several vendors.
- Functional (6): Manual, Smoke and sanity, System integration, Regression, User acceptance support, Database
- Non-functional (4): Compatibility, Usability and accessibility, Performance, Security
- Technical (3): API and integration testing, Test automation, AI agentic testing
- Specialist (1): Oracle EBS, Fusion, APEX and OIC testing
Our Testing Services
Manual Testing
Human-led scenario, exploratory and business-rule testing.
Functional Testing
Smoke, sanity, SIT, regression and UAT support.
Database & Compatibility
Oracle and SQL data checks, cross-browser and cross-platform.
Test Automation
Reusable frameworks on Avo Assure, Tosca, OATS and QET Automate.
API & Integration
Contracts, data mapping, retries and error handling.
Performance Testing
Load, stress and scalability with JMeter and LoadRunner.
Security Testing
Access control, sessions and input-injection testing.
Oracle & Enterprise
EBS, Fusion Cloud, APEX and OIC specialists.
AI Agentic Testing
Agents that help us test faster, and testing for the AI agents inside your applications: task success, guardrails, permissions and regression on every model change.
Tell us the challenge. We'll point to the service.
Pick the closest challenge below, or talk to a QA expert about your release.
Where to start
01
We are launching a new web application
We offer functional, performance and security testing.
Start with: test strategy and functional cycle
02
Regression takes too long every release
We offer test automation.
Start with: automation roadmap with ROI
03
We are migrating or upgrading a platform
We offer functional, database, integration and regression testing.
Start with: rapid assessment
04
Will it cope with peak traffic?
We offer performance testing.
Start with: performance health check
05
We must protect customer data
We offer security and database testing.
Start with: security test scope
06
We run Oracle EBS, Fusion or APEX
We offer Oracle and enterprise testing.
Start with: Oracle QA discussion
From first build to business sign-off
Six test levels, each with a named owner, so nothing falls between teams. Developers own unit testing, and your business users own UAT with our support.
Requirements first, risk-based priority and full traceability: gaps are raised before any test is written, the highest-impact rules are tested first, and every requirement is mapped to test cases and defects.
01
Smoke
Is the build stable enough to test?
Owner: QA, every build
02
Sanity
Does this fix or change work?
Owner: QA
03
Unit
Does the code logic work?
Owner: Developers
04
System integration (SIT)
Do modules and systems work together?
Owner: Developers and QA
05
Regression
Did changes break anything?
Owner: QA
06
User acceptance (UAT)
Does the business accept it?
Owner: Business, with QA support
What each service covers
Pick a service to see what we test and how.
Manual testing is where judgement matters. Database testing checks the data layer directly, and compatibility testing confirms the same journeys work on the browsers and devices your users really have.
01
Manual testing
New features, complex rules, usability.
02
Database testing
The data layer, not only the screen.
03
Compatibility testing
Supported list agreed at project start.
Faster releases, lower cost. We recommend automation only for stable, repeated tests, and keep exploratory and fast-changing areas manual. Our automation work starts with an ROI and risk assessment and a roadmap.
01
What we automate
Stable, repeated tests.
Plan, test, prove
Every engagement starts with an agreed QA/QC test strategy, so scope, levels, environments and acceptance criteria are clear before any test runs. Test cycles: smoke, functional, retest, integration and E2E, regression, UAT support.
- 1
Assess
Requirements, risks and environments.
- 2
Plan
Strategy, scope, gates and test data.
- 3
Execute
Smoke to regression, with daily reporting.
- 4
Sign off
Summary report and QA sign-off for the Go/No-Go decision.
Gates, severities and standards
Entry and exit criteria are agreed up front. Severity levels carry response targets, and a daily triage meeting confirms severity and ownership.
Thresholds shown are typical baselines and are agreed per engagement.
01
SIT exit gate
All planned cases run, agreed pass rate, no open Critical or High defects.
02
UAT exit gate
Business sign-off, no open Critical defects.
03
Release gate
QA sign-off and a recorded Go/No-Go.
04
Critical defects
Response: same day.
05
High defects
Response: within 1 working day.
06
Medium and Low defects
Medium within the cycle, Low in a planned release.
What you receive in every engagement.
01
Test Strategy
Scope, levels, environments and acceptance criteria.
02
Test Plan and time plan
Schedule, gates and test data.
03
Test cases and traceability matrix
Every requirement mapped to test cases and defects.
04
Defect log
Severity, owner and status for every defect.
05
Daily status report
Pass rate, coverage and open defects.
What our automation clients report
65%
shorter regression test execution
300%
increase in test coverage
45%
faster release cycles
40%
faster delivery than industry average
Two programmes, two outcomes
Averages across client implementations are shown above; these are two individual programmes.
Enterprise retail transformation
Challenge: Manual testing delayed releases by 3 to 4 weeks.
Solution: Tricentis Tosca for core applications and Avo Assure for mobile.
Results: 70% less regression time (4 weeks to 1.2). 85% increase in defects caught before production. Releases up from 4 to 12 a year.
Oracle EBS modernisation
Challenge: Manual testing could not keep pace with updates across EBS, APEX and Fusion.
Solution: Oracle Application Testing Suite with custom frameworks for EBS modules, APEX and Fusion integrations.
Results: 80% less EBS regression time. 95% coverage across modules and APEX apps. Zero critical defects in production.
Why organisations choose our QA practice
- Multi-platform expertise: Deep skills across Avo Assure, Tosca and Oracle Application Testing Suite.
- Hybrid automation: Codeless speed plus custom scripting.
- Business-focused: ROI analysis, risk assessment and roadmaps.
- Faster time-to-value: Reusable frameworks and results from sprint one.
- Vendor-agnostic: We recommend what fits, not what we sell.
- Knowledge transfer: Training and documentation so you own it.
Frequently Asked Questions
Which testing services do you offer?
Fourteen services across four groups: six functional (manual, smoke and sanity, system integration, regression, user acceptance support and database), four non-functional (compatibility, usability and accessibility, performance and security), three technical (API and integration testing, test automation, and AI agentic testing), and specialist testing for Oracle EBS, Fusion, APEX and Oracle Integration Cloud.
Can you test AI agents and LLM-based applications?
Yes. We test agents against agreed scenario sets for task success, check tool calls and answers for correctness, try prompt injection and data-leakage attacks, and confirm agents stay within their permissions and stop for human approval on high-impact actions. We re-run those checks whenever the model, prompt or tools change. We also use agents ourselves to draft test cases, maintain scripts and triage failures, with QA engineers reviewing the output.
Which standards and frameworks do you work to?
We structure test processes and documentation along ISO/IEC/IEEE 29119 and the ISO/IEC 25010 quality model, test security against OWASP guidance, and test accessibility against WCAG. For AI agents we use the OWASP LLM, Agentic and MCP risk lists and the NIST AI Risk Management Framework as references. Alignment is not certification, and we can confirm what applies to your engagement.
Will you push your own tool on us?
No. We are vendor-agnostic and work across Avo Assure, Tricentis Tosca and Oracle Application Testing Suite. We also offer our own platform, QET Automate, but we recommend whatever fits your technology stack and budget.
Do you automate everything?
No. We recommend automation for stable, repeated tests such as smoke packs, regression suites, data-driven scenarios, API checks and repeatable performance scripts. Exploratory testing, one-off or fast-changing areas and usability judgement stay manual.
How will I know everything is covered?
Let's talk about your quality goals
Tell us the application type, your go-live date and your biggest release risk. We'll propose the right-sized test strategy and plan. Discovery call: application, risks and release plan. Rapid assessment: scope, tools and effort estimate. Proposal: right-sized test strategy and plan.