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.

[Anonymous]

@AustinJonesMSFT Yes please, it would be great if a support case is created and someone can take a look at the issue. Thank you for your response.

[Anonymous]

@Tarunpreet That is exactly the same issue i was facing couple of days ago. I restored to the basic version and somehow got the app to work but still i see this issue every time I make new changes. I am not able to proceed with my test cases after this issue.

[Tarunpreet]

@Anonymous Thank you for confirming. 

[ramone]

Hi, 

Some considerations: why we have to publish each time we change a case? is tedious and it only slows down the whole testing workflow.
PS: For some reason, it seems I am unable to skip that step... and even more strange, whenever I fire the test app in a demo environment, test suits start in my organization production environment...

Though is a great and fantastic idea the implementation of test suits, is maddening to try to  follow a TDD workflow in this current state: execute tests faster would be my request.

~~Second, why ```Assert(True=true)``` passes as valid test???  I can't see the logic here (bug?)~~

[PS: solved, needed to enable Formula level error management option in advanced settings]
Thank you MS PA team, overall test Studio is a super valuable addition.

[mattgo]

@Anonymous if you are able to submit a ticket directly to our support team (see the bottom of the page at Support | Microsoft Power Apps) that is the preferred route for getting this issue escalated to our engineering team. If not, I can help get this prioritized to help get you unblocked.

[mattgo]

@ramone glad to hear you were able to solve the issue. Thank you for the feedback as well! We are looking into updating and streamlining the Test Studio experience in the first half of this year; I am optimistic we can address your suggestions around faster test execution and reducing the steps required to be able to run tests.

[ramone]

Hi, thanks @mattgo for the reply and follow up! I appreciate that.

I come from an Excel dev background and the whole possibility to make quick exploratory tests is very much missed (regarding here the terminal or 'view panel' execution workflow). 

I understand is not the whole scope or point with this PA platform, but in this case, I would think that if you want to make it more developer friendly, as developer I would like to see more REPL interactivity inclination in the most advanced features, fast test execution and quick command response cycling times. 

Regarding the tests, my feeling by now (discovering phase) is that, as the Test Studio platform is currently layout, seems more to be thought for post-deploying scenarios instead of testing ahead... (I would thank some references on how people -or yourself, dev team- are using it in a TDD fashion.

This comes about as I spend a lot of time learning and adapting my workflow to that techniques and now, having to use your platform for most automatizations I need to do, I see myself somehow limited and disregarded my skills in that topic, which is not fair... 😉

Thanks again!

[Emejcz]

Hello

Let's say I have a gallery with 10 items but amount may vary. I want to perform such test to go through all of entries and edit them within one test.
Is it currently possible to loop such procedure in one test or the only option is to set manually 10 tests to go through each gallery item and edit?

[mattgo]

@ramone I appreciate you sharing your perspective and agree that there is room for improvement to make Test Studio much more capable. As we continue expand and refine the Test Studio experience and capabilities, we are looking at how we can provide a test authoring and execution experience that can cater to the needs and workflows of Makers with both technical and non-technical backgrounds.

With respect to TDD, I'm fairly new to the space and have yet to come across any examples that I can share. Most teams that I've spoken with leverage Test Studio for the purpose of functional testing and/or regression testing on core business scenarios.

[mattgo]

@Emejcz there isn't a great way to do this today, but if all of the items in your gallery are visible when the screen loads, this may work:

ForAll(Sequence(CountRows(Gallery1.AllItems)),Select(Gallery1, Value); SetProperty(TextInputInsideGallery.Text, "Value for row"))

I've played around with this, and it works as long as all the items in the gallery are visible. Otherwise with a gallery containing many items, pagination is not triggered, and you only set values for a subset of the items. 

If the above doesn't work separate test steps will likely be your best bet. To handle variable gallery size you could create one test step per item for the maximum number of items you expect, wrapping each in a conditional statement to ensure you're not trying to manipulate gallery items that do not exist.

-Matt.

-Matt.