Generating a Java program with 90% less code

Re:Generating a Java program with 90% less code by salawat on Wednesday December 04, 2019 @12:06PM (#21704039)

Uh. Question. Why are you executing tests to get the compiler to tell you what was effected instead of doing a top level recursive grep to identify any classes or configs with an explicit symbolic dependency?

I mean, you get the same result, sure, but I find I can hardly ever rely on test coverage alone as an accurate safety net to clearly indicate whether I've reached an actual stopping point for a full refactor.

This is one of the ways in which Java excels, in that that loop is fully accommodated for in most major IDE's.

You can still get caught by surprise at runtime, but I've found that for a strongly typed language like Java, the syntax, and necessity of boilerplate makes most bugs obvious until you start getting overly dependent on frameworks you don't understand.

[ Parent | on HN ]

Re:Generating a Java program with 90% less code by nurettin on Wednesday December 04, 2019 @12:56PM (#21704808)

I am not executing tests to perform import error detection. That was before refactoring tools got better. I was executing tests to check for import errors because it doesn't rely on full coverage on every method. It relies on all modules being imported by tested modules. That is easy to do even if you are too lazy to test every module. Just put an empty test function in all of them and pytest will detect them recursively. Given all that, I would avoid executing manual grep commands. However, you have a valid point for configuration files. Especially log configs need to be checked.

[ Parent | on HN ]