https://www.linkedin.com/posts/grantarchibald_github-microsoftpower-cat-copilot-studio-kit-activity-7313656444921266177-2cJb?utm_source=share&utm_medium=member_android&rcm=ACoAAACK7q0B044fWK4SLXbFtLjTJxKBu4t8hOs
GitHub - microsoft/Power-CAT-Copilot-Studio-Kit | Grant Archibald | 39 comments
🚀 Unlocking the Power of Automated Testing in Power Platform: People, Process, and Tooling 🚀 When we talk about Automated Testing, many think it's purely a technical topic. But the truth is, it requires collaboration across the entire business to be successful. 🧠In the age of AI previous assumptions on the complexity of Automated Testing can be revisited. What can be abstracted and automated? How can we learn from the past and bring these approaches to a new community of users? 🤔 Got your interest? If so check out this ongoing post as we as a Power CAT Engineering team look at apply automated testing to the projects we build as an example. People: Explore who is needed in the process, look at goals and how Automated Testing plays an important part of that process. Process: It is a key part of lifecycle of Planning, Build, Test, Deploy and Monitoring show how this can be implemented. Tooling: ❓👀 Want to follow along with the requirements and code elements as we add them? If so, you can watch the GitHub feature request added to https://lnkd.in/gCQ9wtQM Example: 👉🏼For this discussion we will use the Power CAT Copilot Studio Kit https://lnkd.in/gwHK3qPw as a great example of this People, Process and Tooling. Goal: What's the goal for this post? - Share the journey as we take a real solution and test it using Test Engine - Look at the journey from People, Process and Tooling point of view not just a technical point of view - Demonstrate how Test Engine applied not only to Power Apps but across the platform - Look at how AI can be applied to the process to scale this approach - Identify and share patterns and abstractions to make the process easier - Be a part of the feedback process, what would you like to see next? - Use this process to drive the next set of the learning documentation I am looking forward to sharing more of this journey for our team from a People, Processing and Tooling point of view and how the wider community can use these learnings to help the solution you build. Pattern Summary: ✅Pattern 1: Think about people and process (aka.ms/ppat/1) ✅Pattern 2: Plan your implementation path (aka.ms/ppat/2) ✅Pattern 3: Choose your execution method. (aka.ms/ppat/3) ✅Pattern 4: Work with your security model (aka.ms/ppat/4) ✅Pattern 5: Track Progress and Celebrate the wins (aka.ms/ppat/5) ✅Pattern 6: Choose the correct level of abstraction (aka.ms/ppat/6) ✅Pattern 7: Use Power Fx to control Test Data State for integration tests (aka.ms/ppat/7) ✅Pattern 8: Don't think in silos (aka.ms/ppat/8) ✅Pattern 9: Use Power Fx Functions to abstract complexity and promote reuse (aka.ms/ppat/9) #PowerPlatform #AutomatedTesting #Example #CopilotStudioKit | 39 comments on LinkedIn
kailashr2k
Parents For Future 
Jukka Niiranen
Barret