hi everyone um we're here with another series for the ATF work through today we'll be going over working with t in ATF and um my name isini and the outbound PM for Elm and I have with me um Amanda yes hello everyone my name is Amanda SS and I'm a technical consultant for impact and a little bit about what we do is we help impact customers kind of get um enabled in particular products of Interest learn things like best practices and also give them a head start by providing them those types of resources that would allow them to do so what's done all right so um next is um the safe AB on notice as usual this is what we show you don't make for looking um decisions based on what we're going to talk about um the next one is um our agenda um we're going to go over understanding ATF test read then we're going to go over the benefits of the death r we also um talk about the test hierarchy and um we do we'll talk about the best practices when it comes to working with t stre then am was tickles through um demo concerning T stre um so understanding so basically um this are structured collection of Tex test cases um or test Su organized for the purpose of testing an application um it follows an hierarchical structure which are going we going to talk about later in this deck um and thisy you can actually ar your place your test based on um how you want them to run or the order which you want them to run there are so many key attributes of the test fit the first one being the hierarchy which I mentioned earlier the next one is also group functionality you can also it also helps you with an efficient execution which means you don't have to run your test one after the order you you can just arrange them in an order where you want them to be around you can also shedule your test TR just like you sheding a typical test so when you have um the shling process in place it helps you also make your work better and faster um so the benefits of test streets are the first one which I said is efficient test execution you can run multiple test similarly with a single b a simple action the next one is a comprehensive test covery if fact that you can actually place so many test within a test means you have wider coverage when it comes to testing application you also get better result visibility and Analysis you can analyze all your test um results in one view because of the fact that you're R them on test you can schedule your test run you can also get the hierarchical test structure which I mentioned then you also have this ability to also manage them in such way that you can copy um test from one um location to another hierarchy within the test itself or you can also add this test by F train let's say for example you you want to only run um all the test out with change management under one umbrella you can use the fter to bring them under the same umbrella and add them to t s so this is thech typical of test Swit um you can see the test S one they only the first test s you have TR test under it then you can also have another Branch under this um the first test Street and also forther Branch down so this is this gives you like a comprehensive um view or a wider core video running your test and having it in automated um so now am is going to go over the the demo yes some of um give us some information and some best practices or tips now to walk test in ATF so I will take that screen share from you okay get right on to the demo um so the first thing that we will be navigating to is the actual test SES module on ATF um so of course you want to type ATF in that filter Navigator I have it favored here but we will let me pin this navigate to that Suite section and this will show you all of the outof Box Suites that are currently in your instance as well as any custom Suites that you may have made from scratch um another way to get directly to the outof Box ones would be to click this quick start suits um but for the purposes of this demo we're going to start with just kind of creating a new one um so I won't worry too much about the names here but you have um or regarding creating a new suite of course you can add any type of test or test Suite inside of um a suite but we do have some recommendations on what types of Suites that we um encourage you to create um so of those would be creating a suite for a particular application um if you look into any of the outof Box Suites you'll see that's kind of how service now has it set up you'll see everything for incidents for example change problem management and things of that sort um so that is one way that you could do that another recommendation that we have is to um create Suites for a particular functionality um so if you have a specific customization um and every type of test related to that customization you can package that into one suite and kind of get more specific with that um so those are just um a kind of EX or a few examples of what types of Suites that we recommend to create um but there are a couple of ways so the one of the things that you can do on this view here after you create your name um is set a filter condition the benefit of studying a filter condition would be let's say for example you have 100 catalog item tests um you can actually set a filter condition to kind of capture all of those tests without having to manually one by one add each um of those tests into a suite just because that can get pretty repetitive and timec consuming um so there are a couple of different um options that you can do to kind of filter that down and Target a specific test but I will also save this record once you save it you also have um a few related lists down here allowing you to add a specific test into the test Suite you can add a child Suite um kind of going back to that hierarchy that we showed you you can have Suites within Suites um so that would be way to kind of add those in here in this child Suite module um the other results here we have test Suites results and test Suite schedules um in case you have any type of running schedule on a suite you'd be able to see that here within the actual um record and manage that but I actually do have one that is already created um but in order to create or kind of manually add that you would just do a new um record here and you'd be able to add the name of the suite um set that execution order if needed or abort on failure um one things about this abort on failure I'll go back to that example saying let's say you have 100 catalog items something that you could do is if one particular test step fails you can just completely abort the entire test suite and um kind of get out of that or you can just skip over it and execute the remaining tests so that's the purpose of this abort on fail your field here so I will go to my um test Suite that is is already created um so right now I have one but then like I mentioned earlier we'll kind of show you how to manually add those um so the one that I am going to add would be this test here and then submit so I will go back let me see and then now that is in here um so as far as the execution of your test um you can either set a specific execution order like was mentioned if you kind of want that um to run in a particular manner or um depending on the available workers that you have in your instance you can also run your test in parallel um so if you do have the available workers you can kind of um run those test simultaneously and cut down on the amount of time that it takes um for you to execute your test and this will be really helpful just because again if you do have lots of test having that client test Runner open um could uh depending on how you have it set up if that client the runner isn't open for enough time for all of your tests to execute you would lead to some failures um so I will click this run test feet button and later on we'll get into the cloud Runner and how you can utilize that but for now we're going to use the client test Runner um and watch this test execute um so the two tests that I do have in this instance um there's some simple portal tests that um creates or submit some record producers um and kind of verify the visibility of that record within the portal and also can verify if they're able to um receive some of the updates so in this case they're kind of communicating with the agent through the portal and then we're going to verify that they're able to see that in the back end that the agent is able to kind of see that and then the second example that I have is it's a pretty short test but this is a failing example just so we can kind of see how to troubleshoot um this one is going to try to submit a catalog item and it is not going to work um and I will show you after this test how to kind of um review those test results and analyze that um so on this other end here we kind of see the status of both tests um you're able to click some drop down see kind of the the status of the um steps as well but if you want to get more specific you can click this go to results button or you can also see it from the tab as well and another option we have would be rerun failed test if you want to only rerun the failed test you would have that option here as well but we will click this go to site results and some of the options that you see here it'll show you just overview of the test results so you'll see um both of the tests one succeeded one failed it'll show you the test Suites results so in this case we this is just one Suite so that's why we're saying ATF demo Suite this one failed because one of the tests in the suite failed um if you do have child Suites for example um and let's say one of the test in the child Suite fails they would also be able to see that information and just directly go into that child Suite um and now this one just shows only the failed test so we'll be able to click on this link here and kind of analyze the results and see specifically why it failed um so some of the options that you'll be able to have you'll see the status here that's red as well as a summary information so this typically tells you exactly what happened but there are some cases most of the the time it's direct but there are some cases where there could be a failure and it's not necessarily clear on what happened um so there are screenshots for example that you're able to add um as well as that debug test step button that we um covered on the last video of the series so I definitely recommend to um review that so you can see kind of more details on how to use that debug test button okay so I will go let me go back to the actual test Suite um so back on that test Suite um if you want to Mark a test as mutually exclusive um so like I mentioned earlier sometimes um or if you do have the available workers your test will run in parallel um but if you have some type of dependencies definitely make sure that you set the execution order but there's also another thing that you can do to kind of force the system um to not run your test um simultaneously so something that you can do let's say I have this test here and if there's a test that I really don't want um to run at at the same time you can set this mutually exclusive record here um add a mutual exclusion and then it would allow you to specify the specific test that you do not want to run um in parallel just to kind of force that in case the execution order doesn't work okay and then the last thing um we did already covered this in the last section um but we do have those schedules Tab and I do have one that is a schedule that is already set up um but you do have the option to add those Suites um in there so I'll just do ATF demo Suite click submit and that would be how you'll add a suite into one of your schedules but that is all I have for the demo is there anything you would like to add so I think you C about the buit um I'll just run with the the what's it called the best practices is also the supp but you said yes nice then I'll stop share and then we have that best practices slide all right so um best practices um what are the things we advise you to do basically and still test R that'll be all for today so um we're going to have this um slide posted with the video so you can get some of this um resources we have on this resource resource page and um we're done right yes all right so thank you for watching as well we are going to add more series to this um work through just so you have um less friction when it comes to adopting e for your doing the test thank you very much you everyone bye