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
The total number of tests reported by ProgressLoggerListener is not properly filled. It only lists the total number of Java test classes and not the FitNesse pages which will be included.
For instance when using the project's FixtureDebugTest, with suite: HsacAcceptanceTests.SlimTests.HttpTest the output is:
2017-05-31 21:29:47.274 testSuite Started 'nl.hsac.fitnesse.fixture.FixtureDebugTest'
2017-05-31 21:29:47.274 test Started 'HsacAcceptanceTests.SlimTests.SuiteSetUp' (0 / 1)
2017-05-31 21:29:47.300 test Finished 'HsacAcceptanceTests.SlimTests.SuiteSetUp'
2017-05-31 21:29:47.300 test Started 'HsacAcceptanceTests.SlimTests.HttpTest.HttpFileUploadTest' (1 / 1)
[Fatal Error] :1:1: Content is not allowed in prolog.
ERROR: 'Content is not allowed in prolog.'
2017-05-31 21:29:47.855 test Finished 'HsacAcceptanceTests.SlimTests.HttpTest.HttpFileUploadTest'
2017-05-31 21:29:47.856 test Started 'HsacAcceptanceTests.SlimTests.HttpTest.JsonHttpTest' (2 / 1)
2017-05-31 21:29:47.919 test Finished 'HsacAcceptanceTests.SlimTests.HttpTest.JsonHttpTest'
...
The (x / 1) is, of course, incorrect. The number 1 is calculated only considering the Java class and not the number of pages to be run. It should have been (x / 8), as the currently are 8 pages below the specified suite.
The total number of tests reported by ProgressLoggerListener is not properly filled. It only lists the total number of Java test classes and not the FitNesse pages which will be included.
For instance when using the project's FixtureDebugTest, with suite: HsacAcceptanceTests.SlimTests.HttpTest the output is:
The
(x / 1)
is, of course, incorrect. The number 1 is calculated only considering the Java class and not the number of pages to be run. It should have been (x / 8), as the currently are 8 pages below the specified suite.This is probably tied to the surefire/failsafe plugin update and their issue SUREFIRE-1227
The text was updated successfully, but these errors were encountered: