In this case study you will see different approaches for applying a Technical Testing approach to a desktop Java Application. Over the course of the case study we use technical knowledge of Java, and apply it to a MORIM Technical Testing Model: Modelling, Observation, Reflection, Interrogation and Manipulation. As a result we will explore different ways of observing and interrogating the running application. As we do so we will expand our model of the application and identify ways of manipulating the application. For more information on the Case Study in video form, visit compendiumdev.co.uk/page/casestudyjavadesktop

1. Case Study: Java App Testing
Alan Richardson
JavaForTesters.com
EvilTester.com
SeleniumSimplified.com
CompendiumDev.co.uk
compendiumdev.co.uk/page/casestudyjavadesktop

2. Case Study: Java App Testing
● House of Test Data Generator
● Written by HouseOfTest.se
● Evil Tester Scratchpad
http://blog.eviltester.com/2016/02/lessons-learned-testing-house-of-test.html

3. Run Java App
● Double click to run
● java -jar app.jar

4. Decompile to view source?
● http://jd.benow.ca/
● How to explore via test specific code?

5. Add .jar to project to view source
● Create Project
● Open Module Settings
● Add Library : Java

6. Run Class in Java App
● java -cp app.jar org.app.MainClassToRun
java -cp crappy_little_datagenerator_v_1.0.jar
yhtest.tool.controller.TestTool

7. Application Model
GUI
CLI
DataGeneration

8. A Model of Testing
● Modelling
● Observation
● Reflection
● Intent
● Manipulation

9. A Model of Technical Testing
● Modelling
● Observation
● Reflection
● Interrogation
● Manipulation
● Intent

10. Summary

11. Testing Summary
● Test approach driven by technical
understanding
– Observe, Interrogate, Manipulate: All Stack Levels
● Riskier?
– No test approach mitigates all risk
● Harder?
– Technical knowledge required

12. Go to the source
● Hard to protect source of applications now
– e.g. Ruby, Android, Java, HTML, JavaScript, etc.
● Decompile
● Decompile and run from IDE
● Automated at the source
– e.g. JUnit, JavaScript console

13. Java Summary
● Double click '.jar' (Hidden console)
●
java -jar jarname.jar (visible console)
● java -cp jarname.jar package.ClassName

14. Learn More About Technical Testing
@
● EvilTester.com
● JavaForTesters.com
● SeleniumSimplified.com
● CompendiumDev.co.uk
● Alan Richardson, @EvilTester
Books Online Training
CompendiumDev.co.uk/page/books CompendiumDev.co.uk/page/online_training