[Feature]: Model Driven Application Multi Page Support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- testing-qa
Research direction
Start by tracing ModelDrivenApplicationProvider and the TestState_BeforeTestStepExecuted and TestState_AfterTestStepExecuted event hooks. Check how query string changes are detected and how BuildObjectModel is currently used. Done means multi-page tests refresh the Power Fx object model after URL changes without requiring a full page reload.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Currently, there is a limitation in testing capabilities for model-driven applications that span across multiple pages. This restriction makes it challenging to perform comprehensive end-to-end testing and ensure the seamless functionality of multi-page applications.
Having the ability to test across multiple pages of a model-driven application would greatly enhance the testing process and help identify issues that may arise from navigation and interactions between different pages.
Describe the solution you'd like
I would like the ability for the query string changes in a model-driven application to trigger a reload of the Power Fx Object model. This feature would facilitate the reloading and updating of the object model based on the query string parameters, enabling more dynamic and flexible testing scenarios. It would improve the testing process by allowing tests to simulate different states and configurations of the application without requiring a full page reload.
Describe alternatives you've considered
No response
Additional context?
I would like the ability for the query string changes in a model-driven application to trigger a reload of the Power Fx Object model.
This feature would facilitate the reloading and updating of the object model based on the query string parameters, enabling more dynamic and flexible testing scenarios. Specifically, it would be beneficial if the ModelDrivenApplicationProvider could be updated to monitor changes in the URL during the TestState_BeforeTestStepExecuted and TestState_AfterTestStepExecuted events, and subsequently call the BuildObjectModel method.
This enhancement will improve the testing process by allowing tests to simulate different states and configurations of the application without requiring a full page reload.
- 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
-
priority-0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
StackExchange/StackExchange.Redis#3249 ·
-
[Feat] 조합 영역 구분선 개선 Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100