Mobile Testing Strategy

Existing testing process:

Unit Testing Sprint Testing

(developers) (testers)
Sprint Development/ QA Build

Hotfix
Testing multiple
Hotfix for sprints
prodoction issue(s)
Hotfix Testing Regression Testing
(testers) (developers)

Stage Testing Type Performed by When Tools Testing Platform

1 Unit testing Developers During a sprint Development
environment
2 Manual Sprint testing Manual Testers During a sprint IOS, Android and
Windows devices
2 Automated Sprint testing Automated Testers During a sprint Selenium-based
automated tests
for IOS, Android
and Windows
 devices
3 Regression testing - Manual Testers Before production Jira (test IOS, Android and
Manual release creation, Windows devices
execution,
defect logging
and traceability
tracking)
3 Regression testing - Automated Testers Before production Jira (test Selenium-based
Automated release creation, automated tests
execution, for IOS, Android
defect logging and Windows
and traceability devices
tracking)
4 Hotfix testing - Manual Manual Testers Before releasing a IOS, Android and
hotfix to production Windows devices
release
4 Hotfix testing - Automated Testers Before releasing a Selenium-based
Automated hotfix to production automated tests
release for IOS, Android
and Windows
devices
 Unit Testing Sprint Testing

(developers) (testers)
Sprint Development/ QA Build

Hotfix
Testing multiple
Hotfix for sprints
prodoction issue(s)
Hotfix Testing Regression Testing
(testers) (developers)

Existing Non-Functional Testing

1. Performance testing - Testing the performance of operations e.g. download data, saving, searching, sorting against
set benchmarks.
2. Scalability/ Load testing – Testing to know how many users can be supported while performing specific operations
on the given infrastructure e.g. simultaneous logging-in or synchronization by users
3. Security testing – Testing that all application pages adhere to the set security standards, e.g. to combat cross-site
scripting (XSS) attacks, etc.
4. Usability/ Accessibility testing – Testing that the UI designs and layout conform to the set accessibility standards
e.g. button colors, etc.
5. Compatibility testing – Testing that a version of software is backwardly compatible with the target operating
system, hardware, etc.

Stag Testing Type Improvements

e
1 Unit testing Including BA in
testing at this
stage
2 Manual testing Use of Fiddler
2 Automated testing
3 Regression testing - Including "Day in
Manual life” tests
3 Regression testing -
Automated

Proposed Non-Functional Testing

1. Performance testing - Testing the performance of operations e.g. download data, saving, searching, sorting against
set benchmarks.
2. Scalability/ Load testing – Testing to know how many users can be supported while performing specific operations
on the given infrastructure e.g. simultaneous logging-in or synchronization by users
3. Security testing – Testing that all application pages adhere to the set security standards, e.g. to combat cross-site
scripting (XSS) attacks, etc.
4. Usability/ Accessibility testing – Testing that the UI designs and layout conform to the set accessibility standards
e.g. button colors, etc.
5. Compatibility testing – Testing that a version of software is backwardly compatible with the target operating
system, hardware, etc.
Possible Improvements: Day in life tests for faster testing of common scenario that we can run
Exten

Testing Tools
Current Tools
Possible Improvement: Use of Fiddler