Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,093
Community Members
 
Community Events
184
Community Groups

Jira addon Unit Test fails with java.lang.NoClassDefFoundError: com/atlassian/jira/issue/IssueImpl

Edited

Hi, so I've been trying to learn more about unit tests for my jira addon but I hit wall pretty early. I have simple Unit test which mocks IssueManager with one issue. That looks fine but the problem is when I try to get the issue specifically with issuekey

@RunWith(MockitoJUnitRunner.class)
public class JiraServiceUnitTest {

@Before
public void setUp() throws Exception {
MockIssueManager issueManager = new MockIssueManager();
MockIssue issue = new MockIssue(10000, "FD-1001");
issueManager.addIssue(issue);

MockComponentWorker componentWorker = new MockComponentWorker();
componentWorker.addMock(IssueManager.class, issueManager);
componentWorker.init();
}

@Test
// OK
public void testIssueManager() {
IssueManager issueManager = ComponentAccessor.getIssueManager();
assertNotNull(issueManager);
}

@Test
// OK
public void testIssueSearchById() {
IssueManager issueManager = ComponentAccessor.getIssueManager();
Issue issue = issueManager.getIssueObject(10000L);
assertNotNull(issue);
}

@Test
// ERROR
public void testIssueSearchByKey() {
IssueManager issueManager = ComponentAccessor.getIssueManager();
Issue issue = issueManager.getIssueObject("FD-1001");
assertNotNull(issue);
}
}

From research I did I learned that there might be a problem with jira java api loading for tests that has something to do with osgi and that it could be solved by adding

<bundle-instructions>
<Import-Package>com.atlassian.jira.issue;resolution:="optional"</Import-Package>
</bundle-instructions>

to atlassian-plugin.xml. But this didn't work for me. The question is what am I doing wrong?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events