citrusframework / citrusframework/citrus
Remove Test-Designer
Open
maintenance
prio-medium
- Dominant language
- Java
- Stars
- 485
- Forks
- 155
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 6
Description
To clean up the Java DSL, improve the framework’s maintainability and reduce the complexity from a user´s perspective, we are going to remove the TestDesigner.
Contributor guide
Research direction
Start by locating the TestDesigner entry points and references in the Java DSL. Read the surrounding framework code to determine the full removal scope and any affected integration tests. Done means the TestDesigner is removed without leaving broken Java DSL references, with the relevant test suite passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100