Xray – Test Management inside JIRA (Extended Demo)

Good morning. Good afternoon. Good night depending on your location Welcome to our fourth X-Ray, Webinar so we’ve been having this series of webinars, and thank you very much for spending some time with us today So my name is Joe Mendoza [I] know. It’s kind of a difficult name and I’m the expanded on steam business developer joining me today Sergio Freire I have [said] you frightened. I said you I? Sergio is one of our x-Rays product manager and it will be the one conducting the webinar today in today’s webinar We will go over the main features of X-ray of course one of the most used test management add-on for Jira and we will include some of the features of the latest version so the 2.0 to the doe version of X-Ray if You want to check all the [Brand-new] features you will have of course some in the future some Webinars just relates to this do these [to] that over zh n’, but before we dive into the tool [I] would like to give you just some quick briefing about the expand identity So for you to have an idea. What is what? What is the team that is behind this X-Ray and on so we are making we’re making add-ons for already [four] years? We’ve been having some some experience already We are portuguese, and we do have three offices at the moment so in two different countries, two here in Portugal and one in the UK of course we have at the moment more than [1,000] customers just for X-ray so it’s been growing quite a lot in the last months and we are we are in More than 60 countries so customers in all over the world We of course paid a lot of attention to the new features So they are very important for us and of [course] the opinion of our customers It really matters to us and for example the student version It was a really good example of that, so we do listen well to do the opinions of our our clients so the feature request And we do select the ones that were making more sense for [us] in terms of timing and be selected to build up the studio version so for us It’s really important to have your feedback on of course you have our Clients feedback And of course not just not just new feature requests But also the supports we have more at at the moment more than 500 support tickets Opened and closed so we have a lot of contacts with our clients in this kind of support so and we do have we do [have] We are quite fast in terms of replying and we do keep a lot of attention [to] [that] so as well So you can have the best support as you can get at the moment, [so] of course because of that we do have a lot [of] lines of code and the First of the work is growing and lines of codes of code [maybe] even more in the future, so [we] do hope so with more with more Features new features and the upcoming releases that we’ll have in the [future] for sure so about the two products We are not just about [x-rayed]. We do have another event called exporter x4g reason [add-on] that allows you to export all your jira information and For you to have it in some several templates so for example if you need some information to give up to some client to some management that they have access to Jira and then Do the information that you have there [and] some project or in some specific, Jira issue. You can use Exporter to export that information some I don’t know it can be excel template to a a [word] Format, or a pDf and f it ss documentation and give it to your content or to your management so that’s quite a quite a vein the add-on that it kind of it [kind] of Save some of some of the situation that it’s not very easy to be done in in General, so yes You can export some some information, but you won’t be able to build up some really nice Customizable template out of it So this is also some some really important add-on for our our situation correctly in the expanded ons of course the most important part of us it’s our clients and That this is what more makes make us heart Work harder every day and to build up a bit even bigger and on an even bigger More more suitable for for everybody So with me as I said surgery will be the one that will that will conduct that demo today we will go over the main features of X-Ray as I mentioned of course. [we’ll] try to have some some part off of this webex Of this webinar to [be] a to try first to have some Q&A session and you can ask some some questions of course We’ll try to answer all of them if you’re not able to answer all [of] them here. We’ll do [it] afterwards [also], note [that] this this session is being recorded so even if you have some some colleague that were not able to join us today

You will be able to send this [to] him Or it will get for sure if it was [rejected] you will get for sure an email with that We did this information with this recording so but I will pass now the ball [to] cells you I will present the agenda and also go on with the demonstration of this really nice event for Jira Hello, everyone so first of all thanks for attending our webinar. [I] really hope you enjoy it Name of this webinar is to give you an overview of the main features of X-Ray We won’t have any we won’t have time to explore all features in detail, but We will get an idea of what wax Ray allows you to do in terms of test Management and the best way of course for you to learn all about x-rays by using it and For that we have [a] Sandbox environment that you can try And or you can download the trial to your local? Instance if you want and finally just to say that room as one was saying we will reserve some amount of time in the end So we are able to qualify it with some of your questions. If that’s not enough We’ll contact you afterwards and try to answer all of you so let’s start and Just to show you very briefly. What is our agenda for today and I will start by explaining and what [are] requirements in terms of the X-Ray, how do you configure that and I will then create a Requirement f and from that requirement, I will create multiple tests and Because X-Ray allows you to manage different types of tests And I will also create a precondition. Which is like and the initial conditions. That should be must be met before executing the test and Then I will group all the tests in an entity that we call a test set From there we will create a test plan in order to create track of our our tests and I will create multiple test executions and see how that will fit into the test [point] [and] I will show you them the difference between them the execution of [meinl] and the tomato tests and I will go [briefly] through [the] project tabs to show you the kind of things that you can easily obtain in X-Ray and the the Last topics are written with reporting and with x-ray you can do reporting in Several ways and then I will show you the or at least talk to you about the different possibilities that you have for [that] and I will show you on how you can make reports using the exporter which is our Other [hat] on just [for] exporting material issues Okay, great, so let’s start By showing you then? The the settings that x-Ray offers you can see that now [you] are in the advanced configuration Inside the general administration page, you can see that X-Ray allows you to configure many set same set but I will just focus for [now] and on the issue type mapping which allows you to define which issue types should be consider as Requirements, and this is configurable, okay, you can just [drag-and-drop] them [Dasia] types to to to this column and you can also Define which issue type should be considered as Defects and this is important because for example for requirements. You can have your own issue [typed] and Make test coverage on that So now that I have shown you where and what issues she in [two] types should be considered? Requirements, you can see that we have here is sorry As a requirement issue type. I will start at start by going to my project which is a dummy calculated project that I have and I will start by creating a Requirement that in this case will be a user story so Let’s say [that] The first man important requirement that my calculator should have is That each be able to calculate the sum of two numbers and let’s say that this is for version 3 level decision and it’s also for the current Sprint Okay Now let’s go to our user story and you can see now that the screen of our user story is enhanced with them and

specifics that X-Ray provides for test management so you can see right away? that we provide a custom field which is the requirement status the change that shows us that this user story it’s [and] Uncovered for version 3 got out of the system because we haven’t Yet Made any test for it so you can see right away the status of the our requirement and from the test coverage Pal I know below you can see all the related and tests that are covering this a user story so if you want to [create] a Test for this user story you can just do it right from this button You can also do another thing for example. You can create a test execution which in this case is a sub test execution Which is like a task that will contain all the tests that are covering this user. Sorry if you want you can also a link in this user story with other tests that you may have okay, so Now that we have our user story created Let’s start by creating [and] [the] different type of tests that we have and I will start by creating a manual test So I can [do] it right from here or from the top Menu option, but if I create it from here it will automatically be linked with our user story, so let’s do it Let’s create our and all tests You can see right away that X-Ray Provides different issue types so in fact all the test management related entities are in fact [zero] issue types and this allows you to Configure things like the workflows or the user screen so you can even have your own custom shows to these entities so the first main entity that we will be using is the test entity and the test entity it basically is like a test template for our tests either if they are an Either whether if they are manual or an automated test it will be in fact a test then we can see that we have a Test set and the test set is like a a group of tests nothing more than that, but you can Put [your] tests on [different] test sets and group the test by some something that makes Some watching to use for example. You can group test by by feature or by in my regression and so here you You can group test in many different ways in fact Then you can see that we have also precondition and a precondition is like saying that and before [you] start is your tests and some initial conditions must must be ensured and and You could of course write that same condition that that initial conditions in as the first steps of the manual test for example but sometimes you you may have to to reuse the same preconditions between Different tests so for that we created an abstraction of that initial conditions and we have the precondition which Implements that and you can reuse them the the precondition between different tests then we have a Test execution and the test execution is like a task for easy catching is getting a bunch of tests, so [you] each time you want to execute one test or a group of tests you create the test execution and you for a given version of the system you assign it to someone and then the results the test location will also contain the result of that that [desk], and Finally we have a the test one and the test plan is is like the allows you to group different test executions and to keep track of Tests between different executions, so it contains the latest status of those tests for Independently of the number of executions that you have I will show you Each one of this issue types how to use them and during our our webinar

And [I] think it will be more clear to you as soon as I make the demo so let’s start by creating our manual test and We can just fill out the summary of course. This is a standard manager issue Type you can and you can change the priority you can assign it to some component you can add attachments you can put labels on it, and that’s the beauty of using 0 is attached [to] manage your a [awkward] test management entities the important part here is [that] In the test details tab you can see that We have a test type Where you define which type of test? We are in fact writing so in this case. We can even we can have a manual or an automated test and I will start by creating a manual test and which basically is composite Multiple steps so I can [do] the steps right right through the air from this creation that [dialog] let me just fill Some of them right now you can see that and we have the the three columns and the basically [representing] action of the step the expected result and We have also one optional comma colony which is the data which allows you to? To write some like some input data for the step instead of writing the [8a] in the step Column So let’s press 2 and when we press Eco. We should have three Okay, we now have a bunch of steps and and from this creation dialog we can Edit the steps [we] can reorder them, but of course this is not that much user-Friendly Friendly But when we have to recreate the test itself we go to the issue screen where we are able to do this With more options and in [our] mark a convenient way You can see now that In the we have to add tabs, and I will not go through them but basically the test stats and the precondition tabs allows you to Directly associate this test with an existing test set or any some existing precondition The important part here is as see a shin between the test and an hour a user story so I’ll I’ll do x ray and Associates what one to each other? And you basically we implement a specific linking Between the is the story and the test which is a test linking and and In this case [our] our and our test it tests the the user story that they specify here this issue in fact a test can cover multiple requirements if you want Okay, so let’s create our manual test and let’s go to to the screen of our test Okay Our test and basically contains within the tesla tail it clearly identify the type [of] test that we have and we can now see that we have the multiple steps here, and we can reorder them and We can do and we [can] clone we can Remove the steps we can add for example some attachment to to a given step okay, let’s upload it if we want and We can import a steps for from for example from [AKa] existing look CSV file or from JSon file or if you want you can even write your steps in exhale and and sometimes [some] customers find that very convenient [and] then you just copy paste them to to to the X-Ray Okay One thing that you can do by in the steps you can use wiki [markup] markup any other in order to make your tips step subscription more user-Friendly Okay That’s basically it, but now let’s go a bit down on the our page and we can see them in the existing associations that we with

preconditions right from the test screen or within associations to easy existing test sets or we can see also and are All our [rents] that we have for this test so as soon as we start executing this test. We can see the Results right here this section if you want and you can easily execute this test run away by this and button and We can create a just a test execution from a containing this specific test so we call this like an ad Hoc test execution Because we are educating it outside of a test point And finally we can see that Out the association between the test and the users [or] is done, and this is them between using them Dialing tests to our user story Okay, let’s come back to our user. Sorry now and you can see now that our requirement status is showing that and In fact our requirement now It’s not is being covered, but it’s not run yeah And it’s not run because we have one tested associated to it. We can see that in the test coverage panel and we don’t have a nice equation for it so and that’s why the Requirement is is considered as not run for a patient through the row You can see also them the status of the execution the later stages are of this occasional this test has to do and If you [only] want we can evaluate it for in some different version of the system so if I don’t specify your version it will give me the the latest status of the executed test okay, so now that I have created our our manual tests and to create a Precondition and associated to our manual test so you don’t have in fact to associate Preconditions to [tests] but sometimes you might find that useful Because sometimes you have to do to ensure the same things between different tests so let’s create a precondition and Let’s say that before I started in Doing my son validation on the calculator. [I] must ensure [that] the calculator must be turned on Okay now What is important here? Is that the micro condition type must be of the same type as my manual test that I’m going to link it so in fact I can have the Preconditions for a [convert] test and this will be automated preconditions Then in the conditions field I can specify [let’s] see this is an open text float Where basically I just define the things that must be ensured by This precondition and on [Kalka] way then I Can set this precondition with? The [tests] that I have just created so let’s see it and now let’s go to the to the precondition and Basically the precondition details is just show that The condition is in fact turn on the calculator. [I] can see all the tests that are Linking to it Within this this section, and I can associate this same precondition to other tests that I might have and and Now let’s go back to [our] and Then [all] [passed] you can see that from the Minolta side and I Conceale I can see quite easily [the] preconditions that I have associated to it in fact I can have multiple preconditions, and I can Change the order of them so whenever I’m going to execute this test they say and the precondition say they will appear in the same order [that] I have here and in this precondition panel [ok] manual test and precondition then now let’s create another add other the different type of [tests] that we have and now I will start by [creating] an A not automated [cumber] test So we just fill out a different summary [freight] and within the test detail

Let’s say that this is a convert test in cucumber you Can you can you have two different types you can have a scenario race line scenario outline? So in this case we [will] be using a smaller outline which basically is like Exercising the same tests with different input data multiple times, so let me just fill out a [with] with some Data specification that I already have and You can see that. We do support syntax highlighting for a gherkin which is the the language that Basically where you tells you how to specify? the BDD and that implements the specification on this test so and this this is [why] given and when when then they are highlighted and Now the session to the test Once again since I [created] from the user story. It’s automatically links ok Click right, this is basically hit so let me just go to the humber test and show you then The Syntax highlighting once again, so if I write [that] a sentence and working leads automatically detected And you can see that it will show in angle So now let’s come back to our user story [I] have two tests finally let’s create the last different type of test that we may have And the final test that that we may have is a generic test so, what is a generic test a Generic test is like an having some automated test that it’s not and a cucumber test so it might be some Jayne unit tests and Ruby Script, or some shell script and whatever and But this allows you to create an entity In Jira where you can? report results to so sometimes you may have your own automated tests implemented in some language And you want to report results of it [too] to zero? So for that you need [to] create an entity which would be a generic credit test and report results to it So you have a generic test definition tube where you can use it to complement [the] solution of the test in this case that? You can send it’s like I can use to put like the class Name and the class method that implements a that automated test or the name of the script wherever and then It’s basically This so if I go to my generic test it will show you that There [is] bad the generic test and the definition Has then the finishing slope that I wrote two moments ago, and you can see that. It’s once again It’s linkers to our user story Okay So now that I have created my different types of deaths and my precondition. [I] will create a test set So let’s create a test set which basically is like creating a group of tests that For all my arithmetic operations, so sometimes Nau and you want to group tests Just to make [it] more easy easily for you to whenever you are going to execute the text to pick them up without going Individually through each one so you can create as many tests such as you want and you [can] put some label on it So it makes it would be more easy for you to find them out injury and and sometimes you may you might want to have some tests more handy, so this is a way for you to organize a Test set a test in Jira Okay The test step allows you to quickly have the [tests] that I want to make part of it So you’ll have the three the three different Types that are test types that I have just created so you can see they they are basically the same that I have here

And let me just open the test set you can see that the test set Contains A list of this, okay, you can even reorder them if you want from this test set you can add more tests and There if you want you can even create a test, and it will automatically be linked in to this test set Okay, now that I have created all my tests and how do I start executing my tests? So before is occurring my test. I must create a plan in order to keep track of my tests because I may in fact be easy getting my test multiple times, and I might want [to] keep track just of a certain group of tests and For that I have them the test plan Entity so let’s say that then I want to keep track of all my relevant tests and I want to keep the track of this on the version 3 level [of] the system It’s important that I define here in more fixed version field the version that where I want to check the test zone Because whenever I’m going to execute the test The disease additions that I’m going to create. They will automatically inner the fixed version from the test plan Since this is a plan a plan of course as like beginner and the hand [8] so let’s say that I want this plan to click check under the test between today and next week and Then you can associate the test that you [want] picture [color] on the test plan so you can pick? individually the tests or you can just Pick a test set and that will automatically import the test belong to this test set Okay you can see now that I have the test plan is a Standard a is your issue type But it contains The information of the test that we are tracking on it so we can see that this test plan is composed of three tests and the three tests are and right below and in the overall execution status You can see right away, which is the stages of this the later stages of the tests that are? Part of this test plan so you can see that All [my] three tests my part of it are still to be In to do because we haven’t executed Any of them at least once? below you can see and The tests so you can see that we have the generic second [cumber] and the manual [test] you can see the Lincoln Requirements, you can see the number of these equations that we have for each one of the tests and you can see the latest status of our individual tests By clicking on this arrow, you can drill down on on On the test and see then All the test distributions that we have for it [ok] so now that I have created my plan and Noticed that I can can in fact create multiple plans for a given portion, but I could for example Want to track them independently? So now that I have my test plan I’ll do y is equal to this so I? Can execute the test from this? button and it will create a test execution for example with Containing all my tests that make part of the test plan So let’s let’s do that now and you [can] see that the [tesa] execution that I’m going to create and Once again a test execution is like a task for [using] a budget a bunch of tests. It’s automatically the attribute of the fixed [versioning] is automatically filled out and With version 3.0 because we created a text plane for version 3 3 0 and one thing that we can see that we can also assign to a test execution Would be the test environment

test environments are a new feature of X-Ray to the [roll] and Although I’m not going to show you exactly that during our webinar Basic just to give you a glimpse what? It allows you to do Basically it allows you to institute the same tests on different Environments, so imagine that we have this test And you want to is equal to them both in 100 and in ios, oh Of course you could create a different test one for [han] [some] for Android and other ones for Ios But that will be not very efficient the best way would be to Create the Different test executions and say that okay this one’s Then this tests were executed on Android and the other time they were executed on Ios and the whole institution status for the overall status for each one of the tests Will have into account the latest status that you have for the different environments so for example a test is considered to be passed only if it’s passed on the different environments that you may have and And it is considered as failed if it fails it twists on one of the environments. Where you have institutions Of course you can either use this or not and I will proceed without using it So let’s create our Texas efficient containing our three tests Okay, you can see that now. We are at the test execution and Shoe screen, and you can see that This is an a plan test execution because it’s linked to our test plans through this custom field which is a test plan custom field and the institution and the test execution contains also [a] informational execution status progress which shows you in a very expedient way then the results of the [tests] that make part of this test institution, so My solution is composed of three tests, and they are all the three they ought to be easy to do so and right below we [can] see the trim in the different tests my part of this test execution We can of course you can also reorder this by dragging by moving that this is the test within the test execution We can see the number of the requirements that each one of the tests are going [reagan], and if I click on them within the number I will go to the search issue screen and containing the requirements I Can see also the assignee [okay]? And one thing that in that is rather than tears Since this is a standard [Da] [zero] issue you have an a default assigning which in this case would be me which is the administrator and the dividual test run would be assignment to add to by default to the test execution assignee, but of course you may you may want to reassign an individual individual run [to] a different user so for example I could say that okay and the Generic test should be Executed by drive for ISM. Okay? Okay Now let’s let’s let’s show you how to execute our tests, so I will start buying by the generic test in this case and So our generic test our script that may be implemented Somewhere else and we have the acquittal [as] imaginary Hq to date and validated data query the Script was passing So we can easy get it in line and this Will basically change the status to the two to the given status? Of course you could do this by [using] our rest api so you don’t have to do easy cook this manually, but probably in at least in the initial phase you may have your automated [test] Implemented and not integrated with X-ray so you can come here and just change it

the State [dessert] of the testing line Okay now let’s go to our manual test and show how to go to execute it, so And of course I can change [and] change the overall status of the testing line But the normal way to execute our test will be to go through in the individual steps that make part of it So let’s see secure and From our execution screen you can see that in the [top] we have we can see the test run a result so Just give you some important Mission and [your] screen and you can see that this is an appliance is equation because it’s linked it to our test points through this custom field which is a test point custom field and the institution and the [test] execution contains also [a] informational execution status progress which shows you in a very expedient way then the results of the test that make part of this test institution, so My solution is composed of three tests, and they are all the three they ought to be easy to do so and right below we can see the trim in the different, and that’s what my part of this test execution We can of course [it] can also reorder this and by dragging by moving that Is the test within the test execution? We can see the number of the requirements that each one of the tests are value [Regen] and if I click on them Within the number I will go to the search issue screen containing the requirements [I] Can see also the assignee okay? And one thing that in that is rather than tears Since this is a standard Da [0] issue you have an a default [assigning] which in this case would be me which is the Administrator and the Dividual test run would be assignment 2 [2] by default to the test execution assignee, but of course you may you may want to reassign an individual individual run to a different user so for example I could say that ok and the Generic test should be executed by drive for iSm ok ok Now let’s let’s let’s show you how to execute our tests, so I will start buying by the generic test in this case and So our generic test our script that maybe implemented a similar house And we have the [qt]. Less imaginary HQ to date and validated that Agree, the Script was passing So we can easy get it in line and this Will basically change the status to the tool to the given status? Of course you could do this by using our rest api so you don’t have to do easy cook this manually, but probably in at least in the initial phase you may have your automated tests Implemented and not integrated with X-ray so you can come here and just change it the stage result of the testing line Okay now let’s go to our [mono] test and show how to go to [executed], so Of course I can change change the overall status of the testing line But the normal way to execute our test will be to go through Individual steps that make part of it So let’s see secure and From our execution screen you can see that in the in the top we have we can see the test run a result so Just to give you Some important Feedback is that X-Ray whenever you make create an execution of the test and and the specification of the test is Copied in this we create like an instance of the test

We call it a test run [so] [even] if you change the specification of the test afterwards This is the specification of the test that will be available here It will it won’t be affected, so this is how we guarantee the consistence of your data and Here on the top. You can see [that] our test run is in to do of course if you want you can change them the cities of the our test one of the given status and you can see also the [version] [why] this test is going to be secured and Here on the top section of our test run. You can leave a [verbal] Feedback tool to our test run [so] I can leave a global comment on it I can create a defect in it will be associated globally to to our run and If I want I could add some [file] sir as evidences Relevant evidence of our execution of course the man then the most common would [be] to to To live Feedback as in the steps in the [division] steps whenever we are we are going to executing them individually so below in the execution details You can see that the execution detail shows you the and the linking to our User story, and you can also have access [to] the preconditions that Are associated with the in this case with the our manual tests? below We can see the the individual steps that that implement her this manual test and they are Identified by the by the number in fact you can even easy get them out of order if you want but the normal thing would [which] [is] the first step first and then the second one so on and each one of the steps and is composed like the things that we considered as input data for the step and you have access for example to them to the attachments of the step you can see the scription of the step and expect the result Below and this role is like the outcomes of the step the results So if you want and can leave a comment, you can create a defect and If you want you can for example add some evidences [to] the step itself then in the in the right side you can change the state of the step and Let’s say that all our steps They passed you can see that as soon as I change the step State and just the end the Step color it will automatically relate to stay in the color of the stair step state and You can see that on the top [the] overall execution set is for this test is now being changed to executing since I I’m in the middle of execution So let’s pass on our three Our three first steps and let’s say that whenever we were easy cutting our Our calculator test it fell off So let’s say that the final step to trail we could leave you’re a commentator. Okay calculator Fresh Okay Then if you want you can add some attachment right here okay, and If you want you can create a defect right from the step if you create a defect right through here it will Automatically be links with this test execution and our tests, so let’s do it Let’s create a defect you can also associate the existing Des fĂȘtEs if you want Ok let’s create a defect just to show you a nice feature of X-Ray, I said that the calculator crashed you will see that. Let’s see that and The facts portion is [automatically] throughout with the version where we are executing our [tests] and Below in the description field it is [a] multiple throughout with the steps until the step that fails So let’s just create the defect

Let me shoot then that our defect which in this case will be a bag you can see that the description contains them other steps until the final step and the way you can see that and this effect is linkage with our manual test and with our test execution So even the behavior of the of filling out the description with all the steps until the final step Is configurable? Okay, so let’s come back to our education stream And since we failed our our step we can see that on the top Then now the education status have ours test is considered as failed So if you come back to our testing institution We can see now that the test execution show us that one test is passing and the other one is failing Which is our manual test? Okay And now finally let’s execute that our [Encumber] test, how can we do it? First since we have my a we made a specification of our automated test in Jira, Math We must extract that specification from zero itself, and so we are able to put Our [at] method test we can do that using our rest api or if you want you can use it through the UI [I] will do it through a wife just to show you how this can be done. Let’s export this to humber And let me just copy this to a sample Had come a project that I have and let me show you briefly the Specification and the generated features file you can see that the generated feature file contains the the specification of the Our [compiler] scenario outline and it also contains a the summary [of] the our [user] [story] And you can see that in both our scenario plan and our head feature they are and they are text with the issue Keys of the respective test and test set and they our test execution and even how our user story key So this is what allows us whenever we are going to skip the test? and we never we opt in the report that [kookaburra] generates for us and is the one allows us – To make the linking between the results and the entities with that we have inside X-Ray So let’s see security and for that I would just easy quit the condor a Command of course I can pass some arguments to generate the adjacent report I’ll just scrape that next with that. We can see that now I have a Json file which I can then upload either by using our ui or by making a HtTP post request to our rest api so let’s do that, and if [will] work fine if I refresh now my test execution We should now be seeing that Now I have two tests passing because our cucumber test is passed Okay, this is great [and] I cannot even go to the institution details of our automated tests and a below [I] [am] able to see and [any] video results for the different? Examples that were [given] in our [conversin] area [outline] so I can see [the] [tower] calculator. It worked fine [for] all the different examples Okay Okay, great. So now we have two tests passing and let’s then we have one [filing] So now let’s come back to our test plan and see what it shows us We can see that Basically our test plan since we have just a test institution it shows you shows you then the same information that we have in the test execution in fact so here we can see that my the latest status of the tests and

our passing just except for my [men’ll] [test] since the last execution That I have for it or [as] [a] fail So now that I want One test in this case family. How do I create another test education that validates? our family tests so I can easily create another test execution From within my test plan just for the [tests] [that] are only given [me] [given] cytosol and given a set of stages so let’s create a Test distribution just for the the tester is [filing] Okay Let’s create it okay, now I’m in my test institution and It contains this just one test which feels which is the manual test okay in this case Let’s pass it in line Without going through the individuals steps and let’s come back to [our] test plan Okay, our test plan now shows that that we all my three tests are passing and why is that? this happens because our [manual] test has two institutions and although it failed on on our first institution the our last execution as best soda and The latest [stages] of this test is considered as being best Okay, this is the way that place test [binds] make tracking [a] different Set of tests with multiple classifications more easily Okay Now that is good manual and method test Let’s go to to our pressure test to show you the kind of things that we can easily do in X-Ray so Within your project taji you can see that X-Ray provides several options in fact that allows you [to] quickly List all the tests that make part of your test repository all the test sets all the [tests] institutions and all the test plans and let’s start with the tests and this is This option basically shows [you] all the tests that [are] part of our project, and you can see quite easily and the different Tests that we that we [have] we can filter them out for example by component we can even analyze the stages of this test for a given version so for example I can analyze the This test and for version 100 of the system and this would in fact what will take into account is the [the] [like] the execution that we have for button [1] thorough and Show you right away [the] status of each test for that person the test set Tab shows you all [the] test set such all the groups of tests that you have and And once again you [can] filter them out by component. If for example you created and assigned a test set [to] a given component and Which in this case for example? We we have some test for our ui or for called the course of the system and If you want you can even analyze also that state results introvert test it each test set for a given Barcia and what this does it will take into account then the Executions that you have for all the tests let make part of the test set for the version that is specifying the Lois’s version ok situations Shows you a list of the [old] executions that you have for which person for them all and the portions of the systems were they were executing and the revision of the the code [Vote] was exercised and you can see also that have a quick overview of the overall execution status of this of each individual test execution You can also consider a customize the layout of this [see] screen

[okay], the test plans tab is in fact quite similar to the previous one and It shows you the list of the other plans that you have for Your versions of the system, and it gives you also a quick overview of each test You are able to filter this out by by a given version of the system or by some workflow status for example Now for me. What were the the most interesting tab for me is the requirement coverage tab? Why is that because I? X-Ray Ism. Is [excessive] with requirement coverage, so and hearing the requirement coverage and tab you can see quite, [easily] and The status of all your requirements, so in this case. I’m showing all All my requirements that are part of the system. I can filter the requirements that are shown in my graph and in this case I’m grouping them by priority I could for example group them by priority and What this shows to me in a very efficient way is that for example? I have 19 major Requirements that are [okay]? Or and I have for example 17 requirements that are not okay? Question [three] into RL of the season so I can analyze my requirements in different for different person so I I can Get the same analysis done being done for example for version 2 [the] [role] of the system or for version 1.0, and what this does it takes into account the test execution that we have for version for the given version that I specify In this option I can even analyze the the status of our requirements and by and By a test point so for example if I sled up our test plan I can see that All my requirements are being covered and Just one requirement is in fact being covered and it’s [ok] This is because our test one hungry contains tests that validate this specific requirement If I click on each [one] of the bars, I am able to quickly see the requirements that compose This little bar [chart], and I can see for example that for this specific Requirement. I have three tests that are covering covering it and [open] and now my three tests are passing so the complication of the requirement is 100% and let me just show you an Another type of chart, which is then the damaged 3 shot? Let’s once again. Analyze this for an for version 3 the role of the system and basically what this chart shows you is the dilution of your requirement coverage through time so if all goes well for example here in the 15th of December I have 17 requirements Okay, and if all goes well the green the green bar should go absolute time and and you should have Like one other percent of your requirements being okay? okay, let’s come back to our other cover chart just to show you how another nice feature and then trying to be as fast as Possible let’s add a little down on the measure requirements that are filing [I] have seventeen of them if I click on them I can see them right away and You can see that one of the requirements that is being considered is an epoch and this this is basically because a x-Ray as the notion of parent requirements and sub requirements, so it even understand the notion of a [epics] and user stories, so you can see that for example if you are covering the individual user stories the status of the happy reflects a self having in mind that you can even define your custom relation between a parent requirement and [a] sub requirement in the structure of

X-Ray [ok] and Now let’s go to Refer to them to our our point Eight point, which would be the different possibilities that we have for it making reports So let me show you a dashboard that I had built already and you can see that the the charts that I’m showing to you the containing there and the [one] [on] stages of your requirements they can be included as Jira gadgets in Your own zero dashboards You can also see that [for] example You can easily make a list of your requirements containing the requirement status in This Max in fact use of the filter results gadget that comes with Jira it since X-Ray add some some fields and to the to the For example for to your user stories [let] such as [a] requirements ages you can include them in the list of issues You can also make for example a report part and by grouping of the tests by component since the Component is an attribute of the test itself You can also make for example a pie chart containing That briefly shows you the the all the test runs that you have a group of divided by the status of it finally and Even the the test set and the test is occasions And they’re the test they have specific custom fields for example here the test set status is a custom field that we have to do test sets that quickly allows you to have a glimpse of the the [tests] that make part of this test set and for example you can have a also a List of all your test executions and show you and show them and show their test this occasion status related which one with each one of the [best] execution ok so let’s go to to our last point which is will be the integration between exporter and X-Ray and for that let me go go once again to [our] requirement coverage a panel and let’s Choose some other requirements here that are passing let’s go to the zero strain we’ve containing all these requirements and How can we make for example? requirements traceability Matrix, so in exporter and I can have and I can build a template a word on an excel template and For that for that exporter as a building store [web] with three templates that you can reuse We can even build your own for example You have a specific requirement traceability Matrix report That you can use in order to build [a] some some nice word document, or PDF document containing your traceability Matrix report so let’s come back to our selection of requirements and Let’s make that so from the export action I can recall exporter I would select a template by selecting the requirement traceability matrix and selecting the output as be a word document and Let’s export that And now an exporter has created for me a [word] [document] Okay, you can see the word document And it contains a list of requirements that stages of it the link of tests and [lipids] the effects the beauty [of] the using exporter to make your own Soul customized reports is that you can control accustomed eyes the layout [of] it So in fact there are multiple to reports that you can find and in the template store Even for an excel that allows you to talk [to] [any] group the test runs in different ways

Okay Now just for the last topic I will pass the ball to visual and [joan] will give you a glimpse of them another thing that we have Thank you So another very important thing that you [Ii] think that it’s very important in case you want to ultimate has all these process of this this of your test management is of course integration with any kind of Continuous integration platform so in our blog we do have a tutorial That explains you exactly how you can how you can integrate x-ray with for example this in this case Jenkins But you do have [another] also another example with specifically with bamboo, so this is something. It’s also very important In terms that you want to integrate all [these] information out So what will happen [is] that you will run a job in Jenkins? Then will then collect information that you have in X-Ray it will execute afterwards [a] cucumber, and then of course Import back the results to X-ray so you can have all these buses Completely ultimate eyes of course in this new [Deco] documentation you do have a lot [of] information not just about the tool itself but also all the new thing all the new features [in] our rest api So all that information that you can find here you will have completely available or you can get all that information And this is actually a Brand-new documentation so we Made it so that would be way easier For you [to] go in and get the information out [of] it so as fast as possible and more complete as possible Yes also very important that’s good that you mention is essentially that the recipe is completely built in in the [India] done so as soon as you buy the license you [will] be you’ll have also included the rest api completely free and included in there in the license [stack], so in terms of the of the additional resources that you can find In our in our not just in our [work], but in our documentation and also in our website All the information you will have it here As I [mention] already in the documentation you will have also our website with more information [our] system up extra [does] not exporter Also, very very interesting that our blog will try to populate it [with] with some more information not [just] about new features of both Tools, but also new articles with with new situations also Some some concrete examples that could be useful for you some use cases as well And that that will be also something that will go on in the future of course Another situation will be our YouTube channel will not just update this with two webinars that you’ve been doing during this month Would [you] left some other news there’s not just about the tools, but also some some other other Curiosities that you can find there so that is something that you should check out afterwards [and] [of] course in the end Even if you are not able to to run and install X-Ray in your Jira in your test Jira because you are I don’t know you don’t have access to it [or] in their permission to do so you can [use] our Sandbox so in our Sandbox you have You can use it so it is our own Sandbox [tier] instance and from there. You can not just Try out X-Ray, but also [export] and use it as much as you can so no problems on that and you’ll also have admin levels you can as a summation in the beginning you can configure your issue Tabs and configure our Requirements, and your defect is back so so everything can be configurable there you will have all the permissions to do so so [that’s] all that information. I’m also told that because it’s been already a quite long quite long webinar We do have some time some very short time for the Qa session Will give you an about 30 seconds so you to to get get on your your questions, and we will try to answer them during this time period If you’re not able to to Write down the your question of course we can answer word squeaking afterwards contact as and go for sure Be more than glad to help you out on that all those queries So let’s give 30 seconds to to check out the questions. [it’s] time for you to write them down Okay, so let’s start with with some of the questions so can the test, we’ll use it

example functional test for a process that typically use regression tests in future releases Yes, a test can be uses so as I said initially the tests are like in fact like the testing [plane] so even ever you create a test Execution and an instance [II] of them now if the test is copied internally we recreate [the] test run, so [you] can reuse the same test between different versions that you this is [that] you may want and if you are going to to to do a regression testing a for example you can make a test set [without] the [test] slippery that previous requirements, and so and that would be the [best] way to to work things to make a Specific test sets that we’re going to identify the the tests that should be considered as regression testing So can you demonstrate how to is equal to [phim] test for the same requirement for different versions? well that In fact and in order to do to do that you can You can basically you can create a test execution just [a] second you can create a test execution for example and say that it’s for some other version of the system, so you can create and the different Classifications as you want which is you can use acquit them on different [portions] of the system? and for that, you [just] need to specify that in the fixed portion of the of the test execution and another question is how is that despite in their current [ages] out the story so the requirement status under the user story it shows you and so this is a custom field and The exact behavior of this field is configurable in the [Shinji] and x-Rays administration basically chose you and Then the status of this user story for example for them for the earliest and release version of the system it you can you cannot have a Different customer than one for join of this specific result for rushing to go and Follow other [versions], so but you can [customize] the behavior this specific field so this is just an Andy field and To have you and a quick Way [of] finding out the status of your user story for the passion that you are? from most probably working on Can we have more columns in a test details section so then? yes in fact in a in x-Ray administration you can define layouts of the of the many of those sections that you that we have so just to show you a Few seconds that we have a default columns layout which Basically allows you to customize the layout of the summer the sections for example that that’s that appear in the tests at Issues for example, and this is like the default the default columns that show But you can in each one of the issue types you can customize the the columns that you want to appear Okay so I think for [now] We we are ahead of time, but [uh] furthermore any questions. I will give you feedback by enough So it’s it’s really important because we are already running out of time I will I also wanted to show you just by email so you can prefer Contact me in case you have any question all the questions that are posted here will contact you afterwards sending an email Replying them to you. So we have quite many questions at the moment that we are not able to do it today [but] true for sure contact you by email, so don’t worry

So just post in here contact me afterwards or you can for sure send an email with your questions like I said We’ll contact you afterwards with with not just with we’ll send you with the email not just with the documentation that we share with you Also all the links that we [shared] that in the previous slide but we also share with you the recording so you can just listen to it afterwards, [and] you can serves as some kind of information not just for you, but also for your colleagues at I/o For sure, or are using or will use X-Ray in the Future to fill to contact me. I will be more than glad to help you out So thank you very much for your time here with us. It was really a pleasure We hope that this was a really good session for you to learn some some information that you did in the head at the moment About X-Ray for us it was really a huge pleasure. Thank you for your time, and never have a great week epic testing Thank you very much [mahir]