AGILE MOBILE TESTING WORKSHOP PUNE AGILE CONFERENCE JULIAN HARTY Contact me: [email protected]Rev: 22 Nov 2014 Creative Commons License How to design your mobile apps by Julian Harty is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. http://creativecommons.org/licenses/by-sa/3.0/deed.en_US
Agile Software Development means we want to maximise progress while minimising waste. Delays cause waste, for instance wasted time and efforts; ineffective work causes waste; poor quality causes waste; and bugs cause waste and delay progress, etc.
Mobile apps and the mobile app ecosystem help determine what sorts of testing will be more valuable for the project. This workshop introduces various key concepts and factors related to testing mobile apps effectively. You will have the opportunity to practice testing mobile apps during the workshop to help reinforce your learning and discovery.
We will cover both interactive and automated testing of mobile apps, and find ways to reduce the Time To Useful Feedback (TTUF) so the project team can make more progress while reducing project waste. We will also cover various ways to gather more and better information about the qualities of our mobile codebase and of the quality of the apps-in-use.
Bring your mobile apps and mobile devices and be prepared to get involved in testing!
More details: http://confengine.com/agile-pune-2014/proposal/861/agile-mobile-testing
Conference: http://pune.agileindia.org/
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
AGILE MOBILE TESTING WORKSHOP PUNE AGILE CONFERENCE
Creative Commons License How to design your mobile apps by Julian Harty is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. http://creativecommons.org/licenses/by-sa/3.0/deed.en_US
WHAT IS TESTABILITY? The concept of designing & implementing software so it is easier to test • Testing can be automated • Testing can be interactive
SCALES OF TESTABILITY
There are at least 2 dimensions of Testability: • ease of interfacing • transparency into the state & behaviour of the software being tested.
easy
transparency
inte
rfaci
ng
challenging
trans
pare
nt
opaq
ue
DESIGNING FOR TESTABILITY: HOOKS Programmatic Hooks To connect test automation easily Consider whether to leave them in situ
DESIGNING FOR TESTABILITY: VISIBILITY
“Eyes into the Soul of the machine...” Expose internal data and state
• Makes some checks easier to confirm • e.g. Error recovery mechanisms cleaned up the
app’s internal state Beware:
• Non-test code might start using the data • If so, consider formalising the access in an API
TESTABILITY: LAYERING OF CODE Already covered some aspects in the Segmented Design topic Ideal to be able to automate the testing of each layer or component independently Then testing of the composite software can focus on testing the composite aspects Beware of emergent behaviour
• Test the qualities: non-functional-testing (NFT)
TESTABILITY: SEPARATION OF CONCERNS
Separate generic and platform-specific code Generic code:
• Application logic: What the app does, functionality Platform-specific code:
• User Interface • Threading • Calls to platform-specific APIs
TESTABILITY: ISOLATE COMPLEX CODE
Try encapsulating & isolating complex code • Provide an interface* • Have excellent automated tests exercise it • Warn casual developers (and testers) not to tamper
with it • Now the rest of our code is easier to understand &
manage In parallel consider ways to replace complex code with simpler code
* e.g. See the Facade design pattern
BACK TO “VALUE”
BIG PICTURE
FULL LIFECYCLE COSTS
SPENDING WISELY?
FULL LIFECYCLE COSTS The initial development effort may be dwarfed by maintenance work There are trade-offs between reducing the cost of initial development and the cost of maintenance work Code that costs more to modify is undesirable. Well designed code & good automated tests can reduce the risk and cost of maintenance work.
Beware of premature aging of your app’s codebase!
SPEND MONEY ON TESTING?
WHERE AND WHEN TO
NOVODA Costs 60% more to ‘add’ test automation to Android projects
Who’s willing to sign off on it?
Where and when does the ROI start?
THINGS TO CONSIDER How long do your code bases ‘last’? Who pays for ‘maintenance’? Where is the expertise to maintain the code? Active apps need ongoing nurture & investments even if you’re not changing the functionality
ALTERNATIVES TO TESTING Testing is not the only way to obtain useful feedback. Sometimes it’s not the best way either.
COMPLEMENTING TESTING WITH OTHER INFORMATION SOURCES