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.

[AengusHeaney]

@RemiChambard2 - thanks for the additional info Remi! we were trying with multiple browser versions and could not repro your issue. Based on your testing, it seems you have isolated the issue down to the Timer control. I'll get this reviewed. 

[RemiChambard2]

Thanks @AengusHeaney. Based on my analysis, I think that it's due to the fact that my Timer is constantly updating the user interface.

[AengusHeaney]

Agreed @RemiChambard2 - i can repro the problem. The test runner needs to know when the page is "ready" to be interacted with but since the page state is changing every second, it blocks the next step execution. We can't arbitrarily proceed to the next step as the page may not be refreshed with data from various data operations, so we build in the mechanism to check if the page is "ready" for the next step execution. We'll look at options for the timer control and come back to you...  

[RemiChambard2]

@AengusHeaney As for now, I use a trick where I have bound the "AutoStart" property of my Timer controls to the presence of the "sourceLink" Url parameter.

I have one more query : is it possible to add the "sourceLink" Url parameter when Tests are started from Test Studio ? As for now, the parameter is only set when using the URL autogenerated for tests.

[AengusHeaney]

@RemiChambard2. you could put the below expression in the OnStart of the App. 

Set(isTestMode, Not(IsBlank(Param("__PATestCaseId")) And IsBlank(Param("__PATestSuiteId"))));

and then set the repeat property on the timer to 

Not(isTestMode)

This will allow the timer to initialize first, and any calls that are needed to be executed. The tests will then run after the timer has stopped. 

Let me know how you get on with this. Thx!

[LauraGB]

That sounds a great feature. I know wrong thread but thank you @AengusHeaney  for pointing it out.

[RemiChambard2]

Hi @AengusHeaney .

Sorry for the late reply.

That's perfect ! It made the trick.

Just a suggestion : couldn't be it easier to have a dedicated property in the App object to know if the application is in test mode or note ? For example App.IsInTestMode.

[RemiChambard2]

One more feedback : when editing a test case in Test Studio with multiple test steps (> 20 for example), could it be possible to stay where we are when adding a new step in the middle of the test case ? Currently, it goes always at the bottom of the test case which is a little bit painfull.

Thanks 🙂

[RemiChambard2]

@AengusHeaney do you have an estimated release date for components support ? 🙂

[AengusHeaney]

thanks for the continued feedback @RemiChambard2 ! Rolled replies to each of your posts below..

"App.IsInTestMode" - yes, having a prop to indicate if running in test mode would be alot easier and it is a good idea. We had also discussed this in the team as a longer term option (rather than parsing URL)
"adding new step, focus goes to bottom" - I've created a usability bug for this and we'll review asap. 

"do you have an estimated release date for components support" - can't give an ETA but it is a couple of months out. we want to increase coverage on some core controls like Peoplepicker, timers & how we handle them, datagrids and then components (native & PCF)