Citizen Developer
Timespan
explore our new search
​
Comparing Power Apps Test Studio vs. Power Apps Test Engine
Power Apps
Mar 10, 2025 1:00 AM

Comparing Power Apps Test Studio vs. Power Apps Test Engine

by HubSite 365 about XrmToolCast

Citizen DeveloperWhat's HotPower AppsLearning Selection

Power Apps Test Engine Power Apps Test Studio Web Assembly PowerFx Playground

Key insights

  • Power Apps Test Studio: A low-code solution for recording, creating, and automating tests for canvas apps. It uses Power Fx to make test updates easy by copying and pasting code from the app itself.

  • Power Apps Test Engine: An open-source project that extends the capabilities of Test Studio, offering more robust and flexible testing. It supports canvas apps and aims to support model-driven apps in the future.

  • Advantages of Power Apps Test Engine: Includes features like flexibility through open-source customization, DOM abstraction for stable tests, connector mocking to simulate network calls, and screenshot/video recording for diagnosing failed tests.

  • Test Cases and Suites: In Test Studio, test cases consist of a series of instructions or actions called test steps. These are organized into test suites which run sequentially with shared app states across cases.

  • Best Practices: Automate repetitive or high-impact tests while maintaining manual testing. Keep test cases small and focused on specific functionalities. Use assertions to validate expected results against actual outcomes.

  • Limitations: Current limitations include lack of support for components like nested galleries, media controls, person-type columns, and incompatibility with experimental Git version control features.

Introduction to Power Apps Test Studio and Power Apps Test Engine


In the ever-evolving world of software development, testing is a crucial component that ensures the reliability and efficiency of applications. Microsoft provides two significant tools for testing Power Apps: Power Apps Test Studio and Power Apps Test Engine. These tools are designed to enhance the testing experience for Power Apps developers by offering unique benefits and serving different purposes. In Episode 119 of the XrmToolCast, Daryl and Scott, along with Grant Archibald, Senior Program Manager at Microsoft, discuss the strategic importance of automated testing and how these tools can improve application reliability.

Understanding Power Apps Test Studio


Power Apps Test Studio is a low-code solution that simplifies the process of recording, creating, and automating tests for canvas apps. By utilizing Power Fx, it allows developers to easily update tests by copying and pasting code directly from the app. The Test Studio includes features such as a test step recorder, test editor, and test playback, which can be seamlessly integrated into CI/CD flows using Azure Pipelines. This tool is particularly beneficial for those looking to maintain app quality by continually validating functionality as new changes or updates are deployed.

Exploring Power Apps Test Engine


On the other hand, the Power Apps Test Engine is an open-source project that builds upon the capabilities of Test Studio, offering a more robust and flexible testing platform. It supports canvas apps and is designed to eventually support model-driven apps as well. The Test Engine uses Power Fx for test authoring, allowing for connector mocking, and supports screenshot and video recording. This abstraction of the app's DOM makes tests more stable and easier to maintain, providing a significant advantage over Test Studio.

Advantages of Using Power Apps Test Engine


The Power Apps Test Engine offers several benefits over Test Studio, making it a preferred choice for many developers:
  • Flexibility and Customization: As an open-source tool, the Test Engine allows for community contributions and customization, providing flexibility that Test Studio does not offer.
  • DOM Abstraction: Tests are written using control names defined in Power Apps Studio, eliminating the need to understand the browser DOM or write JavaScript.
  • Connector Mocking: This feature simulates network calls without modifying the app or causing side effects, which is particularly useful for testing apps that interact with external APIs.
  • Screenshot and Video Recording: These features help diagnose failed tests by capturing the exact user experience during test runs.
Additionally, both tools use Power Fx, making it easy for developers familiar with Power Apps to write tests without needing extensive coding knowledge. Moreover, the Test Engine is designed to integrate seamlessly with CI/CD tools like Azure Pipelines and GitHub Actions, making automated testing a part of the development workflow.

Getting Started with Power Apps Test Engine


To begin using the Power Apps Test Engine, there are a few prerequisites and steps to follow:
  • Prerequisites: Ensure that .NET Core 6.0.x SDK and PowerShell are installed on your system.
  • Building the Test Engine: Clone the Test Engine code from GitHub, build the project locally, and install the required browsers (Chromium, Firefox, WebKit).
  • Creating Test Plans: Test plans are defined in YAML format using Power Fx. You can create your own tests or download recorded tests from Test Studio.
Once set up, you can run tests using the Command Line Interface with the PAC CLI command pac test run, providing the path to your test plan file, EnvironmentId, and TenantId. Test results are stored in a .trx file, which includes any screenshots or videos captured during the test run.

What's New About This Approach?


The Power Apps Test Engine represents a significant evolution in automated testing for Power Apps. By leveraging open-source collaboration and the Playwright browser testing platform, it offers a more robust and flexible testing solution compared to Test Studio. The focus on Power Fx for test authoring and DOM abstraction simplifies the testing process, making it more accessible to developers without extensive coding experience. Microsoft is investing in expanding the capabilities of the Test Engine, including support for model-driven apps and tighter integration with CI/CD tools. This will make automated testing an integral part of the development process, ensuring that applications are reliable and efficient.

Conclusion


In summary, the Power Apps Test Studio and Power Apps Test Engine are essential tools for developers aiming to enhance the reliability and efficiency of their applications. While Test Studio offers a low-code solution for recording and automating tests, the Test Engine provides a more flexible and robust platform for comprehensive testing. By understanding the unique benefits and capabilities of each tool, developers can make informed decisions on which tool best suits their testing needs. As Microsoft continues to invest in these tools, the future of automated testing in Power Apps looks promising, paving the way for more reliable and efficient applications.

Power Apps - Enhance Your Apps: Comparing Power Apps Test Studio vs. Power Apps Test Engine

Keywords

Power Apps Test Engine, Power Apps Test Studio, Power Apps testing tools, compare Power Apps test tools, automated testing in Power Apps, benefits of Power Apps Test Engine, features of Power Apps Test Studio, choosing the right Power Apps test tool