* Pass SYSTEM_ACCESSTOKEN so AzDO reporting can work
* Update azure-pipelines.yml
Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
* Update azure-pipelines.yml
* Third or fourth time's the charm
Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
This adds a new stage that runs for public builds and tests our tool E2E on an iPhone Simulator.
1. We publish the nupkg with the XHarness tool as an artifact (compiled in Debug mode)
2. The integration tests stage sends a Helix job to the staging `OSX.1015.Amd64.iOS.Open` queue
3. The job downloads the nupkg, installs the dotnet tool locally and a gets a test app from Azure storage account, then runs it on a 64 bit Simulator
There are few things where we could improve things but I think we need this asap to have some sort of a validation
We shouldn't be running unit tests in official builds.
I created 4 scripts for clarity (PR/internalbuild.sh/cmd) and in case we would like to customize more in the future.
Fixes: https://github.com/dotnet/xharness/issues/58
The following code use to live under
https://github.com/xamarin/xamarin-macios but has moved here. The code
is what allows to:
* Create a facade applicaton for testing dlls.
* Execute tests in simulator/devices.
This code has been worked on for years and is been tested. There are a
number of unit tests that are currently in xamarin-macios that will be
moved in a different PR to ensure that the tests work correctly in the
new xharness CI. There have been just two cosmetic changes:
* Code formatting: Adapted to the dotnet core style.
* OSS header added.
All tests have been migrated to xUnit.
Co-authored-by: Matt Galbraith <mattgal@microsoft.com>
Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
Přemek Vysoký
dotnet-maestro[bot]
Matt Galbraith
Manuel de la Pena
Matt Galbraith