Author Topic: .vpj handling with Built-in Java Unit Testing  (Read 1848 times)

RaffoPazzo

  • Community Member
  • Posts: 65
  • Hero Points: 2
.vpj handling with Built-in Java Unit Testing
« on: January 12, 2012, 12:08:16 pm »
I noticed this little strange defect:
I open a java project with JUnit tests.
Let's say I run N tests (or N time the same test is the same) by using the SE's built-in pop-up menu by right clicking on a project's file.
Close the project.
The vpj file is modified in this way:
The ClassPath element, inside the "Debug" configuration, has N new ClassPathElement elements with Value set to my Junit jar archive.
The following is a shot of my resulting ClassPath element.

Code: [Select]
   <ClassPath>
      <ClassPathElement Value="/opt/slickedit/vsjunit/vsjunit.jar"/>
      <ClassPathElement Value="...project's sources full-path..."/>
      <ClassPathElement Value="/opt/junit4.jar"/>
      <ClassPathElement Value="/opt/junit4.jar"/>
      <ClassPathElement Value="/opt/junit4.jar"/>
      <ClassPathElement Value="/opt/junit4.jar"/>
      <ClassPathElement Value="/opt/junit4.jar"/>
    </ClassPath>
The above is when N is 4. One ClassPathElement, infact, is always present due to my project configuration.

This little issue is just a little bit annoying when a big number of tests run, because the build window starts to become unreadable. Actually the first time this issue appeared made SE no more able to run tests, saying in the status bar: "No tests found".