[QUESTION] Is PowerApps-TestEngine still recommended as THE Power Platform Test Automation Engine?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- documentation, testing-qa
Research direction
Start by reviewing the repository documentation and videos referenced in the question, then compare the .NET 8 test engine with the PAC CLI's .NET 9 version. Check issue #645, the CoE Starter Kit references, and the Setup Wizard example. Done means recording a clear, current long-term recommendation for Power Platform test automation and whether PowerApps-TestEngine remains supported.
Written by the indexing model from the issue text.
Description
Does this question already exist in our backlog?
- I have checked and confirm this is a new question.
What is your question?
In the last weeks, I was trying to use the PP TestEngine and evaluate, if it is a good solution to base Power Platform low code test automation on.
When reading some of the documentation and watching the videos from the beginning of the year, I was fascinated.
Meanwhile, it seems, that I have to question, if it is really a good idea to continue investing in it.
.NET version?
The test engine is based on .NET 8, but the PAC CLI is based on .NET 9
I saw, that there is already a bug #645 created for the update of the sample test cases.
no updates
Since months, there are no updates in this repository. Is that, because the .NET version update of the PAC CLI? Most features are still called Preview, but no commit in the project history.
CoE reference?
It is mentioned, that the test engine is used for test automation of the CoE Starter Kit, but when looking in the source code of CoE, I cannot find many test cases created with this Test Engine. Also, the CoE example in this repository refers to a Setup Wizard CoE app as a canvas app, but the current CoE setup wizard is a model driven app, if I am not wrong...
In the CoE, there are still releases provided every month with a huge long list of bugfixes and changes.
Is there no need to test this anymore or was a better way for test automation identified?
So, on the one side, it is really more and more difficult to get anything to work with Test Engine and on the other side, the project currently looks abandoned.
What is the long term recommendation here regarding PP test automation and especially the PP Test Engine?
What component are you experiencing the issue with?
Other
What pac version are you using?
No response
- Dominant language
- C#
- Stars
- 150
- Forks
- 55
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PowerApps-TestEngine
-
new
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
new
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
new
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
question
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in microsoft/PowerApps-TestEngine
Similar issues
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·