Introduction

It does not matter if you are a programmer, tester, or end user involved in application development. We will not release the application until we understand that all parts work together. Integration or end-to-end (E2E) testing. In fact, the only important test is the E2E test. This proves that the application can successfully complete the entire business transaction.

The problem is that you may have time to run one E2E test in one release, but you do not have time to repeat every E2E test every time you make a change to your application, or even in every release. At least, you do not have time to manually repeat those tests.

Therefore, here is how to integrate Test Studio into your testing process, including how to handle common problems that are part of using automated E2E regression testing tools.

Overview

Power Apps Test Studio is a low-code solution for creating, organizing and automating tests for canvas apps. In Test Studio, you can use Power Apps expressions to create tests, or you can use a recorder to save your app’s operations and automatically generate expressions. You can also play tests written within Test Studio to verify the functionality of your app, run tests in a web browser, or incorporate automated tests into your app’s deployment process.

Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/test-studio

How does it work?

For this case study, I am going to use a sample application, which we created on Canvas app.

Steps

Before test cases creation, an error will be occurred. “Enable error management in your app”

To resolve the above error, Go to the app settings > Select the Upcoming features > in Experimental tab, enable the Formula-level error management.

Now click on the Open tests button.

In order to create Test cases, we have to create a Test suite in which all test cases are coming which is showing by default.

You can create multiple test cases in a suite and you can also add multiple suites based on your requirement.

Now click on Record button.

Process the steps for the first time manually and complete it.

After completion, the all action will be showing it which were performed manually.

On test case completion, now we need to publish it.

Note: Before publishing it, make sure that you have to Save the app for publishing.

Play test case

Now, click on Play button to start the test case process automation.

The negative record have been submitted through the automate process.

Watch this video to learn how to work with Test Studio

Knowns limitations
While work to provide full control coverage in Power Apps Test Studio is in progress, the following functionality is currently unavailable:

• Components
• Code components written in the Power Apps Component Framework.
• Nested galleries.
• Media controls.
• Formula-level error management experimental feature needs to be turned on for the app.
• Support for controls not listed in the Select and SetProperty
• Person-type columns.

Please share your kind feedback in the comments section. For any query, feel free to Contact us or email us on info@kaispe.com

View our other blogs.

The post Using Test Studio to automate Microsoft PowerApps based IP testing appeared first on KAISPE.

This shows our continuous commitment with customers to help them automate the business processes and achieve high operating efficiency with improved bottom line.

At KAISPE, we pride ourselves on our innovation, expertise, and our continued commitment to ensuring delivery of the highest quality products to our customers. As a Microsoft Certified Partner, we provide solutions backed by industry best practices and standards. We are Microsoft Co-Sell partner and have strong presence on Microsoft marketplaces with our remarkable apps and services.

To learn more, visit https://testing.kaispe.com or call (315) 791-4472. Connect with us on Twitter, LinkedIn, and Facebook.

The post KAISPE Employee Training App is now published on Microsoft AppSource appeared first on KAISPE.

Advantage of this important step is helping Independent Software Vendors (ISV) to monitor and manage their applications which has simply not been possible in the past.

So, by participating in the preview wave, you can experience the benefits of a unified view of PowerApps and Dynamics 365 CE apps which can help you track your apps and get information about cross-tenant apps to better support your customers. You can also learn about your installation base on which you can evaluate the success and potential failure of your application installation attempts. In addition, you can check the installed versions for different clients and environments; this will help you evaluate the impact of maintaining an application and its overall adoption rate.

To access the public preview of ISV Studio, navigate to https://aka.ms/ISVStudio.

Here are the pre-requisites to access the ISV Studio:

• The ISV must be associated with a Microsoft Registered Partner Organization [ISV] that has one or more supported applications published on AppSource. Supported apps include model-driven apps built using Power Apps and Dynamics 365 apps, such as Dynamics 365 Sales and Dynamics 365 Customer Service.
• The ISV must have an Azure Active Directory (AAD) account, and this account must be configured as a contributor or application owner in Partner Center for the specific ISV.
• To be noted at last, ISV Studio does not support applications installed on client sovereign clouds.

Note: If you want more users to gain access to ISV Studio, they can add themselves as application contributors in the Partner Center. Instructions can be found in User Management on the Cloud Partner Portal. For more detail click here.

The post Exploring Microsoft PowerApps ISV Studio appeared first on KAISPE.

In Edit Mode, Go to the Advanced Tools on the left navigation tab and Open Monitor.

Now, you can play the app in edit mode and you can see the monitor screen.

It keeps logging everything you can do with your app. You can click and see the detailed result of every single thing and It is very useful to monitor your request and response.

We can invite people or other developers to share the Monitor screen to shows what’s going on with the App. It is going to generate the hyperlink that sends email automatically to the invited user. You can copy the hyperlink and share it with any communication media do you like. The session will be expired after 1 hour of the invite.

You can monitor the published app as follow.

Click on the Monitor and you will be able to see the monitor screen for the published app.

You can play the published app using the monitor screen.

You can invite and connect the user to the published app.

You can download the result as well. It is saving in a JSON format. You can analyze it later after uploading the JSON file.

The conclusion is, If you have a slow app that’s an option you have to check out the monitor and if you have an end-user that’s complaining about the app being slow or having a problem and you can’t repro the steps so it a perfect thing to do where you can make sure it’s a published app and share the link to the end-user and then monitor what they were doing that cause the app slow or an error occurs. You can easily troubleshoot it.

The post Using Monitor in Microsoft PowerApps appeared first on KAISPE.