Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Automate Testing for Power Apps

You're reading from   Automate Testing for Power Apps A practical guide to applying low-code automation testing tools and techniques

Arrow left icon
Product type Paperback
Published in Oct 2023
Publisher Packt
ISBN-13 9781803236551
Length 352 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Carlos de Huerta Carlos de Huerta
Author Profile Icon Carlos de Huerta
Carlos de Huerta
César Calvo César Calvo
Author Profile Icon César Calvo
César Calvo
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1:Tools for Power Apps Automated Testing
2. Chapter 1: Software Quality and Types of Testing FREE CHAPTER 3. Chapter 2: Power Apps Studio Techniques and Automation Tools 4. Chapter 3: Power Fx Overview and Usage in Testing 5. Chapter 4: Planning Testing in a Power Apps Project 6. Part 2:Tools for Power Apps Automated Testing
7. Chapter 5: Introducing Test Studio – Canvas Apps Testing with a Sample Case Study 8. Chapter 6: Overview of Test Engine, Evolution, and Comparison 9. Chapter 7: Working with Test Engine 10. Chapter 8: Testing Power Apps with Power Automate Desktop 11. Part 3:Extending Power Apps Automated Testing
12. Chapter 9: PCF and Canvas Component Testing 13. Chapter 10: ALM with Test Studio and Test Engine 14. Chapter 11: Mocks with Test Engine 15. Chapter 12: Telemetry and Power Apps 16. Index 17. Other Books You May Enjoy

Testing PCF components with Test Engine

Similar to our approach in the Testing canvas components with Test Engine section, we will employ a YAML file capable of modifying the component’s properties. This strategy, when coupled with the ability to interact with other controls, allows us to conduct a comprehensive end-to-end test of the application we aim to evaluate.

Our initial step typically involves configuring the config.dev.json file. Here’s how:

  1. Configure the environment ID and tenant ID where the application is situated.
  2. Point to the path where our YAML file can be found. In this case, since we’re directly using the provided sample file, we must point to the samples folder and the accompanying YAML file.

    Finally, specify the output folder where we wish to store our results, including the .trx file, logs, videos, and screenshots.

    Figure 9.15 shows how the config.dev.json file should appear:

Figure 9.15 – The config.dev.json file for PCF testing

Figure 9.15 – The...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image