Transcript for "Master Salesforce Flow Testing With Winter '27's New Test Mode": Good day. Good day. How are we doing, everybody? Happy Thursday afternoon, evening slash Friday morning for those who are crazy enough to be joining from my side of the world. Hope you're all doing well. Speaking of my side of the world, I'm always curious, you know, if you can check-in the chat where you're joining in from. It's always interesting, number one, to see where everybody's joining from, but it's a good opportunity to to to make sure that we're sort of all familiar where the chat is. Blackpool UK. There we go. Yeah. So so something I'll point out here. Oh, good. I can see some some... There we go. We got a whole bunch of US, Canada, UK. We got Netherlands. Look at that. All over the shop. No No other Aussies? No other Aussies? Come on. I need to get some more Aussies on these. For real. Alright. So, the other thing I'm gonna point out before we continue is you found the chat. That's great. Just next to the chat is the q and a section. So if you've got questions for me, that you're looking, to get answered at the end, so I've got a Q and A section at the end of this session, just pop them in that Q and A section, as you think of them and we'll we'll jump on them at the end. If you see some questions in the Q and A that are similar to what you were going to ask or you you see and you think, oh, I'd love to to know the answer to that as well, make sure you respond to it. So give it, like, a thumbs up react so that we can sort of filter. If we're short on time, we'll make sure that we're answering the questions that are, you know, the the most popular, I suppose, the ones that that most people wanna sort of see the the, the answers to there. Beautiful. And without further ado, I will jump into the session today. We're gonna be talking about the new flow testing mode, that's come into winter twenty seven. For those of you... Actually, I'm curious. We got the chat open, and I'm running the show today. So I'm curious. Has anybody played with this yet? So this has just dropped in winter twenty seven. Very, very, very new feature. There we go. We got Brandy who has used it already. It is it is brilliant. It's one of the biggest changes that we've seen, to flow testing and debugging for a long time, and I think it's exciting nod to what's coming in the future as well. Anyway, I just wanted to see, before we got started, if anybody had had got hands on. I should have done a poll. But anyway, I'm gonna get into the session now. For those of you who who don't know who we are or don't know sort of where you can find more of Salesforce Ben, you may know us very well from our articles. You may have signed up for the newsletter to be in the... Alerted to those articles when we when we post them. But we also have these events, obviously. You know, we're on the webinar right now. We also have in person events. So TDX or Dreamforce or even world tours around the place, we we occasionally will pop up there. You can meet us in person. There's also a YouTube channel. So that is, where we sort of... We'll we'll we'll create, video content for, for those like myself who who are sort of more visual learners and and prefer to sort of watch somebody talking about something rather than, you know, reading through everything necessarily. And then finally, we've got the podcast as well, SF Ben Insider. So, make sure if you're following us on one, follow us on all. We'd love to be, as much a buddy of Salesforce career as we can. Beautiful. Speaker is me. Apologies. You're gonna have to listen to my voice for a little while. Bit bit of that, Aussie drone, but, you'll you'll you'll get past it. I'm sure it'd be a really good session. So I've been with the Salesforce Ben team now, officially for just over a year. I've been working as a sort of an external for, I think, it's seven years now total. So, yeah, part of the furniture. Can't get rid of me. And thanks, of course, to our sponsor, Tricentis. So before we do dive in, quick thank you to Tricentis, who builds AI powered quality engineering tools. Their AI agents create, run, and analyze tests across the software life cycle, and people stay in control of what those agents do. There's a link to learn more at the end of the session, of course. And with that, let's dive into the session. Now there's a whole lot we gotta go through here. The first one is beta. I'll talk about that in a second. Then we're gonna talk about how you can enable flow test mode. So it's not in there and on by default. You do have to enable it. We'll go and talk about that as well. We'll do some walking through of the Test Mode so you understand sort of what is available to you, and all the different bits and pieces and features. Excuse me. And then we'll go through and we'll build out a test scenario so that we can see it in action. There's some automated regression testing as well that we can enable and we can start putting to use with flow test mode. And finally, we can mock some endpoints and subflow outputs. I said finally at the second to final one because the final one is then using AI, for flow test building. So, yes, we have a new tool. We can go ahead and build flow tests, but we can skip over and get AI to help us, in creating those flow tests as well, which is brilliant. So getting to know flow... Sorry. Getting to know testing suite for Salesforce Flow Builder. Now, like I said, I have... Sorry. My my screen didn't change there for a second. I am Australian, so I've put up a picture of Australia. Now why am I specifically putting up the Sydney Harbour Bridge here with a safety first sign? Because we've all seen Salesforce's safe harbor, slides, and I wanted to make mine a little bit different. So this is a bridge going over Sydney Harbour with a safety first, sign on it. This is my safe harbor stat. Thought we'd make it a bit of fun. This is in beta. Okay? So these are features that are subject to change, that are not readily available as yet or or not sort of generally available as yet. So please keep that in mind when you're making your purchasing decisions. Please keep that in mind when you're sort of building out these different features. They are subject to change. And this is a pretty major feature set, that I do think we will see some change on. I don't. Yeah. Anyway, safe harbor. That's my point there. Alrighty. With that out the way, I'm gonna talk about, how to enable flow test mode. So it's done in setup in process automation settings. If you've ever enabled a new Salesforce Flow feature, this is where you've gone before. So if you jump into Setup and you search for Process Automation Settings, you go to that page. You'll need to control f or command f and search that page for Flow Test Mode because there is a lot of different features you can enable in there. But it's as simple then as enabling that checkbox and away you go. So Flow Test Mode there does support auto launch flows and record triggered flows as well, with more flow support coming eventually down the track, possibly, again, safe harbor. Alright. So in the past, when we've been working with Salesforce Flow, we we build on the canvas, then we click the little debug button at the top right, and you'd be in, you know, you'd be debugging right there on the same canvas. Now Flow Test Mode, because it's such a, rich feature set, it has essentially split the Salesforce Flow Builder Canvas into two modes. You got Build Mode and you got Test Mode, and you can flip between them using a little toggle at the top. Okay? So Build Mode, it's the Canvas we know and love that we've seen for years. You can use this to construct your Flow logic. There is now no longer debugging and testing in that entire interface. Okay? Once you are ready to test, that's when you need to flick over to Test Mode, and the canvas shuffles. The the tools that you have available to you change around, and this is where the new magic happens. So this is where you can create your test scenarios, which are sort of... Test scenarios like a repeatable test that you can either run manually or automatically. We'll get to that in a second. Well, I just saw a comment. Mike Williams, I'm still seeing the title slide. Can everybody see the current slide that I'm on? The Flow Builder build burst test. Yes. Yes. Okay. Cool. No. I just thought before we keep going, I wanted to make sure that I'm not just talking to the title slide. That's good. Alright. You're gonna add your assertions as well to check coverage before you deploy for those automated tests. We'll come to all of that in a second. Let me jump over to what building a test scenario looks like. You can see up the top there, you've got your Build or Test. Looks like a little pill button where you can flip between the two. That's where you switch between build mode and test mode. By default, you'll be in build mode. When you're on a Flow type that is supported, so auto launch for record triggered, you will see the ability to switch over to test mode. When you're in test mode, you will see all of your test scenarios that you currently have listed, and you can create new to the... New Test Scenarios either by clicking New Scenario down here or New Scenario at the top right there as well. It'll be up the very far top right of your page. I just shrunk my page for this screenshot so you could see both without having to zoom in too much. So there are multiple different ways to create new test scenarios, depending on where you like to look at the screen, ultimately. Beautiful. So once we have, gone in into test mode and we've clicked the new test scenario, this is where we get to build out the test scenario itself. So just like any other element really inside of a flow, you set a label, you set an API name, you give it a description. Always give it a description, be very, very clear. Now this, I will preface here, obviously. I'm hard coding an ID in this example. You wouldn't necessarily want to be doing that. It was just for the simplicity of a of a nice clean example. Okay? So we'd set up the details. You then define your input values. So inside of this example here, I had a Flow that basically you would pass in a record ID, it would retrieve the entire record and then pass it up to, another Flow, I think, in inside of a screen Flow was was the original, purpose of this Flow. So what I've done here is I've defined the input value as a hard coded ID. For those of you who have spun up a new Trailblazer... Oh, sorry. Trailhead Playground or developer role, you would have seen both the Boxer as one of the leads there. This is just the one that I've decided to use. So, again, don't hard code IDs. Don't take that as an example, but this is, that in practice as a as a test scenario. Then you select your run options. So you can choose, you know, the the debug wait element behavior, running the automation as another user or running in rollback mode. That will seem familiar because that does come back from, the former debug mode. Debug mode, it has now rolled fully into Test scenario two, if you'd been looking for it once it's enabled. Then once you've got everything set up, you can then save and run your test, test scenario. You'll see as well there, there's a checkbox, so automated test scenario. In this case, I haven't yet enabled it. A manual test run is one that you can just select one by one and run it as you desire. Okay? We'll come to automated testing in just a second. There we go. Just a second is right now. So I do wanna flag, it is not quite the same as Apex testing, but it is definitely a step in the right direction. Now what do I mean by that? With Apex testing, you must have 75% code coverage across your entire org. Right? You you cannot write your code in production. You cannot deploy code unless it has been tested and your org sort of covers that 75% minimum threshold. I know a lot of people try to sort of aim for a 100, which is great, but there is a minimum threshold of 75% code coverage, and it must be done in a sandbox or scratch org and then deploy it up. Okay? Flow is a little bit different. Even with flow test mode enabled as of today, you can still build flows in production, and you do not need the tests to promote from a sandbox up to production. Okay? So that's that's one of the key differences that, separates Apex Testing and Flow Testing as of today. Okay? You'll start to see some patterns, in flow test mode that look very, very similar to Apex testing, and I am, fingers crossed, super hopeful that down the track, we'll see the ability to enforce the requirement... The similar sort of requirement to, to Apex where your flows must pass testing before they can be promoted. I think that'll be, you know, it's it's a complaint that I... Or not a complaint, but I mentioned that I hear quite a bit that people wish that there was a lot more tight, guardrails around flow deployment. But, anyway, as of today, it's not there yet. That's all I wanted to point out there. So when you enable automated test scenario, so that was a checkbox I was referring to on this slide here, Then you can set up your, assertion condition, so what you expect the outcomes to be. Assertions, again, very, very similar to to Apex Testing. You can set an assertion as in, this is what I expect a variable value will be after the flow has run versus, you know, what it was before, either nothing or or something has changed. You can then, with automated testing, run one or multiple scenarios together. When you're working with manual, you basically just pick the one and choose to run that test, whereas with automated, you can have multiple. And then you can view your coverage across the board anyway. It's it's it's it's a viewing, not a, a requirement or a threshold as yet. But the fact that you can see the percentage of coverage overall is a good sign, I think, for the future of of where this is going. Fingers crossed, everybody. So here's some screenshots of what that looks like there. So once you enable that automated test scenario button here, you'll see the ability to select a data source. So in this case, I kept it simple, and I ran, from my org data. So I... I'm, again, not a good example, but I hard coded an ID of a lead that I knew was in the org. That's why that's there. You can also choose to, use a clean test dataset from a data silo. Okay? So if you've got a a data silo connected, you can choose to use that. That way you're not running off, you know, production data all the time. You can choose to run off a clean set of test data that you wanna use every single time that's exactly the same every single time and untouched. Excuse me. The other screenshot that you can see there is your expected results or assertion. So if you've worked with Apex testing before, you'd know that, you know, you can set your assertions, to be, you know, what you expect your outcome values to be. So on my flow, we can see that the assign... Sorry. Assign success element at the bottom was visited. That is true because we expect that once it has gathered the lead record, that it would assign those values to the output variable that I'd set. Makes sense. The next one is that we expect, and again, this is only because of the hard coded ID, that the lead's first name will equal Bertha and the lead's last name will equal Buxa. Okay? So those are my assertions. Number one, that we will hit that assigned success element. Number two is, the the first name of that lead will be Bertha, and number three, the the last name of that, lead will be Boxer. Okay? And if I jump forward here, this is where I was talking about that code coverage. Okay? So in this example, I only had one, automated flow, but we can see there that we have one automatically run, one passed, zero failed, zero not run, and a 100% test automation coverage. Okay? So that's kind of the high level, metrics that it shows at the top of that test scenarios panel. Alrighty. Who loves working with endpoints? No. Yeah. Okay. Rhetorical, but that's okay. So as you know, when you're working with with, endpoints, you know, your APIs can get rate limited. You can have some, delay as well. Obviously, given you're working with an external system, there can be some delay in processing. Delays when testing are not fun, especially because sometimes... Especially like in in a, in the case of a flow test here, you're not actually trying to test the endpoint itself when you're running a flow test. Right? All you're really trying to test is that the flow does what the flow is supposed to do. Okay? So with flow test mode, one of the features that you can now have access to and start to use is the ability to, to mock those outputs. So instead of telling your flow, okay, you know, come down to this Apex action and then call out to this system and actually do the call out, retrieve it, and then run with that data, you can say, here's a sample set of data. Oh, here's a sample, response that I've received while running that endpoint call in the past, use that as a mock output. Don't actually make the call, behaviors know you did, use that and proceed through the rest of the flow. Because again, what we're trying to do here with Flow testing typically is we wanna run through the flow logic and make sure the flow logic is doing what the flow is expected to do. Okay? We're not trying to test the endpoint, particularly in environments where you may not have set it up. And and, yeah, in those cases, obviously, the flow is all that you wanna be testing. You don't wanna have to reconfigure everything just to make sure the flow works. You can set a mock output so you don't have to, reach out to those external systems. Okay? Now I have flagged here as well that mock outputs also is in beta, safe harbor, but you can define the exact response and action or subflow element returns in your test. You copy real value straight from debug history. Test your external Flow system separately and focus only on your Flow logic. And, again, this works in auto launch and record trigger flows as well. So to do a mock output, now this... For me, every time I go to set up a mock output, I'm not sure why. I always miss a click and I'm confused. So I thought I would I would realign it, you know, make it really really clear here. You open a test scenario. So you must be not in build mode, but in test mode. Then you have to have either created or opened a test scenario in a flow, okay, that has an action or subflow. While you are in test mode and in a test scenario, have one open, you can then click onto the element in question. Okay? So the action or subflow that you wanna test. Well, sorry. The action and subflow that you wanna add the mock output for. Then you open the scenario output properties tab, which I'll show you on the next slide, and define your paths and outputs. And, again, another warning because this keeps happening to me. You can flick between, whether you wanna take the default path or a fault path. However, if you have set up your mock output and then decide, oh, I wanna change it, it will clear your mock output just as a warning. So this is what that looks like. Once you have, you know, opened your test mode, gone into a test scenario, and then clicked onto a, an action, That... This is the action. You you... It'll go to properties by default, but you then switch up to the, scenario output tab up here. Then you can click the use, not using, use mock output button. Once you click use, then it will open this this interface, and you get the ability to select the path you wanna follow, whether it's the default or the, default path. Because the other thing is, you know, you wanna be testing... The good to give out, mocking outputs as you can force either path. Okay? Where's it going with that? Yeah. And and then underneath is where you actually get to specify your... The mock output. So this is basically what I'm saying to the flow test is don't actually call out to the system, but pretend you did and pretend this is what you got back. Okay? So that's that's what that is there. And, again, if you set up your mock output and then you change the, path after mock output value after you've set it up and not saved it yet, it will clear it, and then you have to reset it all up again. He says from personal experience, so just be aware of that. And then here, we can see, again, once you have run a test scenario, if you look in your, test scenario output, you'll be... Sorry. The the test scenario. Yeah. That's that's that's what I meant to say. The test scenario, but you'll be able to dive into, the run details of the entire flow and, specifically, that action as well. Just gonna have a quick sip of water. Sorry. Next up is building flow tests with AI. So we've seen, flow test builder... Sorry. Flow test mode, and and we've seen it embedded into the the flow builder, where you got your build... Your build canvas and your test canvas. Test canvas is obviously where you create your test scenarios if you choose to work through the UI. We are moving into a headless era of Salesforce, so you no longer need to use the the UI, including for this feature, which, again, is in beta. So Salesforce have thought of that already. You can use Agent Force to write your tests, with Agent Force for Flow Headless. So you can skip manual test creation entirely. You can simply provide a prompt to to agent force five specifically saying create flow tests for x y z. Tell it what you want your tests to look like and what do you want it to test for, all sorts of values like that. You can then draft your success, fault, and edge case paths. Now this works for both headless and inside the UI. You need to plan out your tests and make sure you're covering everything. And then obviously, you'll verify and approve before anything is actually added to your flow. Now something I have done my darnedest to confirm is that as as far as I'm aware, and somebody please correct me in the chat because every bit of looking and searching that I've done is telling me this isn't... This is true. You can only access this feature through agent force vibes. If you're a Claude code, you... Like, you prefer to use Claude code like I do, then you you cannot use the agent force for flow headless as I am aware. Again, please, if somebody can prove me wrong there, I will... You'll be my best friend because I'm so sad that I don't get access to that. So if you wanna be using, Agent Force for Flow Headless, you will need to be leveraging Agent Force Wives. Beautiful. And we got a few bonus things we're gonna talk about too. So some small debug upgrades. Again, the debug mode that we have, come to know and love since Flow Builder came out in... Was it spring nineteen, I think? Is now gone, but rolled into, flow test mode. Okay? However, there have been some slight changes because that functionality now exists in test mode has also evolved. So when you previously... If you had a, a lead record... Or, sorry, an input record inside of your flow, when it came to, running a debug, you would have to search for a particular record, which sometimes was great, sometimes wasn't so great. Now you can paste in the record ID or you can search. So you don't have to search. Now if you're just like, you know, you're like me and you wanna copy and paste an ID, done, and it'll pull the entire record for you, which is handy. The next one there is you can now populate collection variables as well. So you can test the output. In italics, they're primitive collections, directly inside of Flow Test mode. Previously, only single input values could be provided easily. Now primitive collection directly into flow test mode means that you can't pass in, let's say, you know, a collection of lead records, for example, or a collection of records is the only one I could be off off the top of my head. Must be primitive. Right? So, yeah, text or or or number, that sort of thing. And you separate them by a semicolon. Okay? And you can also choose as well to pass in a single value, but that's that's up to you. You may have the ability to to provide multiple values as well. So these are some small changes to the traditional debug that is now folded into flow test mode once you've enabled it that are, good quality of life improvements as well. Cool. Let's jump into key key takeaways because that's, you know, if you've paid attention to nothing else, if you, you know, don't wanna listen because my my Australian is too strong, then please listen for this next part because this is the key parts that I want you to take away. So you can now build and test flows in a single tool. It is not quite yet up to par with Apex testing. And, again, that's that's pure speculation and hopium that we are... We're gonna see flow test mode give you the ability to enforce similar sort of guardrails that Apex testing has. So, again, like, I I would love to see in the future, and I'm really, really hoping we do, the ability to disallow creation of Flow inside of prod, the ability to enforce Flow testing, whether this is for new Orgs or something you can enable in an Org that meets criteria, whatever. You can enforce testing, all flows before they can be pushed up to production just like Apex. These are things I think and I hope will come eventually. We now have the groundwork laid where there is a proper testing suite being introduced into Flow Builder. Again, it is in beta current. You can control your endpoint and subflow testing by mocking the outputs. So now if you pre... You know, if you if you had, endpoints that you were calling as part of your flow and your testing was taking too long or it was timing out, you were getting, you know, different, you know, too much variability, you can mock the output up. Oh, that's great. Candice just commented something in the chat about agent force... Sorry. Agent flow headless. I'm gonna come back to that because because you've just made my day. Sorry. I got totally thrown off by that. You can control your endpoint and subflow testing by mocking the output. So you now no longer need to actually execute and communicate with those endpoints to test the flow that uses them. You can say, Hey, Flow Test, just assume this is what you got back. Don't worry about actually connecting to the endpoint. That's not what we're here to test. We're here to test the Flow logic itself. Okay? So with mocking endpoints and mocking subflow outputs, you don't need to go layers deep to test this Flow right now. Okay? You can also let AI draft for you, which again, I just saw from Candice, there is a way, which I'd I'd love to learn more about because I've I've read so much about that and and and nothing was telling me that I could. But you can let AI draft for you and then validate and adjust. This speeds up your workflows. Again, we're not trying to get AI to immediately replace, you know, somebody using flow test mode altogether. We're not saying to to, Agent Foster Flow Headless, hey. Go and write me all the tests that I need to pass this particular flow that I've built. Number one, that's a terrible way to prompt it. You need to be prompting according to your business requirements because you built the Flow for a reason. Somebody gave you a business requirement, you as the Salesforce professional have identified Flow as the tool to achieve that business requirement and to deliver it, then you need to design tests that run according to that. Okay. So you build the technology, then it needs to say, build me a test that, you know, runs like this. Given given x y z record, when a b c thing happens, this is what I expect to occur. The, the AI will then draft you your flow tests. You could validate that it's done it correctly, but you don't have to click through and and configure this, that, and the other. You can just direct your AI to do it as well. And then, of course, we have seen some changes to, to those standard debug features, that that have existed before. So you can now, search for a record or provide its ID for an input variable. And you can also provide multiple values inside a collection variable for primitive value sets, which is great. Brilliant changes that are high quality of life. So today, we saw flow testing get more automated. We got saved scenarios, assertions, and soon, we'll have tests that AI drafts for you as well, which raises a fair question. As automation scales, who checks that work? That's the problem that Tricentis focuses on. So they put approvals, policies, and audit trails around AI agents that test software. If that's on your radar, follow the link on screen, and thanks again through Tricentis for sponsoring today's session. And with that, we are now at q and a. So I'm going to, jump over to the q and a tab here, and I can see a couple of questions come through. I'm just gonna go... We have a little bit of time, so I'm just gonna go bottom to top here. So for small test variances, we used to have to create each subsequent scenario completely from scratch, which is super time consuming. Has the ability to copy and then modify a test scenario been added? That was from Justin. Justin, I don't believe so through the UI. Through the UI. Okay? So a flow... When it when it comes to your XML, so so the the actual flow itself, flow tests sit separate to flows. So if you want to clone and make minor changes, all you really need to do is extract your, flow test XML, you know, duplicate it a few times, change all the details that you need to inside of, inside of an IDE, so inside of, like, a Visual Studio code, and you would be able to save a significant amount of time. Even if, you know, initially, you just sort of, duplicate and rename and then send it up again with with very little change information you wanna change through the UI, the actual cloning itself, is is much, much, much simpler through, you know, extracting the metadata, making new changes, and then deploying it back up to your scratch or scratch or while you're building, of course. In terms of, yeah, through the UI, from what I have seen, I don't believe so, But I could be wrong there. And if not, I suspect it'll be something that's coming soon as well. Can you set assertion logic? Ah, good question, Jeff. Let me just jump back to the right slide because what I did not include here... Hang on. Sorry. Let me just reread your question. Can you set assertion logic? So one aims two or three. Sorry. Sorry. So I was... I misread your question in the first place. Assertion logic, you you would anticipate that they all let me let me come back to you on that, Jeff. I'm just gonna open a, a flow builder off to the side and see if I can, show you what I'm talking about while I do the next question. I'll come back. For record triggered flows, is it true that you need data that exists and is static in production or you need to write a custom Apex class to create custom data? Great question, Lauren. There was one slide that I had. I'm just gonna bear with me as I jump back and forth. There we go. Sorry. It was this one. So you can select your data source here. So you can run either from your old data, which is that, you know, production data you're talking about, or you can choose to run from a data silo as well. So you can have a clean set of dummy data that you operate with, which I think would be the the way to go in in a majority of cases, but you can also then choose to run directly from your old data as well if you so please. Okay? So you can have your your dummy data set up or you can run off production data. You do have that ability to choose between MBS. Does this new feature allow running regression testing and can that be automated as part of a CICD pipeline? So with, Tal, to answer your question, with the automated testing, you can set up your tests to operate as regression testing. Does that make sense? Once you make a change to another area of Salesforce or a different part of a flow or a different flow altogether, you can go to your individual flows and then run all of the automated testing for that flow to make sure nothing has changed. I don't believe it's the the, sort of run all regression testing across the board that you would have seen through Apex testing, again, yet, but you can go to an individual flow, run all of the tests inside of a particular flow that our Mac does automate it, and make sure they all continue to pass. You're handling again, your expected path and your fault paths and make sure that nothing has changed since whatever change that is. So you can you can operate it as a, as a kind of pseudo, regression testing for now. Yes. That's the answer to that. I... Good. There was... One more question has come in. So cloning... For cloning tests, what you mentioned is the only way I can do it is also, one, commit by version control, two, copy and rename the file, and three, deploy back to Salesforce environment edit. Also super time consuming. Let me let me just confirm that real quick as well. I... Bear with me. We have some time left, so I'm just gonna go rogue real quick, log in to an org. Please bear with me. Just before the session started, I was literally talking about, a live demo. I thought, oh, I probably won't do that because I tend to go very off off topic, if I... If and when I do that. But we're here now, and I think this is a really good opportunity to to tackle some of these questions. So... Alrighty. Let me... I'm just opening up a flow now. I'm opening up that flow that I was working through through my example. So it was a slightly different version of the flow. But here we go. We have version two inactive. This is... While I'm here, I'm going I'm going totally off script, but I'll show you, you know, where we've seen some of those screenshots, what it looks like in the real world. So you've got your Flow Canvas that you know and love. Once you have activated Flow Test mode, you'll see this little toggle here. We can enable Test Mode. This is where you can create your Test scenarios. On this particular version of the Flow, I don't have any Test scenarios. If I did, which I do in Version two because it's a slightly modified version, this is where you'd see them. Okay? So you can see your Test Automation coverage. You can see your automated, flows. If you had multiple, you could, you know, tick all or tick the ones you wanna rerun, for that regression testing question that you had, Tal, and rerun them altogether. Assuming they all continue to pass, you're all good. If you've got issues that were caused, you know, down the track, then then, obviously, you're, you you... You've gotta fix things up. Now there we go. I I lied to you, Justin. So I was wrong. There is a UI, but you can, save as a new scenario. So I've got here my positive lead ID with a record, here. I can go... And I hope that's not too small. I apologize if it is, but I can go save as new scenario like this, and I can call it, let's go negative. You know what? I'm gonna run it where I expect it to fail. Okay? So you can simply, you know, copy and paste by going, you know, save as new flow. So I was wrong there. That was something I wasn't aware of. So there you go. And there was another reason, I did this. So assertion logic. Okay. Cool. So here, what you can do... What you were asking, if I've understood you, Jeff, was can you set assertion logic? So you want it to be, sorry. I've hit that. You want it to be, assertion one and two or three kind of thing. As I can see it, no. It's it's more of a, a a general, did it pass or did it not, if that makes sense. So, you you could get... I think the way to handle something like that would be would be adding a formula in. So calculate a formula inside. This this may be overkill and maybe a better way to do it, but I would I would go into, a formula. Just do a check. You know? Create the formula to check that logic, and then have the formula as we expect the formula output to be either true or false or one or two or whatever it is, and do it that way, if that makes sense. Hope that answered the question. I've gone totally, totally, totally off track there. And there is one more question coming through. So to help with the assertion logic question, I'm envisioning something like work assignment. Whoops. For example, call comes in, and it'll be assigned to agent one or three something that may not always be static. Okay. I I... I'll be honest, Jeff. I'm I'm not sure. I'm not sure. I... You probably could do something a little bit formula y in there, but I'd be... I I couldn't tell you off the top of my head, unfortunately. I know that probably hasn't answered the question properly, but I I hope we've at least ruled some things out there. Justin, we have found that we previously weren't able to deploy flow tests between environments. Flow tests were bound to a specific flow version much higher in lower environments. So attempting to so attempting to deploy the flow test would just fail since that same flow version number didn't exist in our QA environment. Has this since been resolved to where flow tests can be deployed? I know for a fact there were, changes to the way that flow tests are deployed. That particular scenario, I'm not sure off the top of my head either, Justin. It's definitely something I would I would test, to test, if I were you, because I know there were some changes. And I believe... Yeah. Yeah. Jeff, I I think your idea of the work around would be the the full media. 100%. Beautiful. I'm just gonna check if there are any further questions in the chat. No. There's not. Look. With that, thank you for sticking with me, particularly as I went way off... There we go. Particularly as I went way off track. But, hey, we got to see it actually in action that was not in my original script. I hope that was beneficial, and not just a complete sideline. We've answered some extra questions there around assertion logic. There may be some need for formally use. There may be some problems with deployment of flow tests with different flow versions based on whether your environments are totally lined up. It's a really good question that I'm going to follow-up myself as well. But hey, look, at the end of the day, what we've learned is that Flow Test mode is a really good step in the right direction. Please also keep in mind, some of those issues or concerns or questions or feature requests that you flagged as well may come to fruition if they are not already before this comes to, to GA because it is in beta. I really wanna re... You know, reiterate that. This is a super, super powerful testing suite for Flow. We've been begging for something like this for years. It is still not yet at the same level as Apex testing, which makes sense. Apex testing's been around since day dot. I would really love to see... I think my my number one feature request from Salesforce before this goes GA ideally, if not after, is the ability to enforce that Flow testing. Like me as an org owner, I want to be able to say, Okay, cool. We're going to build flow tests for every org that we have today, and then enable a checkbox saying, you can no longer build in production, and before anything touches production, it must pass 75% flow coverage or something like that. I'd love to see that. But now I'm going off track again, so I'm gonna be quiet, and say thank you very much for for your time today. I really hope this has been a beneficial, session. Make sure my colleague, Simon, has just posted the chat as well, to learn more about Tricentis, our sponsor for today's webinar, to click on that link, and get in touch with their team as well. And with that, I will leave you to it. Thank you again, and we will catch you in the next one. See you later.