bd457212d5
* [tests] Add sample tester.
Add a unit project that looks for iOS/macOS/tvOS sample projects in several
repositories, and builds them all.
* [tests][sampletester] Remove known issue which has now been fixed.
* [tests] Only run sample tests on CI in Azure Devops.
* Remove the possibility of automatically running the sample tests with
xharness (so the sample tests won't run on PR bots or internal bots when the
'run-all-tests' label is added). It's still possible to run the sample tests
manually from the xharness web UI.
* Automatically trigger the sample test run in Azure Devops if the
'run-sample-tests' label is applied to a PR (and that PR is executed on
internal Jenkins).
* Fix typo.
* Fix path.
* Verbose output to track down scheduling failure.
* Bump maccore to get improved debug spew.
Diff:
|
||
---|---|---|
.. | ||
Properties | ||
images | ||
.gitignore | ||
BaseTester.cs | ||
Configuration.cs | ||
GitHub.cs | ||
HtmlReport.xslt | ||
Makefile | ||
ProcessHelper.cs | ||
README.md | ||
SampleTester.cs | ||
Samples.cs | ||
TestPlatform.cs | ||
packages.config | ||
sampletester.csproj | ||
sampletester.sln |
README.md
Sample testing
These unit tests clone a series of known repositories that contain sample projects, and build all the relevant projects in those repositories.
It is executed automatically in Azure DevOps every [Saturday][2] for the following branches:
- master
- d16-*
- xcode*
It can also be triggered manually, but have in mind that the commit in question must already have packages (as GitHub statuses).
It's also possible to use the sample tests from one commit, and then test with
Xamarin.iOS/Xamarin.Mac a completely different commit, by setting the
PROVISION_FROM_COMMIT
variable to the commit that's to be tested:
The previous point is still required: the commit to provision from must have packages.
There are two ways to run these tests locally:
- Launching xharness in server mode and execute the "Sample tests" (they're disabled by default).
- Executing
make
in this directory.