The first time you run tests in the Eclipse workspace, you will be asked to choose the launcher in the UI.Please delete any JUnit launchers you have in your workspace that were created before this release.Tests were slow to launch because the test classpath was computed multiple times.Īs a result of the redesign, you will notice these differences:.Only the Bazel JUnit Target option worked. Running tests with the standard JUnit Test option previously resulted in a Class Not Found exception.The latter option has been removed with this release. When running tests, users were presented with a confusing choice in the Eclipse Run menu of JUnit Test or Bazel JUnit Target.With this patch release, BEF now uses the standard JUnit infrastructure for launching tests. ![]() ![]() ![]() This work is a bug fix, but required a redesign of the original feature and so has some user-facing impacts. This is a patch release to resolve a couple of long standing issues with launching JUnit tests in Bazel workspaces.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |