Transcript:
0:00 in this short video we're going to show
you how fast and easy it is to build
0:04 automated tests for Dynamics 365 with
North52's TestShield the scenario we
0:09 want to test is on the opportunity
entity when the probability has changed
0:13 a power automate flow is triggered and
determines what rating should be applied
0:17 let's have a look at this in action I'm
going to update our opportunity with a
0:21 probability of 80% and save the flow
will be triggered and we can see the
0:26 condition that was met in our flow and
the update was made and back on our
0:30 opportunity record the rating has been
set as hot suppose we want to
0:36 automatically test this flows working as
expected on a daily basis or whenever a
0:41 release is made with North52s TestShield we
make this very easy let me show you how
0:47 first open up the North52 Productivity
Suite and create a new test a North52
0:52 test consists of four steps assemble a
range act and assert let's have a look
0:58 at these in turn we complete the test
settings setting the test to be async as
1:02 we are using a power automate flow the
assemble step is where you describe the
1:07 feature or process that you're testing
you can put as much details as you like
1:11 here or link to external documentation
like Azure DevOps next we complete the
1:17 arrange tip this is where we define the
test data that will be created when the
1:21 test runs
TestShield makes this easy as we can
1:24 use the record we created earlier as a
template we simply go to the Explorer
1:28 tab find the record and select the
attributes we need for our test in this
1:32 case just the probability we add the
record details to the sheet and as you
1:37 can see test shield automatically adds
test identifier markers to the topic
1:41 field so that when the records are
created very easily identified to create
1:46 further test records to test various
probability thresholds we simply select
1:51 and drag down to create additional test
data each row represents an opportunity
1:56 record the ACT sheet is where you define
processes that you need to manually
2:01 trigger as part of your test for example
an on-demand workflow or action the
2:06 power automate flow for our test is
automatically triggered so there is
2:09 nothing to do on the ACT sheet for this
test for the
2:12 Assert we need to determine whether the
records created by the test match the
2:17 desired outcome we can use our explore
tab to populate the assert sheet with
2:21 our reference record and then edit the
data for our test each row represents a
2:26 record we want to validate values for
2:31 once the asserts have been specified we
can save the test and manually execute
2:36 it to ensure the test works as expected
the test will create six opportunity
2:42 records which in turn will trigger six
flows if we look at our flow history we
2:48 can see that six flows have been run as
part of our test after a minute we can
2:54 view the test results directly with an
hour test record our test is now ready
2:58 to be run automatically on a schedule
or as part of an azure devops pipeline
3:05 test results can be pushed into Azure
DevOps so that they can be managed as
3:10 part of your development workflow a full
trace file and results details of each
3:16 step are saved
we also provide an addon to easily
3:21 visualize your test results - if you've
liked what you've seen
3:27 let us show you more and a range of demo