Xray repository - the basic concept

Question

Hi,

I am just starting my journey with Jira, after many years with Test Director through to ALM.

As a 'so called/dare I say' power user of ALM Quality Centre, it is quite a shock logging into Jira.  I believe Xray is the chosen method for me to write test cases with Steps.

I have found that I can create a folder structure within the Testing Board, which has a top level Test Repository.  GREAT .... I think ...

I am getting the impression that this is 'just another view' of the issues that are created on the Kanban board used within the project??????

My point being, I need a repository for my tests, from which I can 'collect' relevant tests and add them to a/any Test Set when I need them.  In my opinion/experience, this is exactly what a repository is "a place or receptacle in which things are or may be stored/a central location in which data is stored and managed.".

My perceived problem is that when I create a test within a directory, it is immediately shown in the Kanban board under Backlog, as are my Preconditions and Test Sets.  If I delete anything from the Backlog, it is deleted from the Repository/Testing Board.  This indicates that the issue on Kanban is the one and only instance within the Repository, ie if I were to run the test, it would complete with a status, and I wouldn't be able to use it within another test set, which may have a completely different purpose.

Unfortunately, my organisation is too tightly controlled, and so I can't get to XRay settings (as I am used to within an ALM domain).  Can someone tell me if the experience I have is a fundamental limitation of Jira/Xray, or could it be the way in which someone has chosen to implement this projects Xray settings?

Many thanks

ChrisK_i289hy · Answer

Hi Community,  I would very much appreciate knowing how others use the Xray Repository in regard to the Agile Boards (or perhaps, more so, Status).

My understanding of Jira is that when an issue is created, it 'enters' a workflow, which dictates a Status.  These Status are normally visible on a board.
Using the default workflows, my problem is that when I add 'many' tests to the Repository, they end up in a board, and Jira alerts me and suggests that I Archive.

I do not think filtering will resolve the situation, as this would only 'hide' what is on the board.

Also, I would like to understand if anybody uses the board concept for tests in a Repository.  I believe the boards are used to transition between Status.  I cannot see any reason to do this with tests in a Repository

Should I just create a workflow for xRay tests that uses a Status that is alienated from any board (ie the Repository Status in my initial post)?  I know I can do this, but I would like to understand best practice.

I have not found a discussion about the use of boards with the Xray Repository.  If this exists, can you point me in the direction, or tell me how you have setup your Jira projects (to cope with hundreds of test cases)?

ChrisK_i289hy · Answer

Hi @Rogério Paiva - Xray Xporter , I am still on my journey, and would very much appreciate some more advice.  You mentioned, regarding Agile Boards, "Tests are not supposed to be found here".  Could you expand on this?  Is it correct that the tests will always be associated with a board (status) within Jira, but you can choose not to 'see' them by using filters?

My question comes from a warning I received after importing >100 test cases.  The warning suggested that they were archived.

I have read through the Xray documentation for Importing and Administration & Configuration, but I cannot see any reference as to how the test issues are 'stored' natively in Jira.

(is using an archive suitable, or would they become 'unavailable'?)

Many thanks

ChrisK_i289hy · Answer

Hi @Rogério Paiva - Xray Xporter , thank you for the summary.  You have nicely explained how Jira and Xray fit together.  My fellow team members had 'just' reached the conclusion about using filters with the board, but it is great to have confirmation it is the 'standard' and intended method.

I expect you can guess that I really like the Repository concept.
I would prefer to have the Test Sets visible/stored in the Repository, so they can be managed there, rather than switching filters in a board.
Given the way I understand how it works, I am considering the Test Set to be a Test element, which can be added to an Execution, being Project element used for tracking progress (as you mention above, aka Tasks to be performed).

I guess this isn't an option?

NB I have been on holiday for a week, and a colleague has suggested to the boss that the repository is not needed as everything can be done with filters.  Personally, I believe the Repository has great value for management, but I may have lost the fight due to absence :(

FYI I progressed to Test Coverage reporting, which completely messed up my 'investigation'.  I thought it would simply report on the Test Entities added to my Execution, but found that Test Coverage tests are completely different entities to 'Tests' (ie you can add both within a Test Execution).  That said, I am stating to appreciate that the xray gadgets in a dashboard can report on test progress, so perhaps I don't need Coverage ...I still have a way to go in my journey.  I didn't know there was an Xray academy and very much appreciate the link.