Because Kotlin is fully interoperable with Java, and .kt and .java files can mix-and-match, we can do this conversion piece-by-piece instead of just one big, messy refactor.
e.g.: fun shouldDoAThing becomes fun `should do a thing`
Convert source files in this order
ViewAction
ViewActionMatcher
Models
HTTP
Handlers
Helpers (the W3C conversion may be messy)
Each step of the way, convert one file at a time and always check that the JUnit tests pass. Do any refactoring that fixes any broken tests. Run the e2e tests too. This will expose any other broken code.
Since, as said above, we can do it piece-by-piece, we can do several pull requests and don't need to do it in just one.
Because Kotlin is fully interoperable with Java, and .kt and .java files can mix-and-match, we can do this conversion piece-by-piece instead of just one big, messy refactor.
Here's my recommended ordering
fun shouldDoAThing
becomesfun `should do a thing`
Each step of the way, convert one file at a time and always check that the JUnit tests pass. Do any refactoring that fixes any broken tests. Run the e2e tests too. This will expose any other broken code.
Since, as said above, we can do it piece-by-piece, we can do several pull requests and don't need to do it in just one.