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
Copy file name to clipboardExpand all lines: .claude/skills/migrate-groovy-to-java/SKILL.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@ Migrate test Groovy files to Java using JUnit 5
14
14
When converting Groovy code to Java code, make sure that:
15
15
- The Java code generated is compatible with JDK 8
16
16
- When translating Spock tests, favor using `@CsvSource` with `|` delimiters
17
-
- When using `@MethodSource`, name the arguments method by appending `Arguments` using camelCase to the test method name (e.g. `testMethodArguments`)
18
-
- Ensure parameterized test names are human-readable (i.e. no hashcodes); instead add a description string as the first `Arguments.of(...)` value or index the test case
17
+
- When using `@MethodSource`, name the arguments method by appending `Arguments` using camelCase to the test method name (e.g. `testMethodArguments`) and return a `Stream` of arguments using `Stream.of(...)` and `arguments(...)` with static import.
18
+
- Ensure parameterized test names are human-readable (i.e. no hashcodes); instead add a description string as the first `Arguments.arguments(...)` value or index the test case
19
19
- When converting tuples, create a light dedicated structure instead to keep the typing system
20
20
- Instead of checking a state and throwing an exception, use JUnit asserts
21
21
- Do not wrap checked exceptions and throw a Runtime exception; prefer adding a throws clause at method declaration
0 commit comments