Software quality and accessibility
Functional software testing
Functional software testing checks that your application does what it is supposed to, scenario by scenario, and reports each defect with the steps, evidence and severity a developer needs to fix it.
What does functional software testing from ODOOVATIONS include, and what does it cost?
Coverage matrix, reproducible defects, evidence and one retest cycle. There are three packages, from USD 500 (≈ PKR 138,300), one time, each with a stated scope. Prices are launch offers in US dollars before taxes; a written scope confirms the final price before any work starts.
Is this the right purchase?
The problem it solves
Releases go out after a quick click-through, and customers find the bugs.
Who it is for
Teams releasing web or mobile software without dedicated testers.
When it is the wrong first step
If requirements are unwritten, testers will guess; write acceptance criteria first, or let us draft them as part of the scope.
What is included, and what is not
We deliver
- A coverage matrix
- Test cases up to the tier’s count
- Reproducible defect reports
- One retest cycle
You provide
- A stable test environment
- Requirements or user stories
- Test accounts and data
- Keeps the environment stable during testing
- Fixes defects
- Decides on release
Priced separately
A test case is a meaningful behaviour, not an arbitrary assertion. Device farms and specialist audits are separate.
Packages
20 test cases
USD 500
≈ PKR 138,300
one time
- 20 test cases
- 1 environment
60 test cases
USD 1,200
≈ PKR 331,900
one time
- 60 test cases
- 2 environments
120 test cases
USD 2,500
≈ PKR 691,500
one time
- 120 test cases
- 3 environments
Planning: 1 / 2 / 3 weeks after a stable test environment is available. Proposed planning range, confirmed after inputs and complexity review; not an advertised market average or an outcome guarantee.
Rupee figures are indicative, converted at 1 USD = PKR 276.6 (rate of 30 October 2026). Prices are set in US dollars; a fixed PKR quotation is given in writing.
How the work runs
- Step 1
Plan
What to cover, in which environments.
- Step 2
Execute
Run each case and record evidence.
- Step 3
Report
Passed, failed and blocked separately.
- Step 4
Retest
Once, after your fixes.
When it is done: Done when all cases are run, defects reported and the retest completed. The release decision is yours.
What the work looks like
| Field | Value |
|---|---|
| Title | Discount applied twice when coupon re-entered |
| Steps | Add item → apply SAVE10 → remove → apply again |
| Expected / actual | 10% off / 19% off |
| Severity | High |
Sample from an owned demo application. Not a client defect. More samples in the ODOOVATIONS Release Lab.
What we measure
- Cases passed, failed and blocked
- Defects found by severity
- Defects reopened after retest
Questions buyers ask
One meaningful behaviour checked, not an arbitrary click.
Talk to us about functional software testing
Tell us what you need in a few lines. We reply with questions or a written scope; nothing is charged by asking.

