What You Don't See
Before we go farther, it's worth quickly pointing out a few things
that you might expect to see, but don't. Continuous testing tries
hard not to bother you unless there's something you really need to
know.
First, notice that the tests being run by continuous testing do not bring
the JUnit result view to the front, nor do they appear on the
submenu under Run > Run History. These places are reserved for
launches that you initiate manually. If you want to see details on
what tests continuous testing is running right now, you can open the
JUnit Testing view, which we hid in the Getting Started section. However, we
recommend that you generally use just the information provided in the
status bar and problems view, and leave the JUnit Testing view
hidden, to minimize distraction. Hiding the JUnit Testing view
is as simple as stacking it with another view (like the Navigator),
and then clicking on the tab for the other view.
There are other subtle ways that continuous testing tries to stay out
of your way. First, if there is a compile error anywhere in the
project you are editing or the project containing the tests, or in
those projects' dependencies, no tests are run. Second,
we'll see later that even if two projects
are associated with the same test, only one failure marker per test is
ever created.
