UniformInterfaceException: failed to disable onboarding in JIRA 6.4.1

Philip Wiley April 9, 2015

We have a suite of integration tests that run fine against JIRA 6.3.8, but they throw  UniformInterfaceException when run against JIRA 6.4.1. 

 The exception is thrown during the administration.restoreData() call. Anybody have a work around? 

 

Output: 

. Checking that JIRA is setup and ready to be tested...
. JIRA is setup and 'admin' is logged in. !! WHY DO WE NEVER HAVE TIME TO DO IT RIGHT, BUT ALWAYS HAVE TIME TO DO IT OVER? !!
. Backdoor GET in 59ms /darkFeatures/site/enable
. failed to disable onboarding
. com.sun.jersey.api.client.UniformInterfaceException: Client response status: 404
. at com.sun.jersey.api.client.WebResource.handle(WebResource.java:688)
. at com.sun.jersey.api.client.WebResource.get(WebResource.java:193)
. at com.atlassian.jira.testkit.client.BackdoorControl.get(BackdoorControl.java:80)
. at com.atlassian.jira.testkit.client.DarkFeaturesControl.enableForSite(DarkFeaturesControl.java:38)
. at com.atlassian.jira.functest.framework.FuncTestCase.setUp(FuncTestCase.java:217)
. at junit.framework.TestCase.runBare(TestCase.java:132)
. at com.atlassian.jira.functest.framework.FuncTestCase.runBare(FuncTestCase.java:378)
. at junit.framework.TestResult$1.protect(TestResult.java:110)
. at junit.framework.TestResult.runProtected(TestResult.java:128)
. at junit.framework.TestResult.run(TestResult.java:113)
. at junit.framework.TestCase.run(TestCase.java:124)
. at junit.framework.TestSuite.runTest(TestSuite.java:243)
. at junit.framework.TestSuite.run(TestSuite.java:238)
. at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
. at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
. at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
.

 

Maven dependencies:

<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>11.0.2-atlassian-02</version>
<scope>provided</scope>
</dependency>

<dependency>
<groupId>com.atlassian.sal</groupId>
<artifactId>sal-api</artifactId>
<version>2.10.20</version>
<scope>provided</scope>
</dependency>

<dependency>

<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.5</version>
<scope>provided</scope>
</dependency>


<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.7.5</version>
<scope>provided</scope>
</dependency>

<dependency>
<groupId>com.atlassian.jira</groupId>
<artifactId>jira-api</artifactId>
<version>6.4.1</version>
<scope>provided</scope>
</dependency>


<dependency>
<groupId>com.atlassian.jira</groupId>
<artifactId>jira-core</artifactId>
<version>6.4.1</version>
<scope>provided</scope>
</dependency>


<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.10</version>
<scope>test</scope>
</dependency>

<dependency>
<groupId>com.atlassian.activeobjects</groupId>
<artifactId>activeobjects-test</artifactId>
<version>0.24.0</version>
<scope>test</scope>
</dependency>


<dependency>
<groupId>hsqldb</groupId>
<artifactId>hsqldb</artifactId>
<version>1.8.0.10</version>
<scope>test</scope>
</dependency>

<dependency>
<groupId>com.atlassian.activeobjects</groupId>
<artifactId>activeobjects-plugin</artifactId>
<version>0.24.0</version>
<scope>provided</scope>
</dependency>

<dependency>
<groupId>com.atlassian.plugins.rest</groupId>
<artifactId>atlassian-rest-common</artifactId>
<version>2.9.15</version>
<scope>provided</scope>
</dependency>

<dependency>

<groupId>org.mockito</groupId>
<artifactId>mockito-all</artifactId>
<version>1.8.5</version>
<scope>test</scope>
</dependency>


<dependency>
<groupId>com.atlassian.plugins</groupId>
<artifactId>atlassian-plugins-osgi-testrunner</artifactId>
<version>1.2.3</version>
<scope>test</scope>
</dependency>


<dependency>
<groupId>javax.ws.rs</groupId>
<artifactId>jsr311-api</artifactId>
<version>1.1.1</version>
<scope>provided</scope>
</dependency>

 

<dependency>
<groupId>com.google.code.gson</groupId>
<artifactId>gson</artifactId>
<version>2.2.4</version>
</dependency>

<dependency>
<groupId>com.atlassian.templaterenderer</groupId>
<artifactId>atlassian-template-renderer-api</artifactId>
<version>1.5.7</version>
<scope>provided</scope>
</dependency>


<dependency>
<groupId>com.atlassian.jira</groupId>
<artifactId>jira-func-tests</artifactId>
<version>6.4.1</version>
<scope>test</scope>
</dependency>

 

 

4 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Tuncay Senturk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 23, 2015

Hi, I faced the same problem. But it fails my tests. Moving back to 6.3.x solves problem but this time I can not test JIRA 7.x features. Have you fixed this problem?

0 votes
José Marañón [Awnaba Software S.L.]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 19, 2015

Well, looking a bit deeper into it, it seems like that is a warning, but it is not actually making the tests fail...Thanks a lot for your reply!

0 votes
Philip Wiley October 19, 2015

I don't recall for sure. I believe moving to JIRA 6.4.3 worked around the issue. Not like that will help you :-(

0 votes
José Marañón [Awnaba Software S.L.]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 19, 2015

I am suffering exactly the same problem with only one difference: they worked fine up to JIRA 6.4.12 and I am finding this error when running the tests against JIRA 7.0.0-m01. Did you manage to solve it?

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events