Case file codoid-6
Mobile App Testing Case Study
grade B, partial Named client without a baselined metric.
Claim ledger
Each row quotes the vendor. A row is a claim, and it counts toward outcome verifiability only when the source states the baseline and the measurement method.
| Kind | Vendor claim (quoted) | Before | After | Baseline | Method |
|---|---|---|---|---|---|
| execution-time | “18 hours of manual work reduced to just 3.5 hours of automation” (grade B, baseline no) | 18 hours manual | 3.5 hours automated | no | no |
| suite-size | “we ensured comprehensive test coverage by creating over 300 test cases.” (grade B, baseline no) | not stated | 300+ test cases | no | no |
- baseline:
- The measured value before the work started, against which a later value is compared. source
Engagement facts
- Client
- Ooredoo stated
- Industry
- Telecommunications stated
- Client type
- not disclosed
- Frameworks
- Appium and Cucumber, SpecFlow, Behave stated
- Languages
- Java stated
- CI tools
- Jenkins stated
- Device or browser clouds
- not disclosed
- Team size
- 2 stated
- Duration in months
- not disclosed
- Start year
- not disclosed
- Publication date
- not disclosed
What this case does not tell you
- Client type
- Device or browser clouds
- Duration in months
- Start year
- Publication date
- A metric with a before value (baseline)
- How or over what period any metric was measured
Source
Mobile App Testing Case Study (codoid.com)
accessed 2026-11-11, verified 2026-11-12
Related pages
- Codoid: vendor profile and score
- Appium: vendors with published cases
- Cucumber, SpecFlow, Behave: vendors with published cases
- DeviQA: QA for mobile app builder
- DeviQA: QA services for Shopify appointment scheduling solution
- All case files
- Framework index
- Vendor ranking
- How cases are graded A, B, C or X
- Corrections and regrades log
Scores and grades describe published evidence as of the verifiedOn date on each item. They do not measure service quality. Verify with the vendor before contracting.