You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes we can't generate tests for users code. The generation process will fail for some reasons, sometimes they do not depend on us. We should avoid generation in such situations and inform user about the reasons.
It should highly likely be done similarly to the notifying that test generation during indexing is impossible.
Description
Sometimes we can't generate tests for users code. The generation process will fail for some reasons, sometimes they do not depend on us. We should avoid generation in such situations and inform user about the reasons.
It should highly likely be done similarly to the notifying that test generation during indexing is impossible.
Expected behavior
If user tries to generate tests for an abstract class, we should avoid generation
see Test generation for an abstract class fails #873 for more details
If users's code is located in a package which name starts from "java", we should avoid generation
see https://stackoverflow.com/questions/5490555/prohibited-package-name-java
May be there are some another situations...
Potential alternatives
Fail test generation or do not react on users request at all - seems not very good.