JUnit

But it was very, very limited.

And I think one of the, I think at the same time when Eclipse kind of got built, There was this movement around JUnit and restructuring and restructuring tools.

And those were kind of the things that they built into the Eclipse IDE right from the start as well as re-automating, renaming and extract method and things like that.

And that was kind of a giant step forward compared to all the other IDEs that exist back then that just purely kept doing, let's say, syntax highlighting and autocompletion.

Right.

The Eric Gemma, yeah.

The Eric Gemma, like the NL4, Design Patterns, JUnit, and Tender, and things like that, right? One of the greatest of all time, right? Yeah.

So he led the team in Zurich and I think they mostly focused on the Java developer experience in Eclipse, but also probably decided a lot of the underpinnings of that as well.

Is it necessary to customize them? Mostly not because we try to design them in a way that they do fulfill the dreams and wishes.

So speaking of the JUnit or the testing workflow, right? So it basically looks at your application, figures out if the tests are available or not, writes a testing strategy, lets you edit the testing strategy and even adopt it.

And you can go as far as even add code coverage to it.

So you can influence it in the important pieces.

And you know what's also interesting? If you watch the token counter during these workflow execution runs, because as I said, some of this runs on your laptop machine that doesn't do a model round trip.

So there's just some execution happening and only the results will be shared with the model.

So the Java JUnit workflow can actually estimate migration efforts like front up if you start running it.

So talking about these individual workflows, but what does a good workflow look like for a Java developer on an enterprise? What's the full like snout to tail workflow?