You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Providing a Tractus-X Release Guideline (TRG) for Test Automation using Open Source methods and tools, in order to give product teams a template and best-practice example to start with or improve
Focus will be on API tests at the integration test level (end-to-end).
Potentially UI tests at the integration test level can also be covered.
Test automation with Unit Tests at lower test levels are presumably out of scope of this TRG, as those are already covered elsewhere and standard for implementation.
Explain the topic in 2 sentences
Creation of a TRG for test automation Open Source methods and tools.
Providing code examples for an implementation focused on Cucumber (Gherkin).
What's the benefit?
Providing a guideline on how to implement a closed test automation cycle from feature user story via test case creation to implementation, test execution and test reporting.
Ultimately this should result in increased quality and speed in test execution.
What are the Risks/Dependencies ?
TRG would be defined within 25.03 release cycle, but presumably only go into effect for subsequent releases.
Other methods than described in the TRG could be used instead by product teams, thus not an immediate requirement.
Detailed explanation
TRG contents:
Test case creation using Gherkin syntax, DSL feature files
Use Cucumber with Maven to generate test classes and implement them.
Integrate GitHub automation to execute tests
(Potentially additional example code to import test run results into Jira Xray test management system (not open source))
Current implementation
Compare to existing implementations for products Trace-X and IRS as examples that can be provided
Proposed improvements
Feature Team
Catena-X e.V. test management (doubleSlash, on order of the association)
Potentially involvement of additional teams. Interviews for current test automation status have already been conducted with first teams.
Contributor
ds-meberle
ds-hzimmer
ds-asmierzchalski
Additional contributors to be determined
Committer
ds-lcapellino
Additional committers to be determined
User Stories
Issue 1, linked to specific repository
Issue 2, linked to another specific repository
Acceptance Criteria
TRG for Test Automation proposal created
TRG for Test Automation discussed with the respective expert groups and committees
TRG for Test Automation published
Test Cases
Test Case 1
Steps
Do something
Click something
Add something
Expected Result
Expectation
Expectation
Expectation
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
This feature aligns with our current architectural guidelines
The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
Potential risks or conflicts with existing architecture has been assessed
Justification:(Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)
Additional information
I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)
The text was updated successfully, but these errors were encountered:
Status: Draft, not completed and refined yet
Overview
Providing a Tractus-X Release Guideline (TRG) for Test Automation using Open Source methods and tools, in order to give product teams a template and best-practice example to start with or improve
Focus will be on API tests at the integration test level (end-to-end).
Potentially UI tests at the integration test level can also be covered.
Test automation with Unit Tests at lower test levels are presumably out of scope of this TRG, as those are already covered elsewhere and standard for implementation.
Explain the topic in 2 sentences
Creation of a TRG for test automation Open Source methods and tools.
Providing code examples for an implementation focused on Cucumber (Gherkin).
What's the benefit?
Providing a guideline on how to implement a closed test automation cycle from feature user story via test case creation to implementation, test execution and test reporting.
Ultimately this should result in increased quality and speed in test execution.
What are the Risks/Dependencies ?
TRG would be defined within 25.03 release cycle, but presumably only go into effect for subsequent releases.
Other methods than described in the TRG could be used instead by product teams, thus not an immediate requirement.
Detailed explanation
TRG contents:
Current implementation
Compare to existing implementations for products Trace-X and IRS as examples that can be provided
Proposed improvements
Feature Team
Catena-X e.V. test management (doubleSlash, on order of the association)
Potentially involvement of additional teams. Interviews for current test automation status have already been conducted with first teams.
Contributor
Additional contributors to be determined
Committer
Additional committers to be determined
User Stories
Acceptance Criteria
Test Cases
Test Case 1
Steps
Expected Result
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)
Additional information
The text was updated successfully, but these errors were encountered: