¶ Successful Test Automation with Open-Source Methods
¶ Workshop Contents
Introductory Presentation (PDF)
Full Presentation (PDF) as shown in workshop
Target Audience: Developers, Testers/QA, Project Managers, and other technical stakeholders interested in test automation.
Duration: 2 hours (including practical exercises). Same content planned for both timeslots on Thursday and Friday. See agenda on Arena2036.de
Workshop Objective: To provide a hands-on approach to test automation, particularly for the level of end-to-end API integration tests and to a lesser extent UI tests, leveraging open-source methods and tools. The workshop is based on a planned Tractus-X Release Guideline for test automation, with the widely used Cucumber behavior-driven development framework. The easy to learn Gherkin syntax to describe Cucumber test scenarios provides a shared language for business/design, developer and tester roles to create test cases together.
You will get to experience the practical implementation of an end-to-end test cycle, from user story to test results.
Coaches:
Harald Zimmer, doubleSlash Net-Business GmbH. Test Management for Catena-X e.V.
Fabian Kock, doubleSlash Net-Business GmbH
Note: To participate in the hands-on coding exercise part of the workshop, please bring a notebook and pre-install some applicable tools:
- Your favorite IDE such as IntelliJ IDEA (free Community Edition is sufficient) or Visual Studio Code (free)
- Cucumber Plugin for the IDE
- Java SDK
Alternatively of course you can just follow the presentation, demo and discussion, and work with the provided materials and demo repository later.
¶ Demo Project Repository “Task Manager”
GitHub Link (contents subject to change)
- A simple Spring Boot application for managing tasks. This application serves as the demo target system for the API tests.
- An API test project that contains several tests written in Cucumber to test the given application.
See the contained readme files for details on how to use the provided contents.
¶ Testing Challenges
Following the walkthrough of the test demo project above, you can get some experience writing your own first Cucumber test(s) in two mini-challenges.
In order to minimize what you have to implement and help with , you will build on the provided Cucumber tests for the previously demonstrated Task Manager application
Challenge 1:
Use Case/Goal: Write a Cucumber test (feature file) that tests the Patch endpoint for a given task ID which is non-existent.
Scenario: So, this newly tested scenario would be that the task ID is not found (= negative scenario).
Hint: Reuse as many steps from the provided “good case/happy case” scenario as possible.
Challenge 2:
There is another previously untested Filter endpoint in the application for retrieving to-dos based on their title.
Use Case/Goal: Write a Cucumber test which validates the functionality of that endpoint.
¶ Additional Resources
1) Demo Application used in workshop (see above):
2) Official documentation on Cucumber and Gherkin:
3) Implementation examples in Tractus-X applications:
- Trace-X
- IRS