Power Apps Test Studio Feedback discussion thread

[AengusHeaney]

We recently launched the new Power Apps Test Studio to help you build end-to-end tests for your Canvas apps. You can read more about it in this blog post. As you use the tool, we’d love to hear your feedback, so we can prioritize the next set of improvements, any features that are missing, or any of the current behaviors that may not be ideal.What kinds of tests are you writing? Is there anything that is too hard to understand, and that we could make easier? This community post will be used to consolidate all feedback on the tool. You can also access this post directly from the "Provide Feedback" link in the Test Studio.

[AustinJonesMSFT]

@KL2021 thank you for the feedback!  We are aware of this issue which doesn't seem specific to Test Studio but does seem to affect it quite a bit.  Active investigation into root cause is in progress.

[AustinJonesMSFT]

@KL2021 we have identified root cause of the issue involving datasources that affects the Test Studio save scenario and a fix has been queued for an upcoming release train.  As a temporary mitigation, open the app, save, and publish in Canvas Studio.  Then open Test Studio and the app should load successfully for recording/playback scenarios.  You can continue making updates to test cases within the app but be sure to only save the app from Canvas Studio.  

I expect the fix to be available in preview environments the week of 9/27.  It will then reach all production regions by 10/11 for frequent environments, moderate environments by 10/25.  

[Anonymous]

I am using Power apps Test studio to create test cases for my canvas app. I have used Sharepoint List to store my test results and have added that as a connector. While creating test cases, I constantly face the issue "This test didn't save properly. Please try again.". The same issue persists for Publish, Play and Save as well. I tried to restore the previous version and play my test cases, but no use. I am seeing the same issue.

I have noticed that when there is no much activity for a long time in test studio and after a while if i try to publish or save, this issue starts.

Note: I had played all my test cases and had got the results in my list as well. From this morning i am facing the issue of tests not getting saved. I have tried all ways to get rid of that error but it doesn't seem to work.

Please provide a solution to this problem/bug.

[AustinJonesMSFT]

@Anonymous I'm sorry to hear that you're experiencing an issue trying to save/publish tests.  Based on your comment, can you confirm for me that you keep the Canvas Studio open while you use Test Studio? 

If you happen to close Canvas Studio (or receive a prompt that idle session has been closed), the underlying server session will be shutdown and Test Studio will be disconnected.  You will need to close Test Studio, reopen Canvas Studio and then launch Test Studio again.

[Anonymous]

@AustinJonesMSFT Yes I had my canvas studio open while i was working on the test cases in the Test studio. I was able to create 11 test cases and then play and check it but suddenly i started getting the error which i has mentioned in the thread. I tried to restore previous versions, even then the same issue is present. i have tried to clear the caches and cookies and tried to login fresh! Still the same issue. 

[Tarunpreet]

Hi,

We have started using Test Studio that is built into the PowerApps platform. Few questions/ observations that I came across-

1) Is there a way I can copy test steps across different test suites? Right now I have to go into each step and copy and paste the text in the step. Not sure if there is a better way to copy one or more steps from one test case to another or from one test suite to another.

2) Is there a way to disable/ enable test steps in a test case or a test case in a test suite?

3) Is there a way to add wait times between test steps in a test case?

[AustinJonesMSFT]

@Anonymous which version of Canvas Studio are you using?  Have you tried using an earlier version of Studio to see if same issue occurs?  When you encounter the same issue in a new session, is it immediate or only after a period of being idle in Canvas Studio (>1hr)?

If you are completely blocked, we'd be glad to take a deeper look with you.  Are you able to engage us via a support case that can be escalated to my team?

[AustinJonesMSFT]

Hi @Tarunpreet . These are all great suggestions.  For #1, you're in luck... we offer that capability today!  Simply cut/copy an individual test case and paste it into the desired test suite or fully "duplicate" a test suite (creates a new suite with all cases/steps from the duplicated suite).

Cut/Copy a Test Case

Duplicate a Test Suite

For #2 I unfortunately can't think of a way to temporarily disable individual steps/cases directly.  A hacky workaround would be to "cut + paste" a test case into a separate suite to temporarily hold "disabled" tests.  For #3, we already have an item in our backlog to provide a mechanism for introducing test case "think time" and will consider your feedback as a point of validating that idea.

Let us know how use of the copy/paste capabilities work out for you and thank you for the feedback!

[Tarunpreet]

Thank you for your response Austin. My challenge has been with copying test steps across test cases or test suites. I have been able to copy test cases and even duplicate test suites within an app.

Also, do you know if there is a way to copy test cases/ test suites across different apps? Or if we can build a shared library of test cases/ test suites that can be copied over to other apps?

[Tarunpreet]

Hello, 

I have been having issues with saving and playing my test scripts today in PowerApps. It appears even after I save a publish in test studio the app does not get published. I am prompted to Publish the app again if I try to run my test script. I am also getting error message saying- "This app stopped working. Try refreshing your browser". I have tried clearing out my cache and starting a new instance and also tried switching the versions of the app from 3.21091.38 to 3.21092.24 which is the recommended version but have see this error inconsistently. Wondering if anyone is also having the same issue?