Add a launcher that runs the Sandbox suite from any clone - #76
Merged
Merged
Conversation
Winnow-Tests.wsb has to carry absolute HostFolder paths, so it only works where the repository sits at exactly that path; on the maintainer's machine it did not. Invoke-SandboxRun.ps1 writes the same configuration for wherever the clone lives, starts Windows Sandbox, waits for the harness inside it, prints the summary, and exits 0/1/2 for passed/failed/did not run. It refuses to start while a sandbox window is open and waits for a closing VM to exit first: a sandbox started during the previous one's shutdown can boot without its mapped folders, and the harness then never runs. Verified end to end: 30 passed, 0 failed, 1 skipped by design; with -CloseWhenDone the sandbox is closed and the temporary .wsb removed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Winnow-Tests.wsbneeds absoluteHostFolderpaths, so it only works where the repository sits at exactly that path (it did not on the maintainer's machine).Tests/Integration/Sandbox/Invoke-SandboxRun.ps1writes the same configuration for the actual clone path, starts Windows Sandbox, waits for the harness, prints the summary, and exits0passed /1failed /2did not run.It refuses to start while a sandbox window is open and waits for a closing VM to exit, because a sandbox started during the previous one's shutdown can boot without its mapped folders (seen in practice: the harness never ran).
README and the
.wsbcomment now point at the launcher.Testing: static validation clean (133 files). Ran the launcher end to end: 30 passed, 0 failed, 1 skipped by design, exit 0; with
-CloseWhenDonethe sandbox closed and the temporary.wsbwas removed. No product code changed.