build 957: JUnit configurations persistently renamed to test class name
I have a number of JUnit configurations where the class in question is <top-package>.<middle-package>.<possibly-more-middle-packages>.<last-package>.AllTests. I've distinguished these configurations by having the name of configuration be the name of <last-package>. (For example, if the class is foo.bar.cat.dog.AllTests, the name of the JUnit configuration is "dog".)
In build 957, I'm seeing a behavior where the names of the JUnit configurations are one-by-one auto-magically being changed to "AllTests". I've tried to re-save them with the correct name, but to no avail. The result is that now all of my JUnit configurations are displayed as "AllTests"--not the best situation.
Is anybody else seeing this behavior?
Please sign in to leave a comment.
Wow. This is killing me. I'm watching my dozens of junit targets
dissapear one by one into 'TestAll' hell.
Kendall, did you file an issue for this yet?
Kendall Collett wrote:
Submitted as: http://www.intellij.net/tracker/idea/viewSCR?publicId=19450
Barry Kaplan wrote:
>> I have a number of JUnit configurations where the class in question is
>> <top-package>.<middle-package>.<possibly-more-middle-packages>.<last-package>.AllTests.
>> I've distinguished these configurations by having the name of
>> configuration be the name of <last-package>. (For example, if the
>> class is foo.bar.cat.dog.AllTests, the name of the JUnit configuration
>> is "dog".)
>>
>> In build 957, I'm seeing a behavior where the names of the JUnit
>> configurations are one-by-one auto-magically being changed to
>> "AllTests". I've tried to re-save them with the correct name, but to
>> no avail. The result is that now all of my JUnit configurations are
>> displayed as "AllTests"--not the best situation.
>>
>> Is anybody else seeing this behavior?
>>
I'll open a bug presently. (I wasn't sure if the problem was specific to my configuration somehow...)