Jubula API Tutorial
UI test automation: the why, the how and the what
Agenda
a few bits of theory
Jubula API hands on
short coffee break
equivalence classes
summary
Testing 101
- Testing is important so that we can gain information about quality and risk
- A balanced test strategy involves tests at different levels
- Prompt feedback is important for continuing development
- Automation can help us with recurring tasks
- So that testers and developers can use their brains for interesting and complex activities
Jubula – the elevator pitch
- Functional tests through the UI
- Swing, SWT/RCP, JavaFX and HTML
- No programming knowledge required*
Jubula – Use
- Regression tests
- Automation of otherwise manual test cases
- Acceptance-level tests (business- or customer-facing)
Jubula – Aims
- Whole team involved in quality and test process
- Use in agile processes
- No capture-replay!
No programming knowledge?
- With the Integrated Test Environment (ITE)
- Code-free approach - Drag&Drop test specification
- Automatic test reporting, screenshot on error
- Error handling, JaCoCo, ALM Integration
- With the Client-API
- Jubula actions callable directly in Java
- Application Under Test (AUT) lifecycle control
- Reporting and error handling driven by e.g. JUnit