cube-dragon
commented
2 days ago The first issue has been resolved, and the idea is to iterate through all tests after generation and add numbering to the names of internal and enumeration classes to prevent naming conflicts
Due to the current generation logic being designed to generate tests for individual methods and ultimately consolidate them into a single package, issues arise when there are test classes and enum classes with the same name.
Some tests generated by the LLM not only use internal classes but also external classes with the same name, leading to confusion about which class should actually be used.
The tests generated by the LLM attempt to throw an exception that will never be thrown.