История

Sebastien Pouliot 00a69e1654 [dotnet] Update `Min*` constants and fix builds for tests (#10835 ) We're bumping the minimum OS versions for all supported platforms https://github.com/dotnet/core/blob/master/release-notes/6.0/6.0-supported-os.md Intro's `Introduced` test is ignored as it require (a lot of) changes. This will be fixed in separate PRs and gradually re-enabled. iOS ``` [FAIL] Introduced : 7573 API with unneeded or incorrect version information ``` tvOS ``` [FAIL] Introduced : 299 API with unneeded or incorrect version information ``` Tracking progress in https://github.com/xamarin/xamarin-macios/issues/10834		2021-03-13 10:38:46 -05:00
..
dont link	[dotnet] Update `Min*` constants and fix builds for tests (#10835 )	2021-03-13 10:38:46 -05:00
link all	[dotnet] Update `Min*` constants and fix builds for tests (#10835 )	2021-03-13 10:38:46 -05:00
link sdk	[dotnet] Update `Min*` constants and fix builds for tests (#10835 )	2021-03-13 10:38:46 -05:00
README.md	[tests] Move linker tests to match introspection directory layout. (#3365 )	2018-02-05 15:09:04 +01:00

README.md

Linker Regression Tests

Most of our unit tests follow the default project configuration, which is "Don't Link" for simulator builds and "Link SDK" for device builds.

The linker tests are different as they set both simulator and device configuration to the same settings. This is the main way to test the linker on the simulator (which is the most common test configuration for our bots)

Note that the spaces in the projects directory names are by design as it ensure our tool chain can cope with them.

dont link

regression testing without using the linker
both simulator and devices are set to "Don't link"

link all

regression testing using the linker on the all assemblies
"Link all assemblies" for both simulator/devices

link sdk

regression testing using the linker on the SDK assemblies
"Link SDK assemblies only" for both simulator/devices