Teaches AI agents to write idiomatic Kotlin instead of Java-in-a-.kt-file.
98
98%
Does it follow best practices?
Impact
99%
1.20xAverage score across 8 eval scenarios
Passed
No known issues
The platform team maintains test suites for two components: a StringFormatter utility and a UserService. Both were written in JUnit 5 some time ago, and the team has been modernising older test files to fit current project conventions.
The files are:
inputs/StringFormatterTest.ktinputs/UserServiceTest.ktEach file has its own character — read the existing test code to understand how each one is shaped before picking a target style. The team expects the migration to honour the structural intent of each file, not just mechanically port annotations.
Write the converted files to output/StringFormatterTest.kt and output/UserServiceTest.kt.
Every existing test case must be preserved with its intent intact. Any per-test setup logic must continue to run before each test.