Jagger release 2.0
Download as PPTX, PDF0 likes254 views
This document outlines the goals of the Jagger 2.0 release which aims to decrease the barrier to entry and simplify the framework. It highlights new features such as using Java for test scripting, improved documentation, and introducing Jagger as a Service. The document also provides live demos of Jagger's features including Docker, test scripting, results validation, and the JaaS API. Finally, it lists several potential use cases for Jagger such as API testing, performance testing with custom protocols, and integrating with continuous integration systems.
Jagger release 2.0
- 1. 1 Public1 Public Jagger release 2.0
- 2. 2 Public • Why Jagger 2.0 • Our goals for the release • New features • When Jagger can be useful 2 Agenda
- 3. 3 Public Section 1: Why we decided to build Jagger 2.0
- 4. 4 Public What are the advantages of Jagger Older versions: • High performance • Wide possibilities for customization. When you know how • Good reporting capabilities • Good monitoring capabilities • Continuous integration readiness
- 5. 5 Public What drawbacks did instrument have • High barrier to entry • Complex test scripting • Complex tool installation • Poor documentation
- 6. 6 Public Section 2: Our goal for the 2.0 release
- 7. 7 Public Jagger 2.0 release goal • Decrease barrier to entry • Simplify framework installation • Use java language for test scripting • Improve HTTP/HTTPS support • Create new documentation • Introduce Jagger as a Service (JaaS) • Test execution control via REST API • Test results access via REST API
- 8. 8 Public Section 3: Jagger features live demo
- 9. 9 Public Jagger features live demo • Docker • Test scripting • Archetype • Results validation • HTTP support • Decision making • Documentation
- 10. 10 Public JaaS live demo • Swagger UI for API • Test execution via JaaS • Documentation
- 11. 11 Public Section 4: Use cases
- 12. 12 Public Use cases • API level testing • HTTP support • Responses validation • High performance and distributed mode • Simple test development process • Performance via custom protocols • Customization of load generation and reporting components • Generic interfaces • Building CI • Reporting • Decision making • CI readiness
- 13. 13 Public