Mobile Testing

1. Testerworld.com
Mobile Testing in Isolation
Sriram Angajala

2. Mobile testing
• Mobile Native apps
• Dependencies on external apis

3. Mobile testing
• Advantages of using apis in mobile app
– Dynamic Data
– Update content with out app store submission
– Perform multiple operations taking to different 3rd
parties
– Single Sign on
– Save space in Mobile app

4. Why apis are used in Apps
• Location
• Post code
• Bank Sort code
• Account login
• Ticket Booking
• Banking
• Etc…….

5. Testing mobile apps
• Front end testing
– Functional
– Usability
• Other tests
– Error handling
– Security
– Performance
– Multiple Data Combinations
– End to end tests

6. Problems?
• Cannot develop mobile apps with out apis
• Cost of using real services(10p per vehicle)
• Downtimes
• Cannot emulate error scenarios
• Depend on real data is not always good
• Bugs in 3rd party

7. Advantages
• Test Driven Development
• Quick POCs
• Generate Error Scenarios
• Test Live Environments
• Manipulate Data
• Save Costs
• Faster response
• Concentrate testing on Front End only
• Effective testing

8. How to do it
• Create a Mock Server(what is mock and
stub…)
– Stubbing: mostly a placeholder without real functionality
– Mocking: basic functionality required for a specific testing or
development purpose
– Simulation: complete functionality for testing or development
purposes
– Virtualization: imulation that is deployed into an operational,
manageable and controllable environment

9. What to mock

10. Mocking During Development
Save Dev time

11. Mocking For Functional Tests(More
test combinations)

12. Mocking For External Components-
Isolated testing

13. Mocking For Non-Functional Testing
• Mocks can respond faster - Saving time during
testing due to lower overhead, also provides
more load on the component due to less idle
time.
• Mocking 3rd party components - Saving on costs
for using external APIs in load tests, or replacing
unavailble external dependencies.
• Simulating various response times - Simulating a
greater range of possible response times and
outages is a good way to see how your
component handles them.

14. Mocking Best Practices
• When creating and using mocks as in the practices
described above, here a couple of things to consider:
• Make the mock 100% technically equivalent
• Use recording tools or log files to create complex mock
• Use mocks to create negative tests
• Use mocks to enable continuous testing
• Create your mock so that it can forward requests
– Putting It All Together
• External dependecies
• Isolated development
• Early functional testing
• Customer evaluation
• Avoiding API dependencies

15. Tools Evaluated
– Wiremock
– Apiary
– Mockable.IO
– Soap UI
– Charles

16. Breakdown of tools
Wiremock
– How it works
• Java application is created at backend
• Deployed as normal web application and have json files fulfilling requests
• End points diverted to mock services
– Pros
• Emulates any test condition
• Handles multiple requests on single URL (POST requests)
• Full control over responses
– Cons
• Complex programming
• Maintenance overheads

17. Breakdown of tools cont…
Soap UI
– How it works
• Responses as per preconfigured JSON files
• Uses groovy scripts to programme(light weight)
– Pros
• Simple to mock environment
• Handles multiple requests (GET requests)
• Usable for all static responses & happy paths
• No maintenance overhead
– Cons
• Running in Jenkins server
• Running from command line like a real server is not easy

18. Breakdown of tools cont…
Apiary & Mockable.IO
– How it works
• Free online tool
• Blueprint syntax (Apiary only)
• Responses as per preconfigured JSON files
– Pros
• Simple to mock environment
• Handles multiple requests (GET requests)
• Usable for all static responses & happy paths
• No maintenance overhead
• Full documentation available (Apiary only)
– Cons
• Unable to manipulate responses
• Payload cannot be validated
• Negative conditions not testable

19. Summary
Challenges of mocking services
• Time effective to build
• 3rd party maintenance / changes communications
• Maintenance of mock services in line with 3rd party
service upgrades and changes

20. Summary
Benefits of mocking services
• Independent frontend
testing
• Rapid test completion
• Faster feedback
• More combinations
testable
• Isolated testing
• Error scenario simulation
• More controlled services
• Mock services support TDD
• Supports POC on all
platforms
• Faster = Saved effort =
Saved Time = Saved £££

21. Demo
• Post code search - cost
• Paypal payment - error
• Non available url - POCs
• Data manpluation – order history

22. Setup
• Junit
• Start server
• Apis
• Charles redirection
• Pause and react