-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
All browsers and all versions of both jenkins and acceptance-test-harness
The wizardInstallSuggestedTest has been failing since months ago (it looks like it never worked) https://ci.jenkins.io/job/Core/job/acceptance-test-harness/job/master/28/testReport/core/InstallWizardTest/wizardInstallSuggestedTest/ with
{code}
java.lang.AssertionError: Expected: has logged in user adminUser but: adminUser is not logged in. at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.junit.Assert.assertThat(Assert.java:865) at org.junit.Assert.assertThat(Assert.java:832) at core.InstallWizardTest.wizardInstallSuggestedTest(InstallWizardTest.java:73) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.jenkinsci.test.acceptance.junit.Since$RuleImpl$1.evaluate(Since.java:49) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1$2$1.evaluate(JenkinsAcceptanceTestRule.java:175) at org.jenkinsci.test.acceptance.junit.FilterRule$1.evaluate(FilterRule.java:63) at org.jenkinsci.test.acceptance.junit.WithInstallWizard$RuleImpl$1.evaluate(WithInstallWizard.java:43) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1.evaluate(JenkinsAcceptanceTestRule.java:60) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
{code}
The test is asserting for /user/username and the username is sanitized. The username provided is camel case and after sanitizing there are no capital letters there, hence, the assertion fails. It looks like it never worked since there have been no code changes that make the behaviour different and in the test history I cannot see any green https://ci.jenkins.io/job/Core/job/acceptance-test-harness/job/master/56/testReport/junit/core/InstallWizardTest/wizardInstallSuggestedTest/history/