| Commit message (Collapse) | Author | Files | Lines |
|
firewall rules.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
Install both the x64 AND the x86 versions of Windows Desktop Runtime.
Needed for the Burn Integration tests.
And having dotnet files in the sandbox directory was annoying, so put
them all into an assets directory
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
Removed ARM64/AMD64 folders for dotnet, the Sandbox MUST match the host
here, so no point downloading the installer for the non-host platform.
Debugger could probably be reduced in the same manner, but have not in
this iteration.
Have also added a simple README, just to explain (very basic) operation.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
Fix a couple of copy-paste errors in the "don't have files from
host in Sandbox" path also.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
Not sure if it's ideal, but it works..
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
By default enable /noauth and /anyuser on the debugger, and don't show the
security warning (/nosecuritywarn).
It'll still show the firewall warning prompt. Default settings should be
fine for firewall (Private networks).
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
And a fix up for the tests not launching the first try
(due to delayed expansion).
Also fixed up the copying of the debugger files.
|
|
It will now prompt for configuring the Remote Debugger if it can find it
on the host when doing the setup.
And will prompt within the Sandbox to run the Debugger at startup if found
It will also show the host-local IP address to connect to the debugger.
In addition, it will display a small menu to allow for simple selection of
a particular runtests.cmd version to execute.
I still haven't found a good way to get a debugger attached into the msiexec
environment without already having a coded breakpoint in, however.
Also added this sandbox folder to .gitignore, so that artifacts from here
aren't committed into the repo
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
Will automatically 'install' dotnet/dotnet sdk into sandbox at startup
based on versions in 'src/test/sandbox/{AMD64,ARM64}' (dotnet-runtime.zip
& dotnet-sdk.zip).
Running ./src/test/sandbox/setup_sandbox.bat will download the required
files (when run on the host).
If the files aren't available, and the guest has network, it will attempt
to download the files itself at startup.
Still to be done:
* menu at startup to allow easy one button selection of which particular
test set to run
* investigation into whether vstest.console.exe can be used to capture test
execution, and possibly have the sandbox available as a test runner, so MSI
tests could be run in the sandbox directly from the dev environment.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|