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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Automated test strategy for Jira Server

Hi everyone,


We have a plugin with a lot of automated tests, mainly Selenium (via Cucumber) that are executed via Bamboo. 

Those tests are very slow and not reliable (for example small AUI change can break them and other false positives).

As a alternative, we are focusing on REST tests, combining them with Backdoor object proposed by Atlassian's functest framework (com.atlassian.jira.functest.framework). It is much faster but there are also some limitations: Jira propose endpoints for a lot of different actions but a LOT of administration tasks are not covered (create workflow, add post function to a workflow, etc). So a lot of necessary background tasks for the actual test are currently not possible to execute with REST calls. One alternative is to backup the Jira with already manually configured administration (test background) and to start our test by restoring it via REST call. This is not ideal because backup file is not very "visible" and it is not going to be easy to add / modify / change it when the new tests are written.


I wanted to start a discussion with you about the test strategies that you are using. 









Log in or Sign up to comment