How To Use Copilot Studio Kit for Test Automation

Dewain Robinson - The Copilot Studio Dude
16 Aug 202421:12

Summary

TLDRこのビデオでは、Microsoftのpowercatグループによって開発されたco-pilot Studio kitを使用して、co-pilotを自動化テストする方法を紹介しています。Direct Line APIを通じてco-pilotとチャットすることができる機能や、Azure Application Insightsによるテレメトリの追跡、AI Builderとの連携、Dataverseのデータ管理など、キットの機能を詳細に解説しています。また、キットの入手方法、インストール手順、テストの設定方法、実行方法についても詳しく説明しています。

Takeaways

  • 🛠️ 「コパイロットスタジオキット」はMicrosoftのpowercatグループによって開発された、コパイロットの自動テストを可能にするツールキットです。
  • 🔍 powercatはMicrosoftのエンジニアリングチームの拡張であり、最大の顧客と連携する際に使用されます。
  • 🌐 コパイロットスタジオキットには、Direct Line API、Azure Application Insights、AI Builder、Dataverseなどの機能が含まれています。
  • 🔗 Direct Line APIは、Webチャットエクスペリエンスと同様にコパイロットに接続し、チャットを行うための方法です。
  • 📊 Azure Application Insightsを使用すると、コパイロットの内部で何が起こっているかを追跡して確認できます。
  • 🤖 AI Builderは、生成的なAIレスポンスをテストする際に必要であり、正確な一致が返されるとは限りません。
  • 💾 Dataverseはコパイロットスタジオやpowercatが構築されている基盤技術であり、効果的なデータストレージや検索機能を提供します。
  • 📚 aka.ms/copilot Studio kitにアクセスしてコパイロットスタジオキットのダウンロードとインストール方法を確認できます。
  • 🔧 テストを実行するには、コパイロットスタジオキットをPower Apps環境にインポートし、テストスクリプトを作成する必要があります。
  • 📝 テストセットとテストランを設定し、コパイロットのパフォーマンスを評価するためのテストを実行できます。

Q & A

  • コパイロットスタジオキットとは何ですか?

    -コパイロットスタジオキットはMicrosoftのpowercatグループによって開発された、コパイロットの自動テストを行うためのツールセットです。

  • powercatはどのようなグループですか?

    -powercatはMicrosoftのエンジニアリングチームの1つで、最大で影響力のある顧客と連携しています。

  • direct lineとは何で、どのように使われますか?

    -direct lineはコパイロットに接続し、チャットすることができる方法です。ウェブチャット体験ではdirect line APIが使用されます。

  • Azure Application Insightsとは何であり、何のために使われますか?

    -Azure Application Insightsは、コパイロット内部で起こっていることを追跡し、状況を確認できるツールです。

  • AI Builderとは何で、何のために必要なのですか?

    -AI Builderは生成的AIレスポンスをチェックするための機能で、直接一致するレスポンスが返されない場合に必要です。

  • dataverseとは何であり、どのような役割を持っていますか?

    -dataverseはコパイロットスタジオやpowerが構築されている基盤技術で、効果的なデータ保存や検索、インポート、エクスポート機能を提供します。

  • コパイロットスタジオキットをダウンロードするにはどうすればよいですか?

    -aka.ms/copilot-studio-kitにアクセスして、自動的にダウンロードサイトに移動し、ZIPファイルをダウンロードできます。

  • コパイロットスタジオキットをインポートするにはどのような手順が必要ですか?

    -Power Apps環境に移動し、ソリューションをインポートするオプションからダウンロードしたZIPファイルをアップロードし、インポートプロセスを開始します。

  • Azure Application Insightsの接続を作成するにはどうすればよいですか?

    -Azureポータルから取得したApplication IDとAPIキーをコパイロットスタジオキットに入力して、接続を作成します。

  • テストを実行するにはどうすればよいですか?

    -テストセットを作成し、テストケースを追加して実行します。テスト結果は自動的に記録され、詳細なレポートが生成されます。

  • コパイロットのテスト結果を確認するにはどうすればよいですか?

    -テスト実行ページからテスト結果を確認でき、各テストケースの詳細や成功/失敗の理由を閲覧することができます。

Outlines

00:00

😀 co-pilot Studio Kitの紹介と取得方法

この段落では、co-pilot Studio KitがMicrosoftのpowercatグループによって開発されたツールキットであることが説明されています。このキットは、企業のcopilotの自動化テストを可能にします。Direct Line APIを通じてcopilotとチャットすることができる機能や、Azure Application Insightsによるcopilotの動作追跡、AI Builderの応答生成能力の確認、Dataverseによるデータ管理とインポート/エクスポート機能が含まれています。また、co-pilot Studio Kitを取得するには、aka.ms copilot Studio kitにアクセスし、指示に従ってダウンロードとインストールを行うことができました。

05:04

🔧 Azure Application Insightsの接続設定

この段落では、Azure Application InsightsのインスツルメンテーションキーとAPIキーを通じてcopilot Studio Kitに接続する方法が説明されています。まず、Azure PortalでApplication Insightsを作成し、必要なキーを取得します。次に、copilot Studio Kitの設定でこれらのキーを入力し、接続を作成します。これにより、テスト結果がAzure Application Insightsに記録され、テレメトリデータとして利用可能になります。

10:06

🛠 co-pilotのテスト設定と実行

この段落では、copilot Studio Kitを使用してcopilotのテストを設定し、実行する方法が説明されています。まず、copilotを作成し、トークンエンドポイントを設定します。次に、テストセットを作成し、テストケースを追加します。各テストケースには、テスト発話と期待される応答が含まれています。テスト実行を作成し、選択したcopilotとテストセットを指定してテストを開始します。テスト結果は、成功したかどうかを示し、詳細な情報や推奨事項が提供されます。

15:08

🗣️ テストケースの詳細設定

この段落では、テストケースの詳細設定方法が説明されています。テストケースの名前を設定し、応答の種類(トピック一致、添付ファイル一致、生成的な答え)を選択することができます。また、テストのタイムアウトや開始会話イベントの有無も設定可能です。期待される応答やテスト発話の例を入力し、テストケースを保存して実行します。

20:09

📊 テスト結果の分析とレポート

最後の段落では、テスト結果の分析とレポート機能について説明されています。テスト実行が完了すると、各テストケースの成功状況を確認できます。詳細をクリックすると、応答の内容や成功の理由、推奨事項などが表示されます。また、会話のトランスクリプトや管理者機能、監査履歴などの関連情報を確認することもできます。

Mindmap

Keywords

💡コパイロット スタジオキット

コパイロット スタジオキットは、マイクロソフトのpowercatグループによって開発された自動化テストツールキットです。このキットを使うと、コパイロットのパフォーマンスをテストし、評価することができます。ビデオの主題はコパイロットの自動化テストであり、このキットがその中心的なツールとして紹介されています。

💡Direct Line

Direct Lineは、コパイロットに接続し、チャットすることができるインターフェースです。ビデオスクリプトでは、Direct Line APIを使ってコパイロットと対話することができる機能として説明されています。これはテスト実行において、コパイロットとのインタラクションを可能にします。

💡Azure Application Insights

Azure Application Insightsは、マイクロソフトのクラウドプラットフォームサービスで、アプリケーションのテレメトリを収集し、分析することができます。ビデオでは、このサービスを使ってコパイロットの内部動作を追跡し、テスト結果を豊富にすることが示されています。

💡AI Builder

AI Builderは、マイクロソフトが提供するサービスで、生成的AI応答を生成することができます。ビデオでは、AI Builderがテストキットに組み込まれており、生成されたAI応答のテストが可能であることが強調されています。

💡Dataverse

Dataverseは、マイクロソフトのデータ管理プラットフォームであり、効果的なデータストレージと検索機能を提供しています。ビデオでは、Dataverseがコパイロットスタジオとpowercatの基盤技術として機能し、テストキットのデータ管理に使われていることが説明されています。

💡アカウントの設定

アカウントの設定は、ビデオスクリプトで説明されているテストキットのインストールプロセスの一部です。Azure Portalから取得したApplication IDやAPIキーを設定することで、Azure Application Insightsのテレメトリを保存するための接続を作成します。

💡テスト ケース

テスト ケースは、ビデオスクリプトで作成され、実行される具体的なテストです。テストケースには、予想される応答やテストの実行時間などが含まれており、コパイロットの特定の機能を検証するために使われます。

💡トピック

トピックは、ビデオスクリプトで示されているコパイロットの機能の一部であり、特定の問い合わせに関連する応答を提供します。テストケースを作成する際に、トピックに関連する応答が期待されるかどうかを指定することができます。

💡応答マッチ

応答マッチは、テストケースで使用される機能で、コパイロットからの応答が予想される応答と一致するかどうかを検証します。ビデオでは、応答マッチを使ってテストケースの正確性を保証することが強調されています。

💡テスト実行

テスト実行は、ビデオスクリプトで説明されているプロセスで、テストケースを実際に実行し、結果を収集します。テスト実行のステータスを監視し、テスト結果を分析することで、コパイロットのパフォーマンスを評価することができます。

Highlights

介绍了如何使用Co-Pilot Studio Kit来自动化测试Co-Pilot。

Co-Pilot Studio Kit由微软的Powercat团队开发,该团队服务于微软最大的客户。

Co-Pilot Studio Kit包含Direct Line API,允许用户与Co-Pilot进行聊天。

使用Azure Application Insights跟踪Co-Pilot的性能。

AI Builder集成,用于检查生成性AI响应。

所有功能都建立在Dataverse之上,这是Co-Pilot Studio的基础技术。

通过aka.ms/copilotStudioKit访问Co-Pilot Studio Kit。

下载Co-Pilot Studio Kit后,需要在Power Apps环境中导入解决方案。

创建Azure Application Insights连接以存储遥测数据。

创建Co-Pilot测试时,可以选择关闭Entra ID认证简化测试过程。

配置测试脚本时,可以设置测试集和测试运行。

测试脚本可以设置预期的响应和测试话语。

测试运行可以自动执行并验证Co-Pilot的响应。

测试完成后,可以查看详细的测试结果和推荐。

Co-Pilot Studio Kit提供了丰富的报告和信息,帮助评估Co-Pilot的性能。

观众可以通过评论请求更多关于测试工具的视频内容。

鼓励观众订阅频道并参与评论交流。

Transcripts

play00:00

[Music]

play00:08

in this video I'm going to show you how

play00:10

to use co-pilot Studio kit for

play00:13

automating test with your co-pilot so

play00:16

let's start with what is the co-pilot

play00:19

Studio kit and where did this thing come

play00:21

from well the co-pilot Studio kit is

play00:25

built by a group at Microsoft called

play00:27

powercat and powercat is an extension of

play00:30

the engineering team at copilot Studio

play00:33

that works with all of the biggest and

play00:35

baddest customers that Microsoft has to

play00:37

interface with and they went out and

play00:40

decided hey it would be great to have

play00:42

this automation toolkit that would allow

play00:44

you to be able to test your co-pilot and

play00:47

be able to find out how is it performing

play00:51

so let's explore a little more on what's

play00:54

inside this kit so inside of the copilot

play00:57

Studio kit you actually have this

play01:00

ability to test a co-pilot through

play01:02

something we call direct line and direct

play01:05

line is the way that you can connect to

play01:07

your copilot and be able to chat with it

play01:10

so if you ever think about the web chat

play01:12

experience as an example it uses the

play01:14

direct line API so it's going to use

play01:17

that in order to be able to do your test

play01:19

now we're also going to have Azure

play01:22

application insights that allows you to

play01:25

be able to track and see what's going on

play01:27

within your co-pilot itself we it also

play01:30

has capabilities with AI Builder so if

play01:33

you're going to have generative AI

play01:35

responses you need a way to check those

play01:38

because it's not going to come back with

play01:39

a direct match so that's one of the

play01:41

reasons why you'll see AI Builder as

play01:43

part of this and then lastly it's all

play01:46

built on top of dataverse dataverse is

play01:48

the foundational technology that all of

play01:51

copilot studio and power is built on top

play01:53

of that allows for Effective data

play01:55

storage and does a lot of work to make

play01:58

it so that you get this really robust

play02:01

Enterprise place to store and be able to

play02:04

search and find all the different

play02:06

components and also allows that import

play02:08

export capabilities that you've seen

play02:12

within copilot studio so let's first

play02:15

start with how do I go and get ah hold

play02:17

of the actual copilot Studio kit and the

play02:21

way that you can get this is you can go

play02:24

to

play02:26

aka.ms copilot Studio kit and it will

play02:29

automatically take you to this site that

play02:32

you see here and in this site you'll see

play02:35

that it gives you information about the

play02:38

co-pilot Studio kit it gives you

play02:40

information about uh the different ways

play02:42

that it can work you can see here it has

play02:45

things about exact match attachments

play02:47

match all of these different

play02:49

capabilities that this thing has out of

play02:51

the box and I would encourage you to

play02:53

continue to look at this because uh it

play02:56

enhancements of this may continue to

play02:58

happen uh by the power cap team over at

play03:00

Microsoft so you'll see that even the

play03:04

slide that I shared earlier is here you

play03:07

can see a visual representation of it

play03:10

you can see other things that are in

play03:12

here you can also check the

play03:14

prerequisites and you can get the in

play03:16

installation instructions which is the

play03:18

key thing for us right now so the first

play03:21

step is going to be to go ahead and go

play03:24

to the

play03:25

aka.ms download copilot Studio kit you

play03:29

can just click this link and it will let

play03:31

you download this and just from there

play03:33

you're going to get a zip file that's

play03:35

downloaded on your computer now once

play03:38

you've downloaded that what you're going

play03:40

to need to be able to do is go into a

play03:43

cop Studio enabled environment such by

play03:47

going to make. power

play03:50

apps.com so once you get into your power

play03:53

apps environment that is created as part

play03:56

of this if it wasn't already created

play03:59

you're going to be able to select your

play04:01

environment and you can do so right up

play04:03

here and you can see that I really only

play04:05

have one environment in this particular

play04:08

implementation so I'm going to use that

play04:10

particular environment as I go forward

play04:13

now it's important that the environment

play04:15

is the environment in which you are uh

play04:18

have your co-pilot implementation that

play04:21

you're looking to test so I'm going to

play04:24

go ahead and go to Solutions

play04:30

and now that I'm in Solutions what I

play04:33

want to do is I want to go in and import

play04:36

a

play04:37

solution and when I go click import a

play04:40

solution I can go to browse I can

play04:45

grab that file I just downloaded which

play04:48

is our ZIP file for the

play04:52

implementation and click

play04:55

next and then I'll click next again

play05:04

and notice here that you're going to

play05:06

need to create an implementation for

play05:10

application insights now if you haven't

play05:14

already uh created one you can go create

play05:18

one of these pretty easily inside of

play05:21

azure I'm going to go ahead and refer

play05:24

you to a video where I went through

play05:27

application insights and kind of the

play05:29

configuration that's already on my

play05:30

channel so if you haven't actually done

play05:33

this before just know that you need to

play05:36

go and create one of

play05:40

those so I'm going to go ahead and click

play05:42

on

play05:43

create you'll see here that it needs a

play05:46

connection name and I'm going to go

play05:48

ahead and put in a connection name and

play05:50

I'll just call this uh

play05:56

co-pilot um

play06:01

Studio

play06:04

kit then we need our application ID and

play06:08

our API key now we need to get that from

play06:11

from the Azure

play06:13

portal so I'll grab the instrumentation

play06:17

key right here and go drop it

play06:20

in and we're going to drop that into the

play06:23

application ID right

play06:25

here now we need to get the the actual

play06:30

uh API

play06:33

key if you don't already have an API key

play06:36

you just simply go create one and in

play06:39

this I would recommend giving a

play06:44

description and basically what we want

play06:46

here is we want read and write and I'll

play06:50

just give it all of the different

play06:52

permissions and I'll take this and I'll

play06:55

copy the API key that was given to me

play06:59

and we'll go back and we'll drop that

play07:03

in so we'll drop that into the API key

play07:09

here and then we'll create and by doing

play07:12

this now we have created the connection

play07:14

for the Azure application insights to

play07:18

store like the Telemetry that's going on

play07:21

and then we have data verse which is

play07:23

where our solution is being imported to

play07:25

and being stored and then we can just

play07:27

click import

play07:30

now you'll notice that right here it

play07:32

actually says that it's going through an

play07:35

import process this can take a second or

play07:37

two depending on your environment but

play07:39

just know that it's going to go ahead

play07:42

and create this solution for

play07:44

us once your solution is done importing

play07:48

know that it will give you a

play07:50

confirmation on the screen but let's go

play07:52

ahead and click over into Apps and once

play07:55

we go into apps now you can see the C-

play07:58

pilot Studio kit has been installed and

play08:01

I can hit the play button and once I hit

play08:05

the play button it's going to ask me to

play08:20

authenticate if you notice this hang uh

play08:23

just know that you can click off of Home

play08:25

click over on co-pilots and come back

play08:27

this is what you should see once once

play08:30

you have your solution up and running

play08:33

and at this point we should be able to

play08:35

start configuring a test or a co-pilot

play08:39

that we'd like to test so let's first

play08:41

click over on

play08:43

co-pilots and we'll click on

play08:46

new and we need to create a co-pilot

play08:49

that we want to test so I'm going to

play08:52

test the one that I built for the

play08:53

Porsche

play08:55

information that I have already today

play09:02

you'll need to come in and DEC decide

play09:04

which is the region and in this case I'm

play09:08

just going to take the default

play09:09

region then over here you can see who's

play09:12

the owner you can select who it is that

play09:15

is actually going to be the owner of

play09:16

this particular base configuration for

play09:19

this new co-pilot and then we need to

play09:21

get a token end point so what what I'm

play09:24

going to do is I'm going to use my

play09:25

Porsche product information co-pilot

play09:28

that I built in an earlier video however

play09:32

I'm going to make some slight changes

play09:34

here just to make this simple know that

play09:36

there are different configurations

play09:38

depending on what you want to do but

play09:40

just for the Simplicity of the video I'm

play09:42

going to go ahead and I'm going to

play09:43

change the security on my

play09:48

co-pilot and the way I'm going to do

play09:50

that is go to authentication and I'm

play09:52

just going to turn off the entra ID

play09:55

authentication Now by doing this it

play09:58

gives me the ability to be able to uh

play10:01

connect and get an endpoint without

play10:03

having to worry about setting up all the

play10:05

security once we've done that I'll go

play10:09

back over to channels and we'll go to

play10:11

the mobile app and right here you can

play10:14

get your URL for the token endpoint so I

play10:18

I've copied that

play10:20

over and I'm going to drop that into the

play10:23

token endpoint here now once we get past

play10:27

this we're also going to have things

play10:29

like the channel security and things of

play10:33

this nature and the documentation has a

play10:35

lot of great information guys for you to

play10:37

go check out so if you want to look at

play10:40

all the different configurations that

play10:41

you can have uh and such we you can go

play10:45

do that now we can

play10:48

also go in and put in like enrich with

play10:51

Azure application

play10:53

insites by doing this it basically

play10:57

enriches the test results for generative

play10:59

answers test with Azure application

play11:01

insights Telemetry data because of what

play11:04

we're going to do in this initial test

play11:06

just to show you guys how this thing

play11:07

works I'm not going to be enabling that

play11:10

in our uh environment but that's a place

play11:13

where if you're wanting to get some

play11:15

additional information on what's going

play11:17

on uh behind the scenes with the

play11:20

generative AI features you

play11:23

can now the other option here is that we

play11:26

can enrich with conversation transcripts

play11:28

and again

play11:30

these have to do with pulling in the

play11:32

actual conversation transcripts now

play11:34

again we're not going to do any advanced

play11:37

configurations just calling out a couple

play11:39

of key things that you're going to see

play11:41

and as you can see here we also have the

play11:46

generative AI

play11:47

configuration as well that you can turn

play11:50

on and off and notice here that you have

play11:53

to say what are you going to use and the

play11:55

only option is AI Builder so if you want

play11:58

to test generative AI features you'll

play12:01

need to do this now I may run a separate

play12:04

video that shows how to be able to do

play12:05

this later you guys leave something in

play12:07

the comments if you want to see that now

play12:11

now that we've got this all we have to

play12:13

do is hit save and

play12:15

close and now that we've got that done

play12:18

you'll see that now you have a co-pilot

play12:21

that has been configured so if we go

play12:24

here you'll also see that I need to be

play12:28

able able to configure test scripts and

play12:31

you can see we've done no test runs

play12:34

currently today all we've done is

play12:36

created a co-pilot that we want to be

play12:38

able to test so the first thing that we

play12:40

need to do is create a test set and a

play12:43

test set is going to be like a

play12:45

combination of things that it's going to

play12:47

go run all the tests that we want it to

play12:50

run so in this case what I need to do is

play12:52

I need to give it a test set and I'll

play12:54

just call this um Porsche simple

play13:02

and I'm just going to hit save and

play13:05

close now we've got ourselves a test

play13:09

set and inside of this test set you'll

play13:12

see that we have no actual test that

play13:15

have been

play13:19

run so now what I'm going to do is I'm

play13:21

going to set up some test and we'll

play13:23

start by clicking on new and then we're

play13:27

going to need to give it a name and

play13:28

things of this nature so so let's jump

play13:30

back over to copilot Studio real quick

play13:32

and let's look at some of the topics

play13:35

here that we have and you can see I've

play13:37

got these different things that I've

play13:38

been able to test with and I'm going to

play13:41

start with the fine local Porsche Center

play13:44

and what I'm going to need to do is I

play13:45

need to grab this response right here

play13:48

which is what the copilot is going to

play13:50

respond with and we want to come in and

play13:54

say that we'll just call this uh find a

play14:00

dealer and what we're going to say here

play14:03

is that we want to use the simple test

play14:06

set we also um want to say how long now

play14:10

if you don't know how long your your

play14:13

query is going to take because you might

play14:14

have like a power automate flow or

play14:16

something like that that's on the back

play14:17

end but the point being is what you're

play14:20

wanting to look for as a an input here

play14:24

is how long you think that's going to

play14:25

take now if you read the instruction

play14:27

manual the instruction manual will tell

play14:29

you if you don't know you should put 10

play14:32

now anything below 10 seconds I actually

play14:35

started to see some errors and things

play14:37

like that uh and so just to make sure

play14:40

that it has plenty of time to respond

play14:42

I'm just going to do that and

play14:44

then with that we also have a setting

play14:47

here and this is the setting that says

play14:49

send start conversation and the send

play14:52

start conversation is basically whenever

play14:56

you go into a co-pilot and you first

play14:59

start a conversation a lot of times

play15:01

you'll see it it'll say like hello this

play15:04

is my name and this is what I do but

play15:07

understand that the direct line API

play15:09

doesn't have to do that you have to send

play15:11

in an activity or an event that is the

play15:14

start conversation event so if your test

play15:17

needs to have the start conversation

play15:19

event triggered in order to be able to

play15:21

work then you can flip this but in the

play15:23

case of this I don't really need that

play15:25

and I'm going to put in that the

play15:27

expected response is right here

play15:29

now you'll even notice I have a typo in

play15:31

here and we'll play with that as we

play15:33

go um but what I'll do is and I also

play15:37

want to go in and come up with what is

play15:40

an example of something I might ask and

play15:42

so here is the utterance that I want to

play15:45

grab right here and we'll jump back and

play15:49

we'll put the test utterance in right

play15:51

here so now we have where it's going to

play15:54

ask this question and it expects this

play15:56

response and we will

play15:59

go ahead and hit save and

play16:01

close now you can see here I've got my

play16:04

find a dealer now let's go ahead and add

play16:07

one more in so I'll go ahead and create

play16:10

another new one and let's go in and

play16:13

let's look at a different topic and in

play16:15

this case I'm going to say I want to get

play16:18

accessories and things of that nature

play16:20

like clothes or something of that nature

play16:22

so I'm going to go ahead and copy the

play16:23

response that comes back and we'll give

play16:27

it a name and we'll say you know

play16:31

find

play16:34

clothing and we're going to keep this

play16:36

response match again this is where you

play16:38

can go and say whether you just want to

play16:40

match the topic you want to see

play16:42

attachments a generative anwers so and a

play16:45

topic match think of it that what you're

play16:47

looking for is you want to be able to

play16:48

give it a test utterance you don't

play16:49

really care what it says back you just

play16:51

want to know that it went to the right

play16:53

topic but in the response match we want

play16:55

to see the exact response so in this

play16:57

case I'm going to leave it response

play16:59

match I don't need the this setting here

play17:02

I want it to be in uh part of this test

play17:06

set and then again we'll put in

play17:09

10 and then we'll put the expected

play17:12

response in right here let's go get a

play17:15

test utterance you can see here this is

play17:18

the test utterance that I want to

play17:21

have and I'll drop this in right

play17:25

here and we'll go ahead and save and

play17:27

close and now that we've done this you

play17:30

can see now we've got our different test

play17:32

sets or our test queries that we want to

play17:35

run and now we can actually go and

play17:37

execute this test now we'll go into test

play17:41

runs and you'll see here we don't have

play17:42

any that have actually run you could

play17:44

also come up here and you can see that

play17:47

there's been no tests that have been

play17:48

recently run but let's go ahead and say

play17:51

okay I want to actually run a test so

play17:55

keep in mind that when we have these

play17:56

tests we might want to run multiple

play17:59

instances of these tests to be able to

play18:00

check to see like maybe we want to run

play18:03

in on a certain day or something of that

play18:05

nature so in this case what I'm going to

play18:08

do is I'm just going to put in that this

play18:11

will be um

play18:13

video demo one and what I want to test

play18:18

is I want to test this test set again

play18:21

that'll test all of the things in that

play18:22

test set and then I also want to choose

play18:25

which co-pilot and I want to do the

play18:26

Porsche co-pilot that we've got now once

play18:29

I hit save and close on this what's

play18:31

going to happen on the back end is

play18:32

you're going to see that it'll start and

play18:35

it'll automatically kick this off so

play18:37

it'll take a second for it to start but

play18:39

we'll see it kick off and start to run

play18:41

in just a

play18:45

second and we're looking right here at

play18:47

the Run status is what we're looking for

play18:51

and you can see now it is running now

play18:53

again keep in mind that we had two

play18:55

different things that we needed to run

play18:57

and we gave it up to 10 seconds so it

play18:59

may take a second or 20 seconds for this

play19:02

thing to

play19:05

update and you can see we have a

play19:08

completed test now let's go ahead and

play19:11

click in on the test and you can see

play19:13

here that we had a successful actual

play19:16

match on each of these different items

play19:19

and if you want to you can even click in

play19:20

on them and get more details you can see

play19:23

this is the actual response here's the

play19:27

the reason that it was successful

play19:29

all of these different things you can um

play19:32

and again you can have other things that

play19:35

it will give you recommendations and

play19:37

things of this nature if we had pulled

play19:40

in the uh information on the transcript

play19:43

the transcript information would have

play19:45

shown here you can also see like admin

play19:48

uh functions and things of this nature

play19:51

on the test set there's also related

play19:53

things like an audit history um as well

play19:57

that you can look at if you uh set all

play19:59

of these different things up and the

play20:02

also even background processes and

play20:05

things that are uh that we're taking but

play20:08

again this was just a very simple test

play20:11

of being able to use this but you can

play20:13

see the power that this will give you as

play20:16

you continue to go run and have all your

play20:19

different tests and you can see all the

play20:21

different things that you get coming out

play20:23

of this and being able to give you some

play20:26

really good reporting and information

play20:28

around is this thing performing and

play20:30

doing what you need it to do now if

play20:33

you're interested in seeing more videos

play20:37

about the testing uh tools to allow us

play20:40

to be able to go say run test against

play20:43

generative AI things and things of that

play20:45

nature again please put that in the

play20:47

comments below I really want to try to

play20:49

focus content on things that you guys

play20:51

want to see and as always thanks for

play20:55

coming and watching our my videos I

play20:58

really appreciate all the support that

play21:00

you guys give me know that you can like

play21:03

And subscribe to my channel and as

play21:05

always you can go TR copilot Studio at

play21:09

aka.ms TR copilot Studio

Rate This

5.0 / 5 (0 votes)

Related Tags
AIテスト自動化コパイロットMicrosoftパワーカットDirectLineアプリケーションインサイトAIビルダーデータバーステストキットチャットボット
Do you need a summary in English?