Workspaceslib ut
This pull request introduces a new unit testing framework for the WorkspacesLib module, adds test coverage for various utilities, and integrates the new test project into the build system. Key changes include adding the WorkspacesLibUnitTests project, implementing tests for AppUtils, JsonUtils, and PwaHelper, and updating the build configuration to include the new test project.
Unit Tests Added:
AppUtilsTests:- Added comprehensive tests for methods such as
GetCurrentFolder,IsEdge,IsChrome, andIsSteamGameto validate their behavior under various conditions.
- Added comprehensive tests for methods such as
JsonUtilsTests:- Implemented tests for reading and writing workspace data, including scenarios for invalid JSON, non-existent files, and valid workspace lists.
PwaHelperTests:- Added tests to ensure the stability of
PwaHelpermethods, such asGetEdgeAppId,GetChromeAppId, andSearchPwaName, even with invalid or empty inputs.
- Added tests to ensure the stability of
Build System Updates:
- New Test Project Integration:
- Added the
WorkspacesLibUnitTestsproject to the solution filePowerToys.slnwith appropriate dependencies. - Updated build configurations to include the new test project for both Debug and Release builds across architectures. [1] [2]
- Added the
Pipeline Adjustments:
- Test Discovery:
- Updated the pipeline configuration in
.pipelines/v2/templates/job-build-project.ymlto discover the newWorkspacesLibUnitTests.dllduring test runs.
- Updated the pipeline configuration in
@check-spelling-bot Report
:red_circle: Please review
See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.
Unrecognized words (1)
notsteam
To accept these unrecognized words as correct, you could run the following commands
... in a clone of the [email protected]:vanzue/PowerToys.git repository
on the workspaceslib-ut branch (:information_source: how do I use this?):
curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/c635c2f3f714eec2fcf27b643a1919b9a811ef2e/apply.pl' |
perl - 'https://github.com/microsoft/PowerToys/actions/runs/15605601414/attempts/1' &&
git commit -m 'Update check-spelling metadata'
If the flagged items are :exploding_head: false positives
If items relate to a ...
-
binary file (or some other file you wouldn't want to check at all).
Please add a file path to the
excludes.txtfile matching the containing file.File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.
^refers to the file's path from the root of the repository, so^README\.md$would exclude README.md (on whichever branch you're using). -
well-formed pattern.
If you can write a pattern that would match it, try adding it to the
patterns.txtfile.Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.
Note that patterns can't match multiline strings.
@copilot Fix the pipeline spell checking error
@check-spelling-bot Report
:red_circle: Please review
See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.
Unrecognized words (1)
notsteam
To accept these unrecognized words as correct, you could run the following commands
... in a clone of the [email protected]:vanzue/PowerToys.git repository
on the workspaceslib-ut branch (:information_source: how do I use this?):
curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/c635c2f3f714eec2fcf27b643a1919b9a811ef2e/apply.pl' |
perl - 'https://github.com/microsoft/PowerToys/actions/runs/15606368363/attempts/1' &&
git commit -m 'Update check-spelling metadata'
If the flagged items are :exploding_head: false positives
If items relate to a ...
-
binary file (or some other file you wouldn't want to check at all).
Please add a file path to the
excludes.txtfile matching the containing file.File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.
^refers to the file's path from the root of the repository, so^README\.md$would exclude README.md (on whichever branch you're using). -
well-formed pattern.
If you can write a pattern that would match it, try adding it to the
patterns.txtfile.Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.
Note that patterns can't match multiline strings.
Verified tests included and passed.