xamarin
/
xamarin-macios
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
xamarin-macios/tests/xharness/xharness.csproj

145 строки
6.9 KiB
XML
Исходник Обычный вид История

[Harness] Split out classes from Jenkins.cs to separate files (#8046) Co-authored-by: Premek Vysoky <prvysoky@microsoft.com>
2020-03-06 14:00:34 +03:00
<?xml version="1.0" encoding="utf-8"?>
[tests] Import
2016-05-26 16:06:52 +03:00
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
<Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
<ProductVersion>8.0.30703</ProductVersion>
<SchemaVersion>2.0</SchemaVersion>
<ProjectGuid>{E1F53F80-8399-499B-8017-C414B9CD263B}</ProjectGuid>
<OutputType>Exe</OutputType>
[Harness] Split out Targets, Utils and remove external links (#8061) * [Harness] Refactor process management to be testable. Move all the extension methods to a class. After this refactor, we will be able to DI the manager in the other classes and assert that the processes are called with the correct parameters without the need of launching them. Also added tests for the manager. We create a dummy console app that will be executed by the tests. The console app has a number of parameters that will be used to ensure that the new process behaves as we want: - Use the passed exit code. - Create child proecesses if needed. - Sleep to force a timeout. - Writer messages to stdout and stderr. Our tests call the dummy app and ensures that the results match the behaviour expected by the dummy app. * Apply suggestions from code review Co-Authored-By: Přemek Vysoký <premek.vysoky@microsoft.com> * Move out utils into a separate namespace * Move Cache to the test project * Fix namespaces after merge * Remove unneeded code * Move Target files * Sort csproj * Refactor Targets * Rename Cache to TempDirectory * Fix using * Move ProjectFileExtensions * Remove dead code * Move Extensions * Add empty StringUtilsTests * Add StringUtils tests * Revert refactorings * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Add better formatarguments test * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Manuel de la Pena <mandel@microsoft.com> Co-authored-by: Premek Vysoky <prvysoky@microsoft.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-03-10 15:12:33 +03:00
<RootNamespace>Xharness</RootNamespace>
[tests] Import
2016-05-26 16:06:52 +03:00
<AssemblyName>xharness</AssemblyName>
Switch to mono archive and remove submodule
2019-05-12 19:06:06 +03:00
<TargetFrameworkVersion>v4.7.2</TargetFrameworkVersion>
[xharness] Add support for running the generator tests in .NET mode. This also meant adding support for running .NET tests in xharness. Some refactoring was done to extract common code to shared members, in order to avoid duplicating a lot of code.
2020-03-09 14:56:38 +03:00
<LangVersion>8.0</LangVersion>
[tests] Import
2016-05-26 16:06:52 +03:00
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<Optimize>false</Optimize>
<OutputPath>.</OutputPath>
<DefineConstants>DEBUG;</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
<ConsolePause>false</ConsolePause>
[xharness] Make 64-bits. Avoids any problems with 32-bit OOM conditions (which can take a while to diagnose, because random things start happening).
2017-02-17 18:59:06 +03:00
<PlatformTarget>x64</PlatformTarget>
[Harness] Refactor simulators and devices listing. (#8086) Moved the implementations under Hardare. Add the following to simplify the testing of the AppRunner: 1. Add interfaces for the listing/loading of devices and simulators. 2. Add a special class for mlaunch args. That way we are sure that arguments are correctly passed and we do not have typos. 3. Added tests for the new classes and for the device and devices classes. 4. Added tests for the management of the TCC db. Tests for the SimDevice and Simulators will come in a following PR. The only reason for it is that I realize that the commit was getting to large. Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
2020-03-12 00:06:40 +03:00
<LangVersion>8.0</LangVersion>
[tests] Import
2016-05-26 16:06:52 +03:00
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
<DebugType>full</DebugType>
<Optimize>true</Optimize>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
<Externalconsole>true</Externalconsole>
<OutputPath>bin\Release</OutputPath>
[Harness] Refactor simulators and devices listing. (#8086) Moved the implementations under Hardare. Add the following to simplify the testing of the AppRunner: 1. Add interfaces for the listing/loading of devices and simulators. 2. Add a special class for mlaunch args. That way we are sure that arguments are correctly passed and we do not have typos. 3. Added tests for the new classes and for the device and devices classes. 4. Added tests for the management of the TCC db. Tests for the SimDevice and Simulators will come in a following PR. The only reason for it is that I realize that the commit was getting to large. Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
2020-03-12 00:06:40 +03:00
<LangVersion>8.0</LangVersion>
[tests] Import
2016-05-26 16:06:52 +03:00
</PropertyGroup>
[xharness] Major rewrite (add server mode, add device support, add today extension support). * Add a server mode, which launches a web server (and a web page) that can be used to interactively run tests and view their results. * Add support for running test assemblies in a today extension (generating a new set of projects, similar to how we generate tvOS/watchOS projects based on the iOS project, we now generate a today extension project in addition to the tvOS and watchOS projects). * Load all the different tests (and show them in the html report, although they show up as 'ignored'), even for disabled/ignored tests. This makes disabled/ignored tests more visible, and also makes it possible to actually run them using the embedded web server. * Add support for running tests on device. Tests will be executed on multiple devices simulatenously (any connected devices will be used).
2017-01-04 21:45:26 +03:00
<PropertyGroup Condition=" '$(RunConfiguration)' == 'Default' ">
<StartAction>Project</StartAction>
<StartArguments>--verbose --jenkins:server --autoconf --rootdir ..</StartArguments>
</PropertyGroup>
[xharness] Add project configuration to run Jenkins-style tests. (#3249)
2018-01-18 09:16:24 +03:00
<PropertyGroup Condition=" '$(RunConfiguration)' == 'Run Jenkins tests' ">
<StartAction>Project</StartAction>
<StartArguments>--verbose --jenkins --autoconf --rootdir ..</StartArguments>
</PropertyGroup>
[xharness] Add run configuration to project to easily debug internal jenkins execution. (#4266)
2018-06-15 12:11:25 +03:00
<PropertyGroup Condition=" '$(RunConfiguration)' == 'Run Jenkins (internal) tests' ">
<StartAction>Project</StartAction>
<StartArguments>--verbose --jenkins --autoconf --rootdir .. --label run-all-tests,skip-ios-device-tests,skip-mac-32-tests --markdown-summary=../TestSummary.md</StartArguments>
[xharness] Add project configuration to run Jenkins-style tests. (#3249)
2018-01-18 09:16:24 +03:00
</PropertyGroup>
[xharness] Add device test configuration to project file. (#4143) Add a device test configuration to the project file so that it's easier to debug xharness when running device tests.
2018-05-29 18:20:30 +03:00
<PropertyGroup Condition=" '$(RunConfiguration)' == 'Run device tests' ">
<StartAction>Project</StartAction>
<StartArguments>--verbose --jenkins --autoconf --rootdir .. --label=skip-mac-tests,skip-ios-simulator-tests,skip-ios-msbuild-tests,skip-system-permission-tests,run-ios-device-tests,run-ios-extensions-tests --markdown-summary=../TestSummary.md --label=run-watchos-tests,skip-bcl-tests</StartArguments>
<EnvironmentVariables>
<Variable name="MONO_ENV_OPTIONS" value="--trace=E:all" />
</EnvironmentVariables>
</PropertyGroup>
[xharness] Add project configurations to run & debug Makefile generation. (#4739) This also required a minor fix to allow relative directories as the root directory.
2018-09-03 08:56:44 +03:00
<PropertyGroup Condition=" '$(RunConfiguration)' == 'Makefile.inc' ">
<StartAction>Project</StartAction>
<StartArguments>--configure --autoconf --rootdir ..</StartArguments>
</PropertyGroup>
<PropertyGroup Condition=" '$(RunConfiguration)' == 'Makefile-mac.inc' ">
<StartAction>Project</StartAction>
<StartArguments>--configure --autoconf --rootdir .. --mac </StartArguments>
</PropertyGroup>
[tests] Import
2016-05-26 16:06:52 +03:00
<ItemGroup>
<Reference Include="System" />
<Reference Include="System.Xml" />
[tests] Implement support in xharness for running the simulator tests grouped by simulator, and write out an html report.
2016-06-06 13:48:53 +03:00
<Reference Include="System.Web" />
[xharness] Download mlaunch if we don't have a local copy.
2016-06-16 02:55:06 +03:00
<Reference Include="Mono.Posix" />
[xharness] Add support to configure which tests to run on Jenkins by using labels on pull requests. (#1082)
2016-11-02 18:46:32 +03:00
<Reference Include="System.Runtime.Serialization" />
[Tests] Add a new iOS app to run the xunit and nunit tests (#4914) Mono know provides a set of testing assemblies that contain the tests to be ran in each of the supported platforms. This commit adds the following: 1. Two different runners that can be used to execute NUnit and xUnit tests. 2. The necessary glue to get xharness to run the new tests and report the results. 3. A new test that will ensure that if mono adds new tests, xharness will report failures if the tests are not run or not ignored.
2018-11-16 21:31:40 +03:00
<Reference Include="mscorlib" />
[XHarness] Add logs to VSTS test runs. (#7844) As per the documentation of the VSTS test uploader (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-test-results?view=azure-devops&tabs=yaml#attachments-support) the tests support the addition of attachments. We want to be able to access the logs of the different tests runs, this is achieved the following way: 1. Move TouchUnit to use NUnit V3 which allows to add attachments. 2. Once the tests are ran, add the attachments to the following nodes: 1. The very first test-suite. This will allow to have the logs for succesul tests. 2. Add logs to failing tests. Reduces the number of clicks to be done to access to the logs when a test case fails. 3. Modify the assembly name of the test-suit to match the name of the application. This ensures two things. 1. We have a consistent name for the file column in VSTS, that can be used to see recurrent failing tests. 2. The name is more readable, since if not, it will contain the UUID of the device. Logs are not added to succesful tests because it will have the following problems: * Larger data storage usage. * Longer upload time. The addtion of the logs per tests (succesful or failed) was tested and resulted in an upload time LONGER than 6 hours for all TouchUnit, NUnit blc tests and xUnit bcl tests. In order for this to be useful, the task in the pipeline SHOULD NOT merge test runs. We should have a test run PER application so that we do not mix the logs. Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-02-11 22:03:16 +03:00
<Reference Include="System.Xml.Linq" />
[tests] Import
2016-05-26 16:06:52 +03:00
</ItemGroup>
Switch to mono archive and remove submodule
2019-05-12 19:06:06 +03:00
<ItemGroup>
[Harness] Move code to a shared library (#8234) - Code that will later be moved to the `dotnet/xharness` repo is first moved to an isolated project before it will be extracted to the new repo and NuGetified - New project for the shared code and new test project for tests accompanying the moved code are created - Only Factories are left behind that are used only by XHarness
2020-04-01 20:32:21 +03:00
<PackageReference Include="Mono.Options" Version="6.6.0.161" />
Switch to mono archive and remove submodule
2019-05-12 19:06:06 +03:00
</ItemGroup>
[tests] Import
2016-05-26 16:06:52 +03:00
<ItemGroup>
[Harness] Split out Targets, Utils and remove external links (#8061) * [Harness] Refactor process management to be testable. Move all the extension methods to a class. After this refactor, we will be able to DI the manager in the other classes and assert that the processes are called with the correct parameters without the need of launching them. Also added tests for the manager. We create a dummy console app that will be executed by the tests. The console app has a number of parameters that will be used to ensure that the new process behaves as we want: - Use the passed exit code. - Create child proecesses if needed. - Sleep to force a timeout. - Writer messages to stdout and stderr. Our tests call the dummy app and ensures that the results match the behaviour expected by the dummy app. * Apply suggestions from code review Co-Authored-By: Přemek Vysoký <premek.vysoky@microsoft.com> * Move out utils into a separate namespace * Move Cache to the test project * Fix namespaces after merge * Remove unneeded code * Move Target files * Sort csproj * Refactor Targets * Rename Cache to TempDirectory * Fix using * Move ProjectFileExtensions * Remove dead code * Move Extensions * Add empty StringUtilsTests * Add StringUtils tests * Revert refactorings * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Add better formatarguments test * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Manuel de la Pena <mandel@microsoft.com> Co-authored-by: Premek Vysoky <prvysoky@microsoft.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-03-10 15:12:33 +03:00
<Compile Include="AppRunner.cs" />
[Harness] Completely remove the BCL prefix from the test importer. (#8224) Remove the last BCLPrefix and move the InfoPlistGenerator to the managed namespace since it is part of the managed template.
2020-04-03 18:01:56 +03:00
<Compile Include="BCLTestImportTargetFactory.cs" />
[Harness] Move code to a shared library (#8234) - Code that will later be moved to the `dotnet/xharness` repo is first moved to an isolated project before it will be extracted to the new repo and NuGetified - New project for the shared code and new test project for tests accompanying the moved code are created - Only Factories are left behind that are used only by XHarness
2020-04-01 20:32:21 +03:00
<Compile Include="CrashSnapshotReporterFactory.cs" />
[Harness] Remove launchTimeout parameter from TestReporter, move factories (#8322)
2020-04-08 18:32:47 +03:00
<Compile Include="DeviceLoaderFactory.cs" />
[Harness] Move code to a shared library (#8234) - Code that will later be moved to the `dotnet/xharness` repo is first moved to an isolated project before it will be extracted to the new repo and NuGetified - New project for the shared code and new test project for tests accompanying the moved code are created - Only Factories are left behind that are used only by XHarness
2020-04-01 20:32:21 +03:00
<Compile Include="DeviceLogCapturerFactory.cs" />
[Harness] Split out Targets, Utils and remove external links (#8061) * [Harness] Refactor process management to be testable. Move all the extension methods to a class. After this refactor, we will be able to DI the manager in the other classes and assert that the processes are called with the correct parameters without the need of launching them. Also added tests for the manager. We create a dummy console app that will be executed by the tests. The console app has a number of parameters that will be used to ensure that the new process behaves as we want: - Use the passed exit code. - Create child proecesses if needed. - Sleep to force a timeout. - Writer messages to stdout and stderr. Our tests call the dummy app and ensures that the results match the behaviour expected by the dummy app. * Apply suggestions from code review Co-Authored-By: Přemek Vysoký <premek.vysoky@microsoft.com> * Move out utils into a separate namespace * Move Cache to the test project * Fix namespaces after merge * Remove unneeded code * Move Target files * Sort csproj * Refactor Targets * Rename Cache to TempDirectory * Fix using * Move ProjectFileExtensions * Remove dead code * Move Extensions * Add empty StringUtilsTests * Add StringUtils tests * Revert refactorings * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Add better formatarguments test * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Manuel de la Pena <mandel@microsoft.com> Co-authored-by: Premek Vysoky <prvysoky@microsoft.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-03-10 15:12:33 +03:00
<Compile Include="GitHub.cs" />
<Compile Include="Harness.cs" />
<Compile Include="Jenkins\Jenkins.cs" />
[Harness] Split out classes from Jenkins.cs to separate files (#8046) Co-authored-by: Premek Vysoky <prvysoky@microsoft.com>
2020-03-06 14:00:34 +03:00
<Compile Include="Jenkins\TestTasks\AggregatedRunSimulatorTask.cs" />
<Compile Include="Jenkins\TestTasks\BuildProjectTask.cs" />
<Compile Include="Jenkins\TestTasks\BuildToolTask.cs" />
Merge remote-tracking branch 'origin/master' into dotnet-bgen
2020-03-10 15:45:50 +03:00
<Compile Include="Jenkins\TestTasks\DotNetBuildTask.cs" />
<Compile Include="Jenkins\TestTasks\DotNetTestTask.cs" />
[Harness] Split out classes from Jenkins.cs to separate files (#8046) Co-authored-by: Premek Vysoky <prvysoky@microsoft.com>
2020-03-06 14:00:34 +03:00
<Compile Include="Jenkins\TestTasks\MacExecuteTask.cs" />
<Compile Include="Jenkins\TestTasks\MacTask.cs" />
<Compile Include="Jenkins\TestTasks\MakeTask.cs" />
[Harness] Split out Targets, Utils and remove external links (#8061) * [Harness] Refactor process management to be testable. Move all the extension methods to a class. After this refactor, we will be able to DI the manager in the other classes and assert that the processes are called with the correct parameters without the need of launching them. Also added tests for the manager. We create a dummy console app that will be executed by the tests. The console app has a number of parameters that will be used to ensure that the new process behaves as we want: - Use the passed exit code. - Create child proecesses if needed. - Sleep to force a timeout. - Writer messages to stdout and stderr. Our tests call the dummy app and ensures that the results match the behaviour expected by the dummy app. * Apply suggestions from code review Co-Authored-By: Přemek Vysoký <premek.vysoky@microsoft.com> * Move out utils into a separate namespace * Move Cache to the test project * Fix namespaces after merge * Remove unneeded code * Move Target files * Sort csproj * Refactor Targets * Rename Cache to TempDirectory * Fix using * Move ProjectFileExtensions * Remove dead code * Move Extensions * Add empty StringUtilsTests * Add StringUtils tests * Revert refactorings * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Add better formatarguments test * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Manuel de la Pena <mandel@microsoft.com> Co-authored-by: Premek Vysoky <prvysoky@microsoft.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-03-10 15:12:33 +03:00
<Compile Include="Jenkins\TestTasks\MSBuildTask.cs" />
[Harness] Split out classes from Jenkins.cs to separate files (#8046) Co-authored-by: Premek Vysoky <prvysoky@microsoft.com>
2020-03-06 14:00:34 +03:00
<Compile Include="Jenkins\TestTasks\NUnitExecuteTask.cs" />
<Compile Include="Jenkins\TestTasks\RunDeviceTask.cs" />
<Compile Include="Jenkins\TestTasks\RunSimulatorTask.cs" />
<Compile Include="Jenkins\TestTasks\RunTestTask.cs" />
<Compile Include="Jenkins\TestTasks\RunXITask.cs" />
<Compile Include="Jenkins\TestTasks\RunXtroTask.cs" />
[Harness] Move to create a more general TestTasks class to be reused. (#8286) Some of the Jenkins test tasks are very useful and do A LOT of stuff. So we try to generalize the base class, to later be able to share the most usebul ones in the shared lib. Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-04-08 03:20:38 +03:00
<Compile Include="Jenkins\TestTasks\AppleTestTask.cs" />
[Harness] Split out Targets, Utils and remove external links (#8061) * [Harness] Refactor process management to be testable. Move all the extension methods to a class. After this refactor, we will be able to DI the manager in the other classes and assert that the processes are called with the correct parameters without the need of launching them. Also added tests for the manager. We create a dummy console app that will be executed by the tests. The console app has a number of parameters that will be used to ensure that the new process behaves as we want: - Use the passed exit code. - Create child proecesses if needed. - Sleep to force a timeout. - Writer messages to stdout and stderr. Our tests call the dummy app and ensures that the results match the behaviour expected by the dummy app. * Apply suggestions from code review Co-Authored-By: Přemek Vysoký <premek.vysoky@microsoft.com> * Move out utils into a separate namespace * Move Cache to the test project * Fix namespaces after merge * Remove unneeded code * Move Target files * Sort csproj * Refactor Targets * Rename Cache to TempDirectory * Fix using * Move ProjectFileExtensions * Remove dead code * Move Extensions * Add empty StringUtilsTests * Add StringUtils tests * Revert refactorings * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Add better formatarguments test * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Manuel de la Pena <mandel@microsoft.com> Co-authored-by: Premek Vysoky <prvysoky@microsoft.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-03-10 15:12:33 +03:00
<Compile Include="MakefileGenerator.cs" />
<Compile Include="MonoNativeInfo.cs" />
[tests] Import
2016-05-26 16:06:52 +03:00
<Compile Include="Program.cs" />
<Compile Include="Properties\AssemblyInfo.cs" />
[Harness] Remove launchTimeout parameter from TestReporter, move factories (#8322)
2020-04-08 18:32:47 +03:00
<Compile Include="SimulatorLoaderFactory.cs" />
[Harness] Split out Targets, Utils and remove external links (#8061) * [Harness] Refactor process management to be testable. Move all the extension methods to a class. After this refactor, we will be able to DI the manager in the other classes and assert that the processes are called with the correct parameters without the need of launching them. Also added tests for the manager. We create a dummy console app that will be executed by the tests. The console app has a number of parameters that will be used to ensure that the new process behaves as we want: - Use the passed exit code. - Create child proecesses if needed. - Sleep to force a timeout. - Writer messages to stdout and stderr. Our tests call the dummy app and ensures that the results match the behaviour expected by the dummy app. * Apply suggestions from code review Co-Authored-By: Přemek Vysoký <premek.vysoky@microsoft.com> * Move out utils into a separate namespace * Move Cache to the test project * Fix namespaces after merge * Remove unneeded code * Move Target files * Sort csproj * Refactor Targets * Rename Cache to TempDirectory * Fix using * Move ProjectFileExtensions * Remove dead code * Move Extensions * Add empty StringUtilsTests * Add StringUtils tests * Revert refactorings * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Add better formatarguments test * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Manuel de la Pena <mandel@microsoft.com> Co-authored-by: Premek Vysoky <prvysoky@microsoft.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-03-10 15:12:33 +03:00
<Compile Include="SolutionGenerator.cs" />
<Compile Include="Targets\iOSTarget.cs" />
<Compile Include="Targets\MacTarget.cs" />
<Compile Include="Targets\Target.cs" />
<Compile Include="Targets\TodayExtensionTarget.cs" />
<Compile Include="Targets\TVOSTarget.cs" />
<Compile Include="Targets\UnifiedTarget.cs" />
<Compile Include="Targets\WatchOSTarget.cs" />
<Compile Include="TestPlatform.cs" />
[tests] Implement support in xharness for running the simulator tests grouped by simulator, and write out an html report.
2016-06-06 13:48:53 +03:00
<Compile Include="TestProject.cs" />
[Harness] Merge the Generator and the Factory in a same object and rename namespace. (#8222) The Generator and the Factory classes are a xamarin-macios thing. Initially, they were separated because the code that generated the bcl tests was not inside xharness. That is not longer the case. We can merge both classes, generalize the namespace and be more prepared to move out of the xamarin-macios repo.
2020-03-31 06:23:33 +03:00
<Compile Include="TestImporter\Xamarin\AssemblyLocator.cs" />
<Compile Include="TestImporter\Xamarin\ProjectFilter.cs" />
<Compile Include="TestImporter\Xamarin\AssemblyDefinitionFactory.cs" />
<Compile Include="TestImporter\Xamarin\TestAssemblyDefinition.cs" />
[Harness] Move to create a more general TestTasks class to be reused. (#8286) Some of the Jenkins test tasks are very useful and do A LOT of stuff. So we try to generalize the base class, to later be able to share the most usebul ones in the shared lib. Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-04-08 03:20:38 +03:00
<Compile Include="TestTasks\TestTask.cs" />
<Compile Include="TestTasks\IAcquiredResource.cs" />
<Compile Include="TestTasks\Resource.cs" />
<Compile Include="TestTasks\Resources.cs" />
[Tests] Add a new iOS app to run the xunit and nunit tests (#4914) Mono know provides a set of testing assemblies that contain the tests to be ran in each of the supported platforms. This commit adds the following: 1. Two different runners that can be used to execute NUnit and xUnit tests. 2. The necessary glue to get xharness to run the new tests and report the results. 3. A new test that will ensure that if mono adds new tests, xharness will report failures if the tests are not run or not ignored.
2018-11-16 21:31:40 +03:00
</ItemGroup>
<ItemGroup>
[mtouch/mmp] Use a single SdkVersions.cs in tools/common. (#8318) No need to have two identical files around.
2020-04-08 17:19:34 +03:00
<Compile Include="..\..\tools\common\SdkVersions.cs">
[Harness] Split out Targets, Utils and remove external links (#8061) * [Harness] Refactor process management to be testable. Move all the extension methods to a class. After this refactor, we will be able to DI the manager in the other classes and assert that the processes are called with the correct parameters without the need of launching them. Also added tests for the manager. We create a dummy console app that will be executed by the tests. The console app has a number of parameters that will be used to ensure that the new process behaves as we want: - Use the passed exit code. - Create child proecesses if needed. - Sleep to force a timeout. - Writer messages to stdout and stderr. Our tests call the dummy app and ensures that the results match the behaviour expected by the dummy app. * Apply suggestions from code review Co-Authored-By: Přemek Vysoký <premek.vysoky@microsoft.com> * Move out utils into a separate namespace * Move Cache to the test project * Fix namespaces after merge * Remove unneeded code * Move Target files * Sort csproj * Refactor Targets * Rename Cache to TempDirectory * Fix using * Move ProjectFileExtensions * Remove dead code * Move Extensions * Add empty StringUtilsTests * Add StringUtils tests * Revert refactorings * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> * Add better formatarguments test * Update tests/xharness/Utilities/StringUtils.cs Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com> Co-authored-by: Manuel de la Pena <mandel@microsoft.com> Co-authored-by: Premek Vysoky <prvysoky@microsoft.com> Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-03-10 15:12:33 +03:00
<Link>SdkVersions.cs</Link>
</Compile>
[Tests] Add a new iOS app to run the xunit and nunit tests (#4914) Mono know provides a set of testing assemblies that contain the tests to be ran in each of the supported platforms. This commit adds the following: 1. Two different runners that can be used to execute NUnit and xUnit tests. 2. The necessary glue to get xharness to run the new tests and report the results. 3. A new test that will ensure that if mono adds new tests, xharness will report failures if the tests are not run or not ignored.
2018-11-16 21:31:40 +03:00
</ItemGroup>
[xharness] Move javascript and css to external files. (#5378) This makes editing them a bit simpler. There are no functional changes.
2019-01-11 17:25:36 +03:00
<ItemGroup>
<Content Include="xharness.js">
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</Content>
<Content Include="xharness.css">
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</Content>
</ItemGroup>
[Harness] Move code to a shared library (#8234) - Code that will later be moved to the `dotnet/xharness` repo is first moved to an isolated project before it will be extracted to the new repo and NuGetified - New project for the shared code and new test project for tests accompanying the moved code are created - Only Factories are left behind that are used only by XHarness
2020-04-01 20:32:21 +03:00
<ItemGroup>
<ProjectReference Include="Microsoft.DotNet.XHarness.iOS.Shared\Microsoft.DotNet.XHarness.iOS.Shared.csproj">
<Project>{5be5cabf-8d6c-4f35-9e5b-505b4c40b2ac}</Project>
<Name>Microsoft.DotNet.XHarness.iOS.Shared</Name>
</ProjectReference>
</ItemGroup>
[Harness] Move TestImporter into the shared library (#8283)
2020-04-04 01:28:49 +03:00
<ItemGroup />
[tests] Import
2016-05-26 16:06:52 +03:00
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
[Harness] Split out classes from Jenkins.cs to separate files (#8046) Co-authored-by: Premek Vysoky <prvysoky@microsoft.com>
2020-03-06 14:00:34 +03:00
</Project>