Xray repository - the basic concept

[Chris Kemp]

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

[Chris Kemp]

Not attempting to answer my own question, but I would like to separate some thoughts from above .... I am coming to the conclusion that adding to the Repository/Testing Board creates an 'single instance' Issue.  In my case, this is added to Backlog.

If I choose to add the issue/Xray Test to a Test Set, it creates a separate instance, allowing me to record a result 'within' the test set.  Is this correct?

If so, this is good news, however, I do not want general Team Members to be able to delete the test FROM THE Board.  If I am right so far, I would like to know if I can create a HIDDEN column called Repository.  If the theory is correct, the test (issues) can reside here, but solely managed from the Testing Board.

NOTE: I am expecting the Test Analysts to have edit permissions, so they can create and add steps as they please.  Actually, I really want the test analysts to have edit access to the Testing Board so that they can create tests.  I am still struggling with the permissions that the organisation allows.

To summarise, I would like to solely manage my tests within the Testing Board, using the Repository folder structure.  I do not want anybody to be able to modify the 'issue instance' (aka xray test) from the board.

[Chris Kemp]

Bit of a one sided conversation, but I thought I would provide an update.

The organisation has given me a Team Managed project, so I have been let loose on more settings.  I have been able to change the Test issue type WORKFLOW.

I have created a new Status called Repository (To-do) within the Test workflow.

I have not added this to the board (and suddenly became aware that I only get ONE BOARD in Team Managed ...really?!?!?!?!)

I changed the Create association to Repository, and so new Tests are automatically created with the new Status, and cannot be seen on the board.

This appears to be achieving what I want, but I would appreciate any advice if the community spots pitfalls.

[Rogério Paiva - Xray Xporter]

Hi @Chris Kemp 

I am sure you are aware of this, however, I feel that it is important to reinforce the fact that the Test Director and ALM/QC are testing dedicated software tools while Jira is an issue tracking and project management tool.
So Jira comes from a different background and was designed with a different approach, namely, Jira was designed with Agile methodologies in mind.
Installing the Xray app it will add to existing Jira features the ability to also handle Test Management following the Jira approach.
Since Jira has a more broad approach since it handles several kinds of projects and not only testing, it will require some adaptation and configuration adjustments when dealing with tests.
With this in mind, it is important to understand that the dedicated tools are designed to work out of the box, while in Jira, it might need some adjustments to the purpose of your needs. This is why there are different kinds of projects in Jira so each one can be set up to specific purposes.

Test Repository / Kanban board

These are two different things. Indeed in both cases, it will show issues from a project, however, they have different purposes:
Test repository - is meant to organize the Test cases in folders, the user chooses the organization that makes sense to him.
Kanban board - this is an Agile board and its purpose is to control the tasks to be performed. In most cases, Tests are not supposed to be found here. What could be found here are the Test Executions, which make more sense from a QA perspective, since the executions are the actual tasks to be performed. However, since Jira is highly configurable, you can decide what makes sense to be shown in the board/backlog.
Since Jira has this broad approach, it does not restrict any issue type from the boards by default. So when creating a board in the context of Test Management, it is advisable to filter out the issue that doesn't make sense in the Kanban board.
When you delete an issue (Test, Pre-condition, etc.), it will be removed from Jira, so it will not be visible anywhere. The solution here is to use the filter option of the Kanban board to filter the issue that you don't need in the backlog.

Since you are moving from these dedicated testing tools into Jira which has a more broad approach, I would advise you to first do some courses on Jira to better understand the way Jira works and how to take advantage of its features.
From the Xray side, I would advise doing the Xray Academy courses (https://academy.getxray.app/) so that you can have a good knowledge of the best way to use Xray.

Please contact Xray Support (http://Xraysupport.getXray.app) if you need further help.

Thank you.

Kind regards,
Rogerio Paiva [Xray Support Team]

[Chris Kemp]

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.

[Chris Kemp]

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

[Chris Kemp]

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)?