f29592e7cf
* [tests][sampletester] Add nuget.org single feed to sampletester Since we no longer upstream to nuget.org our sampletester is not able to find packages so we create a nuget config file with a single source to nuget.org to fix it and still be compliant. * [tests][sampletester] Remove ConferenceVision sample, it no longer exists * [tests][sampletester] Double TimeOut for a couple of tests |
||
|---|---|---|
| .. | ||
| BaselineTest | ||
| Properties | ||
| images | ||
| .gitignore | ||
| BaseTester.cs | ||
| Configuration.cs | ||
| GitHub.cs | ||
| HtmlReport.xslt | ||
| Makefile | ||
| ProcessHelper.cs | ||
| README.md | ||
| SampleTester.cs | ||
| Samples.cs | ||
| TestPlatform.cs | ||
| 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 for the listed branches. This includes:
maind16-x- i.e. one or many active release branchesxcodeY- i.e. the current xcode beta feature branchmono-202z-zz- i.e. the mono integration branches (new one every two months)
where x, Y and z needs to be periodically updated as new branches are created (e.g. d16-x) and old ones are merged into main (e.g. xcodeY and mono-202z-zz).
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
makein this directory.