I've been trying to use Qwen Coder 2.5 (32B-Instruct) for building a Java unit test generator, but I'm really having a tough time. It seems like the model just doesn't follow the prompts I give it. For instance, when I ask it not to refactor or delete existing tests, it completely ignores that and ends up changing everything—like redoing the setup method with Mockito mocks and getting rid of current tests. I also told it not to use private methods in the test class, but it keeps referring to them anyway, which is frustrating since I thought it should understand that doing so could cause compilation issues. Even when I integrated a test runner to share Maven compilation errors, it still doesn't seem to pay attention and doesn't update the test class as it should. I'm left wondering if it's the model that's the issue or if I just need to change how I'm prompting it. Any advice would be super helpful!
2 Answers
I’ve been having similar issues with the model not sticking to instructions. No matter how much I tell it not to change comments, it just goes ahead and alters them anyway. I found I had better luck with the DeepSeek R1 model instead.
Honestly, I’d suggest switching to Qwen 3 non-coder if you can. Qwen 2.5 tends to get tied up in certain coding patterns, which can mess with the instructions you give, especially if they're somewhat contradictory.
I’m trying to host the model using Ineferntia, but last I checked, it doesn’t support Qwen 3 yet. That's a bummer!
Which variant of the R1 model do you recommend? I’m concerned that the 671B model might be too large for my setup.