[Fix and Re-enable ] AppModel Area - Feature Test

Open
#115 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
desktop, testing

Research direction

Search for the listed AppModel test methods, especially the CommonDialog, Navigation, and Journal subareas, and inspect their DisabledTestCase attributes. Run an individual test with .\RunTests.cmd /Area=AppModel /Name=, or a subarea with /Subarea=; use /DebugTests when needed. Done means the tests are re-enabled and pass, with any required test fixes made.

Written by the indexing model from the issue text.

Description

The following tests were disabled while open-sourcing the test area:
Common dialogs [ /Subarea=Commondialog ]

  • CommonDialog_OpenCustomPlace
  • CommonDialog_CustomPlaceCases
  • CommonDialog_FileDialogCustomPlaceCases
  • CommonDialog_OpenFileIsThreadModal
  • CommonDialog_OpenFileBeforeShow
  • CommonDialog_SaveFileIsThreadModal
  • CommonDialog_OpenFileOnSecondThread
  • CommonDialog_SaveFileOnSecondThread

Navigation:

  • NavigateUri
  • FragmentNavigationStandalone
  • SandboxExternalContentStandalone
  • NavigationFailedStandalone
  • CredentialPolicyPreserved

Journal

  • NavigateToNull1
  • NavigateToNull2
  • NavigateToNull3
  • NavigateToNull4
  • NavigateToNull5
  • NavigateToNull6
  • AddBackEntryOnEmptyNSXBap
  • JournalEachChangeXbap
  • ReloadCurrentPageXBap
  • GoBackXbap
  • CustomJournalingGoForwardXbap
  • RemoveBackEntryAndGoBackXbap
  • NavigateAwayAndReturnXbap
  • StopNavigationAndReloadXbap
  • NavigateToFragmentXbap

The cause of failure is not known as of now. It may be that the tests themselves need to be fixed.

For re-enabling the tests -

  1. Search for the methods named as above in the code.
  2. Comment out the DisabledTestCase attribute before the test function.

To run the tests in isolation, use the following command:

.\RunTests.cmd /Area=AppModel /Name=<test-name>

is the full name mentioned above in the list

To run a subarea:

.\RunTests.cmd /Area=AppModel /Subarea=<subarea-name>

is the full name of the Subarea (like: Journal, commondialog)

For debugging the tests, add the /DebugTests argument in the command above.

Related issue: [Microsuite] Failures AppModel & Editing #49

Dominant language
C#
Stars
72
Forks
33
Avg merge
3h 58m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/wpf-test

All issues in dotnet/wpf-test

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.