Details
-
Suggestion
-
Resolution: Fixed
-
None
-
None
-
None
Description
Many of the JIRA func tests use "assertions" to test if a condition is FALSE, catch the exception and then declare that things are OK.
Many of the "false" assertions are in the web test helper methods and hence happen over and over again. for example
junit.framework.AssertionFailedError: Link with text [Delete] found in response. at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at net.sourceforge.jwebunit.WebTester.assertLinkNotPresentWithText(WebTester.java:627) at net.sourceforge.jwebunit.WebTestCase.assertLinkNotPresentWithText(WebTestCase.java:248) at com.atlassian.jira.webtests.WebTestCaseWrapper.assertLinkNotPresentWithText(WebTestCaseWrapper.java:834) at com.atlassian.jira.webtests.JIRAWebTest.removeAllFieldScreens(JIRAWebTest.java:3605) at com.atlassian.jira.webtests.TestFieldScreens.testFieldScreensOrdering(TestFieldScreens.java:120) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324)
This means that 1000's of lines of assertion stack traces exceptions are generated during the web tests and hence build logs are inflated.
The tests should be tweaked to remove these FALSE POSITIVES.