Alright, so I'm trying to automate the pain away from our decade-old monolith. Figured Q would be perfect to slap some unit tests on the crusty Java service classes.
I feed it a class with 20 methods, tangled dependencies, zero test coverage. Prompt is straightforward: "Generate JUnit 5 tests for this class." What I get back is... a skeleton. Like, it imports `Mockito` and sets up a test class with maybe two methods that just call the real method and assert null. Completely useless.
Tried:
* Giving it the specific method signatures.
* Asking for integration tests instead.
* Feeding it adjacent classes for "context."
It's like it sees the complexity and nopes out. Anyone actually gotten this to work on real legacy code, or is it only good for greenfield `Calculator.add()` examples? 🤨
Example of the garbage output:
```java
@Test
public void testProcessOrder() {
OrderService orderService = new OrderService();
Order result = orderService.processOrder(new Order());
assertNull(result);
}
```
My man, if the result was ever null, the prod would have been on fire since 2015.