Skip to content

Commit e65b83d

Browse files
authored
Merge pull request #2259 from MicrosoftDocs/aengusheaney-patch-1
Update working-with-test-studio.md
2 parents 775c3b2 + 46cd9e1 commit e65b83d

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

powerapps-docs/maker/canvas-apps/working-with-test-studio.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ By default, a test suite and test case are created for you in Test Studio. Test
5252

5353
## Create a test case
5454

55-
Depending on how you want to organize or group or your tests together, you can create multiple test cases in a test suite. Each case can test a specific feature or a subset of functionalities in your app.
55+
Depending on how you want to organize or group your tests together, you can create multiple test cases in a test suite. Each case can test a specific feature or a subset of functionalities in your app.
5656

5757
1. Select a test suite.
5858
2. Select **New Case** in the top menu to create a new case.
@@ -62,7 +62,7 @@ Depending on how you want to organize or group or your tests together, you can c
6262

6363
## Record a test case
6464

65-
A test case consists of test steps that contain actions. Test actions are written using Power Apps expressions that perform a task. There are two ways to create test steps in the Test Studio. You can use the recorder to automatically generate the test steps as you interact with your app. After you record, you can update the test case, add new steps, delete steps, and write test assertions to validate the result of your test.
65+
A test case consists of test steps that contain actions. Test actions are written using Power Apps expressions that perform a task. You can use the recorder to automatically generate the test steps as you interact with your app. After you record, you can update the test case, add new steps, delete steps, and write test assertions to validate the result of your test.
6666

6767
> [!NOTE]
6868
> Only published app plays in record mode. Publish any recent changes to the app before you start recording a test case. Recording without publishing recent changes causes last published version of the app to play in record mode.
@@ -118,7 +118,7 @@ To add test steps and test assertions in Kudos app:
118118

119119
6. Select **Insert a step above** from the top menu or by selecting the option from the active row. This creates an empty step.
120120

121-
7. Enter an expression or formula in the action input to trace and write the *kudosBeforeTest* value to the test results record.
121+
7. Enter an expression or formula in the action input to [Trace](./functions/function-trace.md) and write the *kudosBeforeTest* value to the test results record.
122122

123123
```Trace("kudosBeforeTest : " & kudosBeforeTest);```
124124

@@ -144,7 +144,8 @@ Before you play the recording back with recent changes, you must publish the app
144144

145145
![Play without publishing](./media/working-with-test-studio/publish-test-studio-changes.png)
146146

147-
If you skip, the recording plays back previous version of published app with test case or suite as selected.
147+
> [!IMPORTANT]
148+
> If you skip, the recording play back will not contain your recent test changes. The last published test case or suite will play against the app.
148149

149150
1. Click **Publish**. This automatically saves and publishes your test.
150151

0 commit comments

Comments
 (0)