so welcome everybody um this is our uh 27 platform Academy session uh today I am being joined by uh Dinesh and Edwin for uh product managers for automated test framework which is very exciting I'm looking very much forward to this session uh my name is Lisa hornstein I'm an outbound product manager for the now platform more specifically workflow automation I work Adam and the other colleagues who joined us as panelists as well so I've been working with the now platform for almost seven years and I've joined service now almost four years ago just thank you so much Dinesh and Edwin for joining us today please give a quick introduction to yourselves and then I'll do a small bit of housekeeping and um then we can get started with the session take it away Dinesh sounds great hey everyone how's it going my name is Dinesh kakamani as Lisa mentioned I'm one of the product managers here at servicenow uh I've been at service now for about a year now and the two areas that I own are ATF and upgrades so today I'm super excited to talk to you guys about uh the new enhancements that we pushed out for ATF um a couple weeks ago and I'm also accompanied by our engineering manager Edwin Edwin I'll kick it over to you hey everyone um my name is Adam Coronado I'm uh the manager for the new antimatter team or ATF test generator and Cloud Runner application I've been with the company for almost eight years but uh start as an intern so yeah it's been a long road oh that's so awesome thank you too so much for being here a couple of housekeeping items I can see the first questions already coming in so please let them uh come in I'll kick it off over back to you Dinesh thank you everybody right and yeah let's keep this um session super interactive so definitely feel free to ask questions and you know um we can just have a conversation so as always the Safe Harbor statement applies please do not make any business or purchasing decisions based on what you see here today so what we're going to do is we are going to start off first talking a little about ATF I know a lot of you probably are familiar with ATF but always good to have a have a refresher so what is ATF ATF enables you to create and run automated tests to confirm that your instance Works to after major changes or releases so what we're really trying to say is that we want to help you push changes out to production faster and validate those changes in production whether you're pushing changes out on a weekly basis a daily basis or you're pushing out changes on the upgrade cycle we really want to make sure that experience is as seamless and quick as possible so that's kind of the goal of ATF so why ATF the problem we're really trying to solve with ATF is avoiding having to do manual testing manual testing consumes roughly 50 of time and resources on upgrade obviously manual testing is slow it's um it's very dependent on on the the resource customers typically spend about one to five months four major upgrade upgrades when doing only manual testing and because there's just a lot to test and to do it manually is challenging you need to have you need to be very organized around your Excel sheets and all the test cases and making sure the appropriate people test the appropriate flows and then different people can interpret the results differently so it's really hard to manage and coordinate between manual tests Mana tests also result in testing that isn't consistent and it is somewhat error-prone um so this is kind of where ATF comes in with ATF you could leverage quick start test and reusable templates so along with ATF we deliver a bunch of Quick Start tests that could serve as a launching Point um to to your ATF experience so if you want to test a specific area you can look at your quick start test copy those over modify them and then and then execute those tests ATF can automate manual test cases reducing the upgrade test burden so instead of having a QE resource or an NGO resource manually go and test specific changes you can automate that and you can make that part of your CI CD flow or you can make it part of your regression testing cycle the tests are obviously reusable so as soon as you could use it multiple times and it's literally just clicking a button you click a button you run these tests and you can see what the results look like and it goes to the flow that's clearly defined and there's there's it avoids user errors because it's a system that's going in running these tests going automatically as opposed to a physical person going running through a specific workflow it also provides transparency across the organization different users and different people in your organization can now come and look at a test and say okay well is this the right business flow does this follow the right logic and they know exactly what's happening you can see what steps have failed what steps have passed what tests have passed as well as like doing the suite level so it really does improve the transparency across the organization so when should we use ATF use ATF for functional testing of business logic so if you're trying to test you know business logic within within your applications or specific flows that's when ATF really shines browser compatibility testing and regression testing so it's not recommended for do not run your ATF or other functional tests in your production instance we don't want to create any unnecessary noise or change any production data it's not intended to test every single UI component as we mentioned it's kind of a business logic testing tool and it's not really intended to test UI an ATF is not a load testing of performance testing application so we don't do any type of load testing or performance testing in ATF as of today uh one quick in into this because people are starting to ask about some guidance and best practices around building tests um we did have a couple of sessions on ATF among others with my colleague Daniel who's also here is the panelist uh last year and I will post the link to the past Academy sessions chat so if you're interested in Basics the best practices the guidance and recommendation beyond what Dinesh shares today please check out our previous sessions on it yeah thank you Lisa so what can you test with ATF you test a variety of things on our platform with atfu test Forum service portal service catalog custom UI rest apis and the navigation bars we are continuously making enhancements here but these are the the core areas of where ATF can really help you with your automation um so with that that quick primer on ATF I want to talk about what have we released in ATF to make your testing experience more seamless so the first thing I do want to talk about is test generation so why did we think about test generation well there are three main pain points associated with ATF today and we're really trying to address those pain points the first pain point is there's a learning curve associated with ATF in ATF you really need a specialized person to come in learn how to use it and then once you learn how to use it it takes time to author those tests you have to go and figure out what's how to create all the different steps you have to um you know do all the specific configurations so it takes time to author those tests as well and then once you author them and you learn how to work with the ATF you have to maintain those tests so anytime you make changes to your production instance or anytime you make any changes at all you need to make sure the appropriate tests reflect the specific changes that have been made so that failing or passing incorrectly all this contributes um to obviously the development time in terms of you know when and how frequently you can do automation so that's where test generation really comes in test generation aims to solve a lot of these problems um so starting with the learning curve with test generation now we do one click test generation so you literally just click a button what we do is we take a look at your instance look at the activity on the instance and then we'll automatically generate regression tests for you with the click of a button so you can imagine that you you have an instance you have your test Runners to set up you hit I want to generate my test you come back in the morning and you'll see a bunch of tests that have been generated and those tests that have been generated really represent a snapshot of your instance at that given time so the idea is you generate your tests before an upgrade and you run them you see what passes what fails then after your upgrade for example you could run the same Suite again and you can see what fails and resolve those issues um so it's really powerful in the sense of being able to being able to author and get a bunch of tests in a very short period of time without using any QE resources obviously in terms of authoring there's really no authoring required you're just hitting a button you're doing a little bit of configuration at the beginning you hit a button and then you have your test and lastly test regeneration is completely free so you could regenerate tests as many times as you want so if you find that you've done a bunch of changes and you're the test that you generate initially are no longer valid you don't need to go in and modify those specific tests you just instead go and do another regeneration you go regenerate um regenerate the test again and that will give you a fresh snapshot quote-unquote right of how your instance looks at that given time and you can use those tests going forward so you have free test regenerations and it's really easy so um now with if you download the application from the store under the ATF section you see this test generator option and we'll obviously demo all this in a bit as well Edwin's going to do an awesome demo for us and do a little Deep dive um and then you select a test generation user and then you just you generate your test so you have the ability to provide an email test generation varies in terms of how long it takes to generate these test Suites so you can provide an email address with and that user would get an email as soon as a generation has been completed you hit submit and then we take a look at your entire instance and generate those tests if you don't want to generate tests across your entire instance you'd also go to the advanced section and then select specific tables incident for example and just generate tests for that specific table so in terms of availability it's available in store now for customers on Tokyo patch 2 and Beyond it's not available for on-prem customers so you can go to the store right now and you can actually go ahead and download it and play around put the link in chat so we have a question regarding this uh maybe you want to take that live what data does the test generator look at to generate the tests and how do we ensure a clean generated is it best clone from production first yep so uh definitely flown for production Edwin can speak on some of the data aspects as well but um clothing for production helps the more data that's on the system the better but I think we can successfully generate tests with 50 I think 50 records and Edwin please correct me if I'm wrong there yeah so uh the data that we look at is for the past six months so it's based on like a role combination so um if we look at um like the ital role right we would um graph some some of the we'll discover some of the users that have those roles we would then impersonate a user with an itool look at records that they have modified or updated or inserted in the past six months then we extract those values we generate a test that basically mimics that user going through it and ensuring that um State visibility matches with the expected um that the field after clicking insert right that the fields match what the um the expected record looks like so it takes for it tests for correctness so it's uh it's ensuring like that the test that we generate they're passing so to kind of answer the question of um how do we know that they're working on something like that we we actually run the tests and they won't show up in your generator tests unless those tests are passing so we look at the we discover the use cases we find the sample records we make sure that the functionality is there that the fields match that the visibility matches that after inserting the expected values are there if all that passes in our tests then we save it in your generated test Suite awesome thanks Evan can I have one thing since we're talking about the availability um Dinesh I just want to make sure we're confirmed too so this is available in the store now for all of our commercial users not on-prem is it available for regulated markets no it's not available for regulated marketing not yet for that so that that's something that's that's coming but for all our commercial customers we're all set you can go do it while we're talking yeah that's right but that if you're in a regulated market or federal customers it's not available yet exactly um looks like another question here what kind of tests test generator creates it asks for a table as input does it create tests for all customization and typically include uh yes so we do create test for all your customizations um and oh yep so we do create tests for all of your customizations on the specific table we'll test the entire workflow what we do is Edwin kind of mentioned alluded to earlier is we'll take a look at the users that have specific permissions for that table and then we'll do validations for those users and check the security as well we generate tests for forms and lists today we do want to expand scope to expand to other areas which I'll talk about in the roadmap section but we generate tests for primarily just the forums and lists um so moving on to the cloud Gunner and parallel test execution so what are the current test execution methods today we have two forms of test executions we have the Headless browser and then the test Runner so for the Headless browser for those of you that use it it's a customer hosted solution so something that you host uh the customer spins up NXT tests on their own VMS right so you're you're spinning up your own VMS you're spinning up your own containers it requires some setup on your side but the benefit is you don't need to run the test locally and you can you can offload the processing to the Headless browser outside of your outside of your local computer there's some maintenance required you got to maintain the entire configuration you got to maintain the setup and the all the infrastructure that's associated with this then we have the task Runner um so this execute tests locally there's no setup required but there are some challenges with scheduling tests because it is running locally right so you can hit uh run with the the test Runner and then the test will open up on your you know on your local computer and then it'll start executing and the computer must be up and running for the test Runner and things like that so what we did is we noticed that this was a huge pain point and we came out with the cloud Runner so the cloud Runner allows you to offload execution of tests to servicenow infrastructure so it's kind of taking that concept from The Headless browser except eliminating the entire setup required so now you need to do you don't have to do any setup as long as you have the application you can offload all the processing to servicenow um we also as a part of this release came out with parallel test level execution so what this does is um right now before the release Here you can run Suites in parallel but now what you do is you could actually run tests within a suite in parallel as well so you can imagine that could that could help with your execution time then help with capacity um and at what the application you get two free test executions so that means you can run two tests in a suite at the same time so hopefully reducing the entire execution time for that Suite so if before your Suite was running taking four or five hours to finish executing hopefully with the parallel execution it completes uh much quicker and there's obviously scheduling a little bit enabled on the cloud Runner as well so with this you hit the run test button so once you have a suite the cloud Runner will let you run any test so it could be generated tests or tests that you manually created yourself as well you hit the run test button and then you have these start a new test Runner option and then you have that new option that says Cloud Runner so we kind of guide you through the the steps here in order to make sure that you can use a cloud Runner so if you if we if you don't have the application installed we prompt you to say hey you know you should go download the application from the store once you download the application we say hey you know what like you got to configure the admin user before you can do it and then once you configure the admin user you could select your Cloud Runner option here and then you hit your run test and then the test run right so you can imagine the entire end-to-end flow now as you could say I want to come in I generate my test okay my tests have been generated now schedule it on the cloud Runner and then it's almost like a full end-to-end automation of authoring and generating tests to execution so like I mentioned you get two free parallel executions with the download with the application download if you find that you're um you know you need more capacity say your Suites are taking you have a lot of Suites or your Suites are taking like 15 hours or much longer to execute we actually have an additional package that's available for purchase so you can purchase five additional apparel executions as well giving you a total of seven so that means you can run seven tests in parallel within a suite as well this is also available on on store uh now for customers on Tokyo patch 2 and Beyond uh same requirements as the previous one where it's not available for federal customers so it's um yep so definitely take a take a moment to download it and let us know what you think any questions on the cloud Runner there are a couple so one question I um already answered in um the Q a panel but just to uh make this very clear so how does the cloud Runner work with headless browser it doesn't it's kind of parallel technology so you can use either the Headless at a browser or the cloud Runner or your local Runner depending on what your current needs are it would do the same and that would also fit the other question that we have um so does this also create the screenshots yes it does create screenshots uh what else do we have here so we have some more on chess creation but let's go with the um Cloud owner questions can I schedule sweets on cloud Runner yes you can it's scheduleable awesome um do you have anything else on the cloud burner or do you do you want to go through the rest of the question um I was actually going to have uh kick it over to Edwin to do a demo yeah how everything looks maybe while you set up your demo that was one of the questions just now will there be a demo on these yes just now and while you set that up one question in chat is is that will this we be available on pdis do you know that um Edwin it should be on pdis right the on personal developer instances yes um I I want to say 90 convinced yes but the mtlers might be a problem for uh okay for um pdis we'll get that object I'm gonna go check that out thank you awesome so look good let's go ahead I love the questions keep them coming it's awesome absolutely great yeah awesome so everybody can see my screen right yes first of all I did want to point out that it's right here shiny looking good I got to download so two point uh Tokyo patch two and uh onwards I just want to kind of show that we're live there and um right here I have an instance running Tokyo patch 2. so I'm going to start with I guess the uh the probably the first step that a lot of people are gonna go try out is um not having to sit down in their computer while this test is running or not having to set up their own hosted um browsers so we're going to go to a suite that I have created so I'm just going to ATF I'm going to my Suites and I actually created one called parallel Suite and I'm going to go ahead and open this suite and in here I have two very basic UI tests I think these are actually out of box so if you have a fresh instance you would see these um let's open this up this UI test just some person into user open some forms at some values and then submits the form so very simple so I'm going to go back to my suite and now when I hit this button right here you'll see that we have two options now we have a test Runner which is um in your browser or the cloud Runner right so this is a new um app the ATF test generator on cloud Runner so I'm going to select this right here I'm going to click run Suite so now as you can see these both um come online now this starts talking to the back end you know and acquiring the resources getting um getting a runner getting a a browser and we'll let this go for a little bit okay so one of them started now the second one starts so you can see they're both executing parallelly so sometimes really neat they're both executing parallely they're taking screenshots and I think someone asked that and we go to the results so now we have both results right here so very seamless um you don't have to sit on your computer looking at your uh your Runner so as you can see the screenshots are here as well for every step we take a screenshot that's I think we have enabled that by default you can disable I believe but it's enabled by default so we have the screenshots now for the newer functionality I'm going to go ahead and in my left navigation bar where I guess since Polaris is the top navigation I'm going to go to um cloud uh test generator I'm just going to test generator right here so the first sentence first time you install the app actually I'm going to show you a different page in fact I'm going to go to select Cloud user so this is the first picture you're going to see once you have installed the app you might see a little modal that says hey we're still configuring your instance there is some work that happens in the and when you install the app uh shouldn't take too long but there is some work that happens to set your instance up with certificate based authentication so um once that happens you'll see this field is going to be empty you can type in and it's gonna you're going to select an admin user so it's an admin user once you select that you click submit it's going to go ahead to our backend and just make sure that yes this user can log in successfully and as you can see I've selected system admin and it's been successfully validated so once you've done that now you're ready to generate tests so I'm going to click here to go to my test generator page so you can click that button or again you can just come to the left now and select test generator and it takes you to the same place right here so if I were to just submit it as is it's going to go and it's going to generate tests for all tables so all tables that'll take a while it will take a while exactly so depending on the volume of data you have um it can take like from hours to days to possibly a week so this is um a slow quote-unquote process because it does have to analyze a lot of roles a lot of data it has to find a lot of Records it has to stand up the browsers in our backend right we we're standing up browsers and we're logging in and trying it as a user we actually do so all that process is uh is a little bit time consuming so it depends on on of course the volume and data you have on your instance so if you care about most more specific tables though um The Nest was touching this earlier that you can click the advanced um toggle right here the checkbox and now you can select specific table so let's say I wanted to do something like incident like I'm really I really want to create for incident first just type in incident um and you can here you can add your email so if you could put your email in here then you just get an email at the end notifying you that it's complete so for now let's say I created this I submitted it let it run um so after a few hours on this demo this is a um out of box instance so there's not a lot of data in here so after a while um we have this generated suit right here there's 86 tests in here um as you can see it's it names them with the um the Rope right here and some other views so like the default view so if I open one of these for example you can see that we're impersonating we're opening a form uh we're we're doing some field State validation to make sure like oh this is visible it's not visible right um and then for some of the larger tests uh I think some of the incident ones for example you can have up to the generator can generate up to like 80 steps in one single one single test so it really varies on the role and the different things that we're uh testing for and just uh just one thing I wanted to add there Edwin is um one koala is as tests are being generated uh the cloud Runner gets queued so you know if you're running a test generation and you say you want to execute test in the cloud Runner as well those tests will get queued until generation has been completed correct yes thanks so much yeah no problem Dinesh can you tell us something about Evan about the um admin user that was set in the cloud cloud user settings is that does not need to be a real person or would a dummy uh user work what is um what would happen if that person would leave the company what's your recommendation for this yes so the so if we go to select Cloud user so it's any user basically with the admin role um you can create a like a fictitious um a record for fictitious user and it's fine as long as they have the admin user um if that user gets disabled or the admin role is removed from it um your test will automatically like fail and you'll see some login errors so it should be fairly easy to figure out oh you know I need to go check my my admin user and maybe change it um sorry here for example if I select fretludy I can submit it and just come in and resubmit it and it'll go ahead and authenticate the user and make sure it's it's good to go do you have any information on when the tests are being generated and say there would be different tests for certain roles um is there a way to add impersonation to those generated tests to make sure that one Suite would test in the context of one user with certain roles and one Suite would test with another does that is that being generated yes it's generating for different roles and it is impersonating the user that contains those roles yes yeah and this Cloud user is just kind of used to generate the test itself right so what we're doing is in order to even generate the test we use this user to kind of go into the instance and understand what activity is happening generate those tests but if you actually look at the test we do impersonate like the various users and go through the appropriate flows and and that would also work for scoped apps and scoped app rules roles right [Music] anything this user can see right so that's why admin admin role is pretty normal is what we'd expect here if people see the data the only use case I can think of is if it was an admin is if you had data that admin couldn't read that then you would probably need to change right if I were doing HR testing would I need to change this to a user that had access to the HR data yes that's the use case can you repeat the request sorry yeah so so generally like you mentioned that this user is going to have admin access right the admin role but the use case where that's not true would be if admin doesn't have data as Dinesh said we use this user to go in the test generation to interrogate the data to figure out which test to generate yes it's s impersonate exactly this user has to have access to the data to read to figure out what the test should be so if I were going to test HR data that admin the admin role cannot see it's not going to generate a test for it if I use admin I'll need to come in switch this to my HR admin generate my test for those tables I mean generate them all but generate tests for those table for those HR tables then I'll come back and switch it to my normal admin user kind of leave it back in the general use case does that sound right to you Edwin uh so this user always needs to have the admin role for the use Keys Discovery and for some other like um coordination we do between the back end the uh the roles for the test generation right we get this user is going to gather all those roles and generate for each of the specific roles and then when we generate a test it's going to use a user with that role to log in and actually do the testing so this this kind of always needs a new user with an admin role here the cloud user okay so in that case you would give the cloud user the HRM role and the app yeah so and and Adam like one of the other things we could do is it's possible to create a different role that has the admin role as well as the roles required for HR for example right yeah and to go with that so if we have that user I mean one of the important notes Here is that I'm not storing a password right so this user I'm going to create a dedicated user for this that has admin and HR admin which is something that no person actually has but I can generate it it's got to be unlocked it's got to be active but nobody needs to know the password so like a scheduled job I might be creative create my test generation user give it admin give it HR admin or any other uh scoped app admin that I need to have that admin doesn't have access to type in gibberish for a password that nobody knows I can use that user nobody can log in as that but it's it's all it's all set from there yeah someone was also asking if we could see the progress on this and you actually can so if I were to submit it um so let me let me go ahead and do that let's go ahead and go to the test generator and I'm going to just submit one for all so I'm going here just I'm just going to click submit it's going to set up the test Generations it takes a little bit but it's coordinating with the back end inserting all the jobs that it needs to but someone was asking if we could see the progress for this once it's going and progress is basically for anything going to our to our backend so if you come in here this is going to take you to your generated test so you'll see you want to assess ATF generated Suite um but you can also come in here and under ATF you can look at Q so if you type in q under ATF you'll see browser orchestration queue right here if you click this and you see a nice progress bar here that's telling you where it is oh that's nice so even for the test user right here so earlier you saw that I Said Fred Lodi earlier this was it right here and you see a little info right here oh the test user was validated over here too for the test runs we see they're all complete so this one's going to start moving along once the generation starts um so yeah you can definitely just go again type in Q and under ATF Administration browser orchestration queue right here yeah and one thing to call out on this is that the progress won't reflect right away um so you know you might hit test generation and then we wait for the test case Discovery to finish and then we start updating the progress so just kind of like a warning there is don't don't worry if it the progress doesn't update right away as soon as you hit test generation might take a little bit of time before you start seeing this progress bar progress we have more questions about the test generation can it create tests that um use components like spokes so provided those folks are connected to something that provides a valid response um before you answer I would put in one thing um in general or creating tests we would recommend to test the outcome so in this case if there's a spoke that returns a specific value I would expect a test to test for the outcome so we wouldn't go ahead and test if a Spoke has been called but we would do some inputs and then check if values change based on what we expect to happen based and I would guess the generated tests do some yes exactly we don't take for like we don't really test for um for like positive assertions it's more of like hey this is the snapshot this is how it looked um I'm expecting this it's not really about oh did this happen like did I actually trigger something that's more of like what you're saying if what I trigger returns some data I'm I don't really care about the previous I just care that the data is there does it look like that yeah and Edwin uh maybe a good thing here to also show real quick is how do we cancel tests that have been pattern generation in case someone's like I want to really execute my test you know I don't want to wait for Generation to complete yes absolutely that's a great question yeah especially test generation like we're saying it could take up two weeks if you have a very very large instance so if you feel like you messed up and you may want to just create for one single test uh one single table you can definitely come in here click cancel job that's going to go ahead and talk to her back and tell it hey you know what cancel these tests um and it'll also cancel this job the execution tracker so everything's gonna get you know so any other questions on the demo I think there's one question also um on this generation is the data for the test so that the instance that is creating the tests is that potentially storing any data uh no we're not storing any data um what happens is we have like an inso we have our Cloud Runner the cloud run reaches out talks the instance we open up a browser so there's going to be a moment where we have information about browser that we open up in the sessions but as soon as that browser is terminated we get rid of all the data so we're not storing any data and all this is outlined in our T's and C's on the application as well so definitely please make sure to have your legal team review the t's and C's and and make sure it aligns with the policies in your company another good question around test Generation Um that I've quite asked myself to is will there be an option to select multiple tables or maybe what I think would be useful is picking a scope and then creating tests for one scope exactly that's uh definitely something we're thinking about actually Adam gave us that idea as well where it's like hey I want to test generate tests based on an application so we we brought that back to the team it's definitely on our roadmap so it's not just individual tables you can say I want to test this entire scope and then generate test for that's code so not yet but on the roadmap awesome thank you um one more uh somebody uh noticed that the generated tests with a hard-coded user uh did all steps including opening something and checking policies but it didn't submit the form or created steps to check what happens after the workflow I would guess that's probably based on the data that was provided that the tests were trained on right yes yeah because some tests can be testing just um for changes like invisibility and stuff and the other other tests could be testing for uh um after insertion and we are impersonating a hard-coded user um I think someone was asking that and I think we're going to take that feedback I think it was Patrick I remember someone was saying that um if we generate a dummy user as it's usually um best practice for ATF so we're gonna take that feedback and we might add that as well just so instead of using an actual hard-coded user for to impersonate just create one with those specific roles sounds good um is there any best practice around maintaining these apps should they be pushed so test push to production Etc um in terms of Maintenance it's pretty obviously we don't recommend running any of these in production whether you want to keep in production or not is completely up to you based on your um your flow your your journey in terms of like upgrades and things like that um but in terms of Maintenance yeah you just regenerate right so like you don't necessarily need to maintain these old test Suites you can as soon as they become stale you can just regenerate the test Suite that is uh the perfect um uh segue to the next question can you show the Regeneration of tests and does it overwrite any custom changes to a generated test can you specify which tests are read oh so when we do regeneration we don't modify the same Suite what we do is we create a brand new suite right so a brand new suite that represents the new new snapshot so we're not overriding the existing Suite so we're just recreating all the new tests and then you can deactivate the the ones you don't need right you could deactivate the ones you don't need anymore yeah um more questions about the promotion of tests so um are we as the idea to promote those tests from Dev to test to another subprod instance where you are actually running the tests or upgrading yeah it kind of depends on your testing life cycle and your testing Journey like where do you where do you want to run regression tests and where do you typically run regression tests um so wherever you typically run your regression test that's where you'd want these tests to exist um so these again are focused purely on regression for forms and lists more questions does the test narrator breakout tests but different views as well as role does it take foreign views or List views an account no I don't think it does Edwin you correct me if I'm wrong um it's just the primary view right now I think it does the default view so if let's say a user has like the ESS view right so I'm looking at literally one right now actually let me show um right here so whatever is the default view so for example this guy right here right incident Joe employee this is the user's default view so the user's default view for most of them is default view but for example Joe employee is ESS so it's testing against the user that specific users um default view you know while you're I was about to say while you're showing that we have another question for a small uh for something to demo can you uh show how to schedule a suit we're using the runner how you pick the cloud runner for for the schedule test Suite yes I love this part of the demo yeah right it's like how hey can you can you demo how to do headless testing hmm Daniel's favorite thing to do yes hey can you demo automation can you show me how RPA works so I'll create a new one here so it's very simple you it's already checked by people by the way because we want you guys so it's already it's basically the same that you're used to it's just now we have this new um checkbox that you run in Cloud so if this by the way is checking it's going to check if your um that cloud user is set so if for some reason you see that this um checkbox is unchecked and it's read only go ahead and check your Cloud Runner user because it's most likely doesn't have the admin role anymore or it's not set so we do check for that but basically for example for an existing one right here my new schedule I already have a suite here it's a mixed suite and just like a regular ATF Suite but uh I have this new box here and that's that's literally it that's all you have to do yeah and Edwin our schedule test blocked by um block by generation as well yes yes so those jobs if they're in the middle of something it's gonna probably finish what's already running in the browser but then it will it will basically pause and test generation is gonna proceed since it's much more um a resource intensive test generation we let that run um separately and um isolated yeah and one of the workarounds too is when you have test generation is you can just say okay well until my test generation is complete I'll use my headless browser I'll use my local test Runner right so you can still execute your test using these other methods it's only the cloud Runner that's going to be blocked for uh test execution that's good you can still use like if you already have a setup uh with the virtual virtual server uh that you've been using before for your scheduled uh test Runner so you can still use that just as a backup and there is a difference too right um do we know what browser we're using for the cloud Runner cool so that's Chrome had the scrum so if I were at there's still needs if I was doing some other cross browser testing um and I wanted to use something that was not Chrome yes it's definitely not yeah it's definitely not like a UIA testing like you know like uh uh what is it like I forgot the name but that service that has a bunch of different um browser vendors it's definitely not that right we're just using the browser more to a means and like as a means to an end to check uh correctness that's it so we're not really um running any other browser yes there's uh one more question in the Q a um our generated tests instance agnostics so um will there be any instance URLs I guess somewhere in the test or will they work if you transfer yeah they're they're instance agnostic so if you were to move it though you would kind of need to move it to a clone though because if you do have customizations right it's a certain stat so it's um it is agnostic in the sense that there's no hard-coded values like that but it's relied on the data exactly oh sorry go ahead but we can move from Dev to to test or to a QA instance in my in the stat in the in the normal stack it should be should be okay but it would still be dated dependent so if you had different users or wildly different data it would be uh odd could be odd yeah and one last thing I wanted to bring up about schedules um that's worth mentioning is that if you are going to run test generation it's a good idea to disable uh your scheduled Suites just because um those uh constantly try to insert into our assist trigger tables or our schedule job table so you'll see a better a little bit better performance if you um disable those while test generation is running just as an FYI yeah all right I will start wrapping things up and when I do this I'll start one Poll for this specific session so I'd love to do your feedback on how you like this session um so that we can improve and make things better and and know how you like this and then I have a couple of more slides um to share with you um first of all uh I am so happy to see you all here I've seen a couple of new faces that we haven't seen in the academy yet I just wanted you to know that this is a recurring session a recurring webinar format we usually um run every other week we do have um only one more session this year because in two weeks is Thanksgiving for the US colleagues so we don't have a session then but we'll have another session on December 8th uh we're still finalizing the topic but make sure to follow the the blog that I'm linking here um on the now Community because I will post new sessions um there so you know when to sign up for those uh we have a huge catalog of previous topics around ATF instant scan subscription management flow designer process automation designer and all kinds of other awesome platform and workflow automation topics so I would love to see you back and in this format and I would love for you to check out previous sessions and then a second feedback and I will also put this link in uh in chat in just a second we would love to have your feedback on how you found this session and how you like the community um overall and the um experience of uh learning about this Academy and this Academy session on the now community and how we can improve uh in that in that area as well let me put this in chat uh to make sure we can get your feedback um on these on these Academy sessions and we always want to improve and make these better and more interesting I am very very grateful to Dinesh and Edwin to come join us today this was an awesome session a very very important topic and I'm uh I think this will be one of the uh one of the sessions that get re-watched again and again on the um on YouTube so um thank you very much for answering all of the questions um and I would love to see you back next year when we have more updates to this product right 100 and you know as you guys play around with it if you have any issues questions concerns please reach out to Lisa and she could you know reach out to us Edwin and I am more than happy to hop out jump on a call and help you know get feedback and help you through any issues absolutely so this is about all I have today uh remember to uh subscribe to the community post uh you will get the updates there the link for the recording and the presentation as a PDF will be shared over there as well um and then subscribe to the overall Community um post and as I said the next session is on December 8th and then we'll pick up again in the new year I think that's uh January 5th or something well I'll make sure that I know the date next time all right thank you everybody thank you so much for joining us today I hope you have a wonderful rest of the week and a wonderful weekend thank you bye