Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

9,934

Downloads of v 2.0.0-alpha5:

92

Last Update:

14 May 2022

Package Maintainer(s):

Software Author(s):

  • Charlie Poole

Tags:

testcentric nunit gui runner test centric testing tdd

TestCentric Runner for NUnit

This is a prerelease version of TestCentric Runner for NUnit.

  • 1
  • 2
  • 3

2.0.0-alpha5 | Updated: 14 May 2022

Downloads:

9,934

Downloads of v 2.0.0-alpha5:

92

Maintainer(s):

Software Author(s):

  • Charlie Poole

TestCentric Runner for NUnit 2.0.0-alpha5

This is a prerelease version of TestCentric Runner for NUnit.

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Charlie Poole. The inclusion of Charlie Poole trademark(s), if any, upon this webpage is solely to identify Charlie Poole goods or services and not for commercial purposes.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install TestCentric Runner for NUnit, run the following command from the command line or from PowerShell:

>

To upgrade TestCentric Runner for NUnit, run the following command from the command line or from PowerShell:

>

To uninstall TestCentric Runner for NUnit, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade testcentric-gui -y --source="'INTERNAL REPO URL'" --version="'2.0.0-alpha5'" --prerelease [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade testcentric-gui -y --source="'INTERNAL REPO URL'" --version="'2.0.0-alpha5'" --prerelease
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install testcentric-gui
  win_chocolatey:
    name: testcentric-gui
    version: '2.0.0-alpha5'
    source: INTERNAL REPO URL
    state: present
    allow_prerelease: yes

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'testcentric-gui' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.0.0-alpha5'
  options  '--prerelease'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller testcentric-gui
{
    Name        = "testcentric-gui"
    Version     = "2.0.0-alpha5"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'testcentric-gui':
  ensure          => '2.0.0-alpha5',
  install_options => ['--prerelease'],
  provider        => 'chocolatey',
  source          => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 14 May 2022.

Description

The TestCentric Runner for NUnit (TestCentric) is a GUI runner aimed at eventually supporting a range of .NET testing frameworks. In the 1.x release series, we are concentrating on support of NUnit tests. The user interface is based on the layout and feature set of the of the original NUnit GUI, with the internals modified so as to run NUnit 3 tests.

This package includes the both the standard TestCentric GUI runner (testcentric.exe) and an experiental runner (tc-next.exe) which is available for... wait for it... experimentation! The package incorporates the TestCentric test engine, a modified version of the NUnit engine.

Features

Most features of the NUnit V2 Gui runner are supported. See CHANGES.txt for more detailed information.

NUnit engine extensions are supported but no extensions are bundled with the GUI itself. They must be installed separately using chocolatey. In particular, to run NUnit V2 tests, you should install the NUnit V2 Framework Driver Extension.

Warning: When using the GUI chocolatey package, only chocolatey-packaged extensions will be availble. This is by design.

Prerequisites

TestCentric requires .NET 4.5 or later in order to function, although your tests may run in a separate process under other framework versions.

Projects with tests to be run under TestCentric must already have some version of the NUnit framework installed separtely.


tools\agents\net40\nunit.engine.api.dll
md5: 7E15F91EF58AC443F7170E2AFAE03087 | sha1: 9A2AE27FD58B019CF9104289074B8571FCE81270 | sha256: 2191097317CEAF4E4D62AEF9B3A73965B2640FA810C1D08374A14CA2EF35D2B6 | sha512: 0DF7281D2FC8D06CAA7650385B342CC08BE2238ED1318ED9929302309E972F2E0FC19D063DD3554ACD64C865F5EA2E97DB3A29B9309833B50FA748C8F23E27E2
tools\agents\net40\testcentric-agent-x86.exe
md5: E729BB718B2C3424832BDA7539C87844 | sha1: 66C0E913F9F66D8A44B9A6C350B4007F63FF4BE6 | sha256: 5897F517B5990653B5C0D28B456C5A75597D52C68BFBCF5BA6584D927EBD998E | sha512: 8EC781EC9D5F58B227CC5CADADBF83B38058D036C300230B8AA9CFC0B7811666B4520B732F05533A4AF698C0D3EF28C37D9C6906F431149B5439A212C4CFAC4B
tools\agents\net40\testcentric-agent-x86.exe.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!--
   Nunit-agent only runs under .NET 2.0 or higher. 
   The setting    useLegacyV2RuntimeActivationPolicy only applies 
   under .NET 4.0 and permits use of mixed mode assemblies, 
   which would otherwise not load correctly. 
  -->
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <!--
     Nunit-agent is normally run by the console or gui
     runners and not independently. In normal usage, 
     the runner specifies which runtime should be used.
     
     Do NOT add any supportedRuntime elements here, 
     since they may prevent the runner from controlling 
     the runtime that is used!
    -->
  </startup>

  <runtime>
    <!-- Ensure that test exceptions don't crash NUnit -->
    <legacyUnhandledExceptionPolicy enabled="1" />

    <!--
     Since legacyUnhandledExceptionPolicy keeps the console from being killed even though an NUnit framework
     test worker thread is killed, this is needed to prevent a hang. NUnit framework can only handle these
     exceptions when this config element is present. (Or if future versions of NUnit framework drop support
     for partial trust which would enable it to use [HandleProcessCorruptedStateExceptions].)
    -->
    <legacyCorruptedStateExceptionsPolicy enabled="true" />

    <!-- Run partial trust V2 assemblies in full trust under .NET 4.0 -->
    <loadFromRemoteSources enabled="true" />

    <!-- Enable reading source information from Portable and Embedded PDBs when running applications -->
    <!-- built against previous .NET Framework versions on .NET Framework 4.7.2 -->
    <AppContextSwitchOverrides value="Switch.System.Diagnostics.IgnorePortablePDBsInStackTraces=false" />
  </runtime>
  
</configuration>
tools\agents\net40\testcentric-agent.choco.addins
 
tools\agents\net40\testcentric-agent.exe
md5: 31F4FE68E607C6C42D58745FB8CCE64E | sha1: 4B912A8461BCAAA577B0359B94AAE863C5CE63F3 | sha256: C4D48D1A26F4DA26B623F2D7911E13A4D5FAC0A412729933AC6E010C7F25CA04 | sha512: 4EF74A15B38FC5F84A2843849E974A5F7CD453ECA467FF5DC5845BD4B1DC6D4BB9DE7D78C77A029D75C273D411DC0708BFD6CC5F67ECAFB0C8688762C3C8565F
tools\agents\net40\testcentric-agent.exe.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!--
   Nunit-agent only runs under .NET 2.0 or higher. 
   The setting    useLegacyV2RuntimeActivationPolicy only applies 
   under .NET 4.0 and permits use of mixed mode assemblies, 
   which would otherwise not load correctly. 
  -->
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <!--
     Nunit-agent is normally run by the console or gui
     runners and not independently. In normal usage, 
     the runner specifies which runtime should be used.
     
     Do NOT add any supportedRuntime elements here, 
     since they may prevent the runner from controlling 
     the runtime that is used!
    -->
  </startup>

  <runtime>
    <!-- Ensure that test exceptions don't crash NUnit -->
    <legacyUnhandledExceptionPolicy enabled="1" />

    <!--
     Since legacyUnhandledExceptionPolicy keeps the console from being killed even though an NUnit framework
     test worker thread is killed, this is needed to prevent a hang. NUnit framework can only handle these
     exceptions when this config element is present. (Or if future versions of NUnit framework drop support
     for partial trust which would enable it to use [HandleProcessCorruptedStateExceptions].)
    -->
    <legacyCorruptedStateExceptionsPolicy enabled="true" />

    <!-- Run partial trust V2 assemblies in full trust under .NET 4.0 -->
    <loadFromRemoteSources enabled="true" />

    <!-- Enable reading source information from Portable and Embedded PDBs when running applications -->
    <!-- built against previous .NET Framework versions on .NET Framework 4.7.2 -->
    <AppContextSwitchOverrides value="Switch.System.Diagnostics.IgnorePortablePDBsInStackTraces=false" />
  </runtime>
  
</configuration>
tools\agents\net40\testcentric.engine.core.dll
md5: ACDACC4957D25553EB672F903576ED3D | sha1: 3672B8A00EB398BF516FF949BD9CBAFB89A71A5B | sha256: 28ABA151B17CFFD3840EF35A65C42C2BC2A983BC5D3C42476F33BC3740A13D8C | sha512: 435CBFC245F674DCD55C001363E278643AE4D45FA65D2D6704E42973BC37FA6C82B8EB43677A90BF3E0E1F32266860C0C1859125F0AEC5E0521D7EBE027633F9
tools\agents\net40\testcentric.engine.metadata.dll
tools\agents\net5.0\nunit.engine.api.dll
md5: C554CD4116A84EBD71A0A607923619A7 | sha1: C044280AAD049ED3B23C69C537CAD64E61A21AA8 | sha256: 1FCB9EAFB4B00A5F53C627A3638D78C7B2CC0E7B5CF2DA1DD3B79C3BC5E29C97 | sha512: F62AD4EF448BF7BA06B06FD63F0D37A6D495983FAF7FBBD78B64ED2A8A13F0534B5B4475956D1538DD0651B961348DC4CFD69E4A7EDDB4F80B6FCE8EF6E10490
tools\agents\net5.0\testcentric-agent.choco.addins
 
tools\agents\net5.0\testcentric-agent.deps.json
{
  "runtimeTarget": {
    "name": ".NETCoreApp,Version=v5.0",
    "signature": ""
  },
  "compilationOptions": {},
  "targets": {
    ".NETCoreApp,Version=v5.0": {
      "testcentric-agent/2.0.0-dev00014": {
        "dependencies": {
          "testcentric.engine.core": "2.0.0-IDE"
        },
        "runtime": {
          "testcentric-agent.dll": {}
        }
      },
      "NUnit.Engine.Api/4.0.0-dev-05363": {
        "runtime": {
          "lib/netstandard2.0/nunit.engine.api.dll": {
            "assemblyVersion": "3.0.0.0",
            "fileVersion": "4.0.0.0"
          }
        }
      },
      "TestCentric.Metadata/1.7.1": {
        "runtime": {
          "lib/netstandard2.0/testcentric.engine.metadata.dll": {
            "assemblyVersion": "1.7.1.0",
            "fileVersion": "1.7.1.0"
          }
        }
      },
      "testcentric.engine.core/2.0.0-IDE": {
        "dependencies": {
          "NUnit.Engine.Api": "4.0.0-dev-05363",
          "TestCentric.Metadata": "1.7.1"
        },
        "runtime": {
          "testcentric.engine.core.dll": {}
        }
      }
    }
  },
  "libraries": {
    "testcentric-agent/2.0.0-dev00014": {
      "type": "project",
      "serviceable": false,
      "sha512": ""
    },
    "NUnit.Engine.Api/4.0.0-dev-05363": {
      "type": "package",
      "serviceable": true,
      "sha512": "sha512-1Lqyf+pmK4OsJ+5jMCENWbF+rMfmhMa3fG7kmV4NRBneqS1M1ahuz2hbmTGuU1wFpnx/FUeuPJkHk2ROYwP3UQ==",
      "path": "nunit.engine.api/4.0.0-dev-05363",
      "hashPath": "nunit.engine.api.4.0.0-dev-05363.nupkg.sha512"
    },
    "TestCentric.Metadata/1.7.1": {
      "type": "package",
      "serviceable": true,
      "sha512": "sha512-QjdwsUJXJbGmFKNiTZbWeRpwhqRcEAtgb+dwR4YVK8xUBBEfXfrFV074f1DBtnrOfAIT+LnZCeVVeg/fYUlAEA==",
      "path": "testcentric.metadata/1.7.1",
      "hashPath": "testcentric.metadata.1.7.1.nupkg.sha512"
    },
    "testcentric.engine.core/2.0.0-IDE": {
      "type": "project",
      "serviceable": false,
      "sha512": ""
    }
  }
}
tools\agents\net5.0\testcentric-agent.dll
md5: 6A4FA327D621CD93273F1CE28F3EF8C0 | sha1: AD601BF7A7F14C490850EA3215D446BACCE9B78D | sha256: 1B36A845E99BA3CF4B9524CBB3DF92AFA26F375BA3C30D03E30A60C5738AA76E | sha512: 6510CC4D52E179FA6AD998D025239A808F7648044423268DA4E9B180EAF6CB644769054800BD2262F425DFC6160F9CC985BBA3C71187A366039CECA646A37DEF
tools\agents\net5.0\testcentric-agent.dll.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!--
   Nunit-agent only runs under .NET 2.0 or higher. 
   The setting    useLegacyV2RuntimeActivationPolicy only applies 
   under .NET 4.0 and permits use of mixed mode assemblies, 
   which would otherwise not load correctly. 
  -->
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <!--
     Nunit-agent is normally run by the console or gui
     runners and not independently. In normal usage, 
     the runner specifies which runtime should be used.
     
     Do NOT add any supportedRuntime elements here, 
     since they may prevent the runner from controlling 
     the runtime that is used!
    -->
  </startup>

  <runtime>
    <!-- Ensure that test exceptions don't crash NUnit -->
    <legacyUnhandledExceptionPolicy enabled="1" />

    <!--
     Since legacyUnhandledExceptionPolicy keeps the console from being killed even though an NUnit framework
     test worker thread is killed, this is needed to prevent a hang. NUnit framework can only handle these
     exceptions when this config element is present. (Or if future versions of NUnit framework drop support
     for partial trust which would enable it to use [HandleProcessCorruptedStateExceptions].)
    -->
    <legacyCorruptedStateExceptionsPolicy enabled="true" />

    <!-- Run partial trust V2 assemblies in full trust under .NET 4.0 -->
    <loadFromRemoteSources enabled="true" />

    <!-- Enable reading source information from Portable and Embedded PDBs when running applications -->
    <!-- built against previous .NET Framework versions on .NET Framework 4.7.2 -->
    <AppContextSwitchOverrides value="Switch.System.Diagnostics.IgnorePortablePDBsInStackTraces=false" />
  </runtime>
  
</configuration>
tools\agents\net5.0\testcentric-agent.runtimeconfig.dev.json
{
  "runtimeOptions": {
    "additionalProbingPaths": [
      "C:\\Users\\appveyor\\.dotnet\\store\\|arch|\\|tfm|",
      "C:\\Users\\appveyor\\.nuget\\packages",
      "C:\\Program Files (x86)\\Microsoft Visual Studio\\Shared\\NuGetPackages",
      "C:\\Program Files (x86)\\Microsoft\\Xamarin\\NuGet"
    ]
  }
}
tools\agents\net5.0\testcentric-agent.runtimeconfig.json
{
  "runtimeOptions": {
    "tfm": "net5.0",
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "5.0.0"
    }
  }
}
tools\agents\net5.0\testcentric.engine.core.dll
md5: 7C3800E6AEE10D8219E99F45DB17A25F | sha1: 2D2E600F776B034E926FFCB385AD2FE851F37135 | sha256: 34963938D1286D843B8ACFEDFBA84DDB2CB15B6B527DB03C7F8859021DE3AFB8 | sha512: BFE5605DDC907BCAE76B539F00D73A5F843EF4068A313E95B6CBB4E0A3205365C7D92A9A6D1D310144B26DAFE48CCA3B3278AA51BDC3B99EB9B53B35AAC44FD5
tools\agents\net5.0\testcentric.engine.metadata.dll
tools\agents\netcoreapp3.1\nunit.engine.api.dll
md5: C554CD4116A84EBD71A0A607923619A7 | sha1: C044280AAD049ED3B23C69C537CAD64E61A21AA8 | sha256: 1FCB9EAFB4B00A5F53C627A3638D78C7B2CC0E7B5CF2DA1DD3B79C3BC5E29C97 | sha512: F62AD4EF448BF7BA06B06FD63F0D37A6D495983FAF7FBBD78B64ED2A8A13F0534B5B4475956D1538DD0651B961348DC4CFD69E4A7EDDB4F80B6FCE8EF6E10490
tools\agents\netcoreapp3.1\testcentric-agent.choco.addins
 
tools\agents\netcoreapp3.1\testcentric-agent.deps.json
{
  "runtimeTarget": {
    "name": ".NETCoreApp,Version=v3.1",
    "signature": ""
  },
  "compilationOptions": {},
  "targets": {
    ".NETCoreApp,Version=v3.1": {
      "testcentric-agent/2.0.0-dev00014": {
        "dependencies": {
          "testcentric.engine.core": "2.0.0-IDE"
        },
        "runtime": {
          "testcentric-agent.dll": {}
        }
      },
      "NUnit.Engine.Api/4.0.0-dev-05363": {
        "runtime": {
          "lib/netstandard2.0/nunit.engine.api.dll": {
            "assemblyVersion": "3.0.0.0",
            "fileVersion": "4.0.0.0"
          }
        }
      },
      "TestCentric.Metadata/1.7.1": {
        "runtime": {
          "lib/netstandard2.0/testcentric.engine.metadata.dll": {
            "assemblyVersion": "1.7.1.0",
            "fileVersion": "1.7.1.0"
          }
        }
      },
      "testcentric.engine.core/2.0.0-IDE": {
        "dependencies": {
          "NUnit.Engine.Api": "4.0.0-dev-05363",
          "TestCentric.Metadata": "1.7.1"
        },
        "runtime": {
          "testcentric.engine.core.dll": {}
        }
      }
    }
  },
  "libraries": {
    "testcentric-agent/2.0.0-dev00014": {
      "type": "project",
      "serviceable": false,
      "sha512": ""
    },
    "NUnit.Engine.Api/4.0.0-dev-05363": {
      "type": "package",
      "serviceable": true,
      "sha512": "sha512-1Lqyf+pmK4OsJ+5jMCENWbF+rMfmhMa3fG7kmV4NRBneqS1M1ahuz2hbmTGuU1wFpnx/FUeuPJkHk2ROYwP3UQ==",
      "path": "nunit.engine.api/4.0.0-dev-05363",
      "hashPath": "nunit.engine.api.4.0.0-dev-05363.nupkg.sha512"
    },
    "TestCentric.Metadata/1.7.1": {
      "type": "package",
      "serviceable": true,
      "sha512": "sha512-QjdwsUJXJbGmFKNiTZbWeRpwhqRcEAtgb+dwR4YVK8xUBBEfXfrFV074f1DBtnrOfAIT+LnZCeVVeg/fYUlAEA==",
      "path": "testcentric.metadata/1.7.1",
      "hashPath": "testcentric.metadata.1.7.1.nupkg.sha512"
    },
    "testcentric.engine.core/2.0.0-IDE": {
      "type": "project",
      "serviceable": false,
      "sha512": ""
    }
  }
}
tools\agents\netcoreapp3.1\testcentric-agent.dll
md5: 190B736794F956B15D94779B193A3871 | sha1: 34C5A691ACDBDC5DD6EEDC53730A80B6AEA2345F | sha256: 403AECC48AB8416EB497E0C231C1B26E4D6B41DC14953F779AF52F5B5C7D1C76 | sha512: 6454D57115570C1AE58D41A73BE5B2AF2A85800DFCD505B536EAD82F7107F3C386473A7B6705D9472486A5EE167C42B5F576B4AA8199BFE0BDA9DB3A47696BD5
tools\agents\netcoreapp3.1\testcentric-agent.dll.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!--
   Nunit-agent only runs under .NET 2.0 or higher. 
   The setting    useLegacyV2RuntimeActivationPolicy only applies 
   under .NET 4.0 and permits use of mixed mode assemblies, 
   which would otherwise not load correctly. 
  -->
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <!--
     Nunit-agent is normally run by the console or gui
     runners and not independently. In normal usage, 
     the runner specifies which runtime should be used.
     
     Do NOT add any supportedRuntime elements here, 
     since they may prevent the runner from controlling 
     the runtime that is used!
    -->
  </startup>

  <runtime>
    <!-- Ensure that test exceptions don't crash NUnit -->
    <legacyUnhandledExceptionPolicy enabled="1" />

    <!--
     Since legacyUnhandledExceptionPolicy keeps the console from being killed even though an NUnit framework
     test worker thread is killed, this is needed to prevent a hang. NUnit framework can only handle these
     exceptions when this config element is present. (Or if future versions of NUnit framework drop support
     for partial trust which would enable it to use [HandleProcessCorruptedStateExceptions].)
    -->
    <legacyCorruptedStateExceptionsPolicy enabled="true" />

    <!-- Run partial trust V2 assemblies in full trust under .NET 4.0 -->
    <loadFromRemoteSources enabled="true" />

    <!-- Enable reading source information from Portable and Embedded PDBs when running applications -->
    <!-- built against previous .NET Framework versions on .NET Framework 4.7.2 -->
    <AppContextSwitchOverrides value="Switch.System.Diagnostics.IgnorePortablePDBsInStackTraces=false" />
  </runtime>
  
</configuration>
tools\agents\netcoreapp3.1\testcentric-agent.runtimeconfig.dev.json
{
  "runtimeOptions": {
    "additionalProbingPaths": [
      "C:\\Users\\appveyor\\.dotnet\\store\\|arch|\\|tfm|",
      "C:\\Users\\appveyor\\.nuget\\packages",
      "C:\\Program Files (x86)\\Microsoft Visual Studio\\Shared\\NuGetPackages",
      "C:\\Program Files (x86)\\Microsoft\\Xamarin\\NuGet"
    ]
  }
}
tools\agents\netcoreapp3.1\testcentric-agent.runtimeconfig.json
{
  "runtimeOptions": {
    "tfm": "netcoreapp3.1",
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "3.1.0"
    }
  }
}
tools\agents\netcoreapp3.1\testcentric.engine.core.dll
md5: 7C3800E6AEE10D8219E99F45DB17A25F | sha1: 2D2E600F776B034E926FFCB385AD2FE851F37135 | sha256: 34963938D1286D843B8ACFEDFBA84DDB2CB15B6B527DB03C7F8859021DE3AFB8 | sha512: BFE5605DDC907BCAE76B539F00D73A5F843EF4068A313E95B6CBB4E0A3205365C7D92A9A6D1D310144B26DAFE48CCA3B3278AA51BDC3B99EB9B53B35AAC44FD5
tools\agents\netcoreapp3.1\testcentric.engine.metadata.dll
tools\CHANGES.txt
TestCentric Runner for NUnit 2.0.0-alpha3 - October 2, 2021

This release incorporates a critical fix to a bug, which caused the program to crash
when run on a machine with .NET 6.0 installed.

Bug

 * 818 TestCentric Runner for NUnit 2.0.0-alpha3 - September 30, 2021

TestCentric Runner for NUnit 2.0.0-alpha3 - September 30, 2021

Breaking Changes

 * 808 Switch to the dev-40 build of the NUnit Engine API
 * 809 Stop building for .NET Standard 1.6 and .NET Core 1.1

Feature

 * 804 Remove references to the engine from the GUI proper

Enhancement

 * 705 Modify Arguments to Agent Process

Build

 * 805 Stop use of Image Directory where not needed
 * 812 Use VS Project properties to generate the assemblyinfo files
 * 813 Upgrade to the latest Cake version

TestCentric Runner for NUnit 2.0.0-alpha2 - August 15, 2021

Features

 * 230 Save and restore Visual state
 * 609 Allow selecting normal versus forced stop
 * 732 Merge features of the experimental GUI into the 2.0 standard GUI
 * 735 Remove Categories Tab from left-hand GUI panel
 * 740 Remove right-hand panel Run and Cancel buttons
 * 741 Move Progress Bar to left-hand panel
 * 742 Remove Not Run tab
 * 744 Port PropertyView from experimental GUI
 * 745 Port XmlView from experimental GUI
 * 757 Remove "Run Failed" from split button choices in menu bar
 * 758 Make "Stop Run" a separate button on menu bar"
 * 761 Make Menu Bar full width of main window
 * 762 Variable positioning of progress bar
 * 780 Restore TestPropertiesDialog for use with the mini-GUI

Enhancements

 * 737 Remove checkbox-related buttons from below tree display
 * 755 Display last run summary on demand
 * 786 Show package settings at top of PropertiesDialog and only show for tests representing packages
 * 789 Display package settings in TestPropertiesView
 * 790 Hide result box in TestPropertiesDialog when there is no result
 * 794 Adjust PropertiesDialog Layout to be closer to that of TestPropertiesView
 * 798 Improve Test Run Report Presentation

Bugs

 * 767 GroupBy dropdown has no effect when changing
 * 769 Groupings, which do not apply to the current display format, should be disabled
 * 770 Need icon for display format button
 * 778 Visibility of StatusBar is not saved
 * 783 NRE when File Menu pops up without an open project
 * 788 Location of form should be saved before changing GUI layout
 * 791 TestPropertiesDialog does not update after test run

Build

 * 733 Remove unneeded conditionals from the engine
 * 753 Move "common" gui components to the  Gui project

TestCentric Runner for NUnit 2.0.0-alpha1 - June 30, 2021

The 2.0.0 release is the first major upgrade of the TestCentric Gui.
It includes a number of breaking changes as well as new features.

Gui Features

 * The ProcessModel and DomainUsage menus have been eliminated.

 * A new Select Agents menu allows the user to choose a non-default
   agent when more than one is available for a particular assembly.

Engine Features

 * In-process execution of tests and the ProcessModel package setting
   are no longer supported. Each test assembly is now run in its own
   separate process.

 * The DomainUsage package setting is no longer supported. The runner
   itself decides whether an AppDomain should  be used when running
   on a particular platform.

 * All test execution is now performed by agents, which are usually
   separate local processes. Agent selection may be automatic or
   user-specified using a package setting.
   
 * It is now possible to create "pluggable agents" by use of a new
   engine extension point. Currently, this capability is limited to
   local process agents, but it is intended to be extended to other
   agent types in the future.

 * Services are now initialized when they are first accessed through
   the service context rather than at startup.

 * There is no longer a .NET Standard build of the engine.

 * The metadata assembly is now a separate package, which is used
   by the engine.

 * X86 builds of .Net Core agents are no longer provided, since
   they are not needed.

Breaking Changes

 * 444 Eliminate in process execution
 * 656 Pluggable Agents
 * 657 Eliminate DomainUsage option
 * 664 Replace AppDomain and Process with "Agent" from user perspective
 * 665 Eliminate ProcessModel setting

Features

 * 678 Create package for use by pluggable agents
 * 684 Make metadata assembly a fully independent package
 * 689 Remove DomainManager as a service
 * 691 Remove InProcessTestRunnerFactory
 * 693 Stop building engine for .NET Standard
 * 694 Remove x86 build of agent for .NET Core
 * 697 Agent Redesign

Enhancements

 * 666 Issue an error message when user provides an obsolete project setting. Ignore in project files.
 * 677 Update AboutBox for 2.0 release
 * 715 Make dependencies of one service on another explicit.

Bugs

 * 707 ResultHelper.Aggregate doesn't count warnings
 * 719 Crashing Testcentric on trying to change Process Model to X86

Build

 * 682 Build script should check files for valid headers
 * 699 Create separate test assembly for nunit.agent.core
 * 700 Use the GUI to run its own tests
 * 716 Provide test doubles for all services needed for testing.
 * 725 Upgrade NUnit framework to 3.12
 * 729 Allow creation of draft and production GitHub releases for pre-release versions

TestCentric Runner for NUnit 1.6.2 - March 24, 2021

This additional release of TestCentric 1.6 was necessitated by the identification
of a critical bug.

#### Bug

* Show CheckBoxes does not work

TestCentric Runner for NUnit 1.6.1 - January 17, 2021

The main change in this release is that the `InProcess` option is disabled
when the loaded tests cannot all run in the Gui process under the .NET
Framework 4.x and would otherwise cause an error.

This is intended to be the last release in the TestCentric 1.x series. The
next release, version 2.0, will contain breaking changes including the
elimination of the `InProcess` option as well as of all `DomainUsage` options.
In future, the use of AppDomains in platforms that support them will be treated
as an implementation detail outside the control of the user.

#### Enhancement

* 661 InProcess menu item should be disabled if any .net core tests are loaded.

#### Refactor

* 658 Restructure or rewrite runtime framework detection code

TestCentric Runner for NUnit 1.6.0 - January 10, 2021

The main feature of this release is the addition of an agent for running tests under .NET 5.0.
Since the runner itself targets the .NET Framework, this feature is only available when tests
are run out of process. By default, tests targeting .NET 5.0 will run under that agent, provided
that .NET 5.0 is installed. The File menu also allows running tests built for earlier versions
of .NET Core under .NET 5.0.

Issues Resolved

* 593 GetExecutingAssembly() returns the path of appdata folder instead of actual location
* 640 Review tests of Dialogs
* 648 misaligned Force Stop button
* 651 Add a .NET 5.0 agent to the build
* 653 Export Draft Release for use in CHANGES file and on website

TestCentric Runner for NUnit 1.5.3 - December 23, 2020

This release fixes a critical issue in 1.5.2

Issues Resolved

* 631 Website not being rebuilt for production release
* 632 Move website for gui into testcentric.github.io
* 637 Document process for creating a release
* 638 Testcentric 1.5.2: About testcentric throws an unhandled exception
* 641 Update AboutBox text and ensure it all fits
* 642 Dashes rather than separators in menus

TestCentric Runner for NUnit 1.5.2 - December 16, 2020

Issues Resolved

* 626  Tailor content of Release Note created by release build

TestCentric Runner for NUnit 1.5.1 - December 14, 2020

Issues Resolved

* 324 Convert to use new VS project format
* 603 Add Getting Started section to the documentation
* 616 Improvements to the Release Process
* 617 Migrate "master" branch to "main"

TestCentric Runner for NUnit 1.5.0 - December 8, 2020

This release includes one major new feature. The Stop button now triggers a non-forced
stop, running all teardowns. It then gives the user the option of a forced stop in case
the run does not terminate. In addition, it incorporates major build improvements, which
will make it easier to do more frequent releases in the future.

Feature

* 374 Implement two stage Stop, first trying non-forced and then letting user select forced stop.

Bugs

* 613 Version 1.4.1 release zip file is missing
* 607 Clear All  and Check Failed checkboxes do not work correctly
* 605 Results not being cleared in tree for each new run

Build

* 612 Automate final release process
* 611 Convert projects to new format
* 602 Add CodeQL analysis to the build
* 599 Automatically update website

TestCentric Runner for NUnit 1.4.1 - September 3, 2020

This is primarily a bug fix release, the exception being the use of our own metadata
assembly which is being published as a separate nuget package for use by others.

Engine

 * The Mono.Cecil package is no longer a dependency. A new assembly incorporates Mono
   source code and provides the specific introspection features needed by the engine.

Issues Resolved

 * 577 Carry CurrentDirectory over to agent processes
 * 579 1.4.0 Unhandled exception
 * 585 Metadata Assembly
 * 595 InvalidCastException, "Properties" context menu entry

TestCentric Runner for NUnit 1.4.0 - April 30, 2020

This release introduces execution of .NET Core tests along with .NET Framework and 
adds several other smaller features.

GUI

 * The NUnit Project Editor may now be launched from the GUI. A Settings page
   has been added to allow specifying an alternate editor.

 * The Runtime menu allows overriding the version of .NET Framework or .NET 
   Core to be used, provided that the version used is compatible with all
   loaded assemblies.

 * The project configuration (e.g. Debug or Release) may be set individually
   for each loaded project, through the GUI test tree context menu.

 * Package settings are now displayed in the Test Properties Dialog for tests
   that correspond to a package.

Engine

 * Tests targeting .NET Core 1.1 through 3.1 may now be executed in the GUI.
   The GUI can simulataneously load .NET Framework and .NET Core test assemblies.

 * .NET Core tests communicate with the GUI using TCP. .NET Framework tests
   continue to use remoting.

Issues Resolved

 * 218 Support editing projects through the project editor
 * 453 Execute tests under .NET Core
 * 478 Review and update engine creation logic
 * 484 Recognize .NET Core as available and display in GUI runtime menu.
 * 508 Create agent process executable for .NET Core 2.1.
 * 512 Create transport protocol for use with .NET Core agents.
 * 565 Create agent process executable for .NET Core 3.1
 * 568 Run .NET Core 1.x tests under 2.1 or higher agent
 * 570 Support project configs
 * 572 Display Package Settings in TestPropertiesDialog

TestCentric Runner for NUnit 1.3.3 - April 17, 2020

This release corrects a critical issue whereby engine extensions were no longer
being recognized by the GUI. Additional package testing, including use of
extensions, has been added to prevent regressions.

Issues Resolved

 * 551 Automate Release Process
 * 558 ReportPortal addins to TestCentric
 * 560 Support the NUnit engine API
 * 562 Expanded package testing prior to release
 
TestCentric Runner for NUnit 1.3.2 - March 15, 2020

This release corrects a new bug found in the 1.3.0 release and makes a
number of improvements in the automation of the release process.

Issues Resolved

 * 428 Update assemblyinfo automatically
 * 525 Create a nuget organization for TestCentric
 * 534 Automate packaging and deployment
 * 540 Support for unattended execution of the GUI
 * 542 FIXED: Default process model for 32 bit v1.3.1

TestCentric Runner for NUnit 1.3.1 - March 6, 2020

This release corrects a critical problem in the 1.3.0 release. None of the
1.3.0 packages included agents for use under .NET 4.0 and higher. This
release adds those agents.

Issues Resolved

 * 535 FIXED: Cannot load test assembly after 1.3 update
 * 536 Restructuring the build.cake script
 * 537 FIXED: Missing files in Release 1.3.0
 * 538 Add package checking tasks to build

TestCentric Runner for NUnit 1.3.0 - February 23, 2020

General

 * A NuGet package is now available on nuget.org. While we continue to
   recommend use of the chocolatey.org package for most developers, because
   it provides a central installation point for use with all projects, a
   number of users requested a nuget package as well.

   NOTE: Whichever installation package you use, you should install any
   needed extensions using the same package source.

GUI

 * The runtime selection menu is now disabled when tests are being run in
   process, since no other runtime is available within the GUI process.

Engine

 * The UserSettings service is no longer part of the engine but is handled
   directly in the GUI. This is not considered a breaking change, since
   the engine is not yet released separately from the GUI.

 * A new PackageSettings service has been added to the engine. Its job
   is to analyze all packages, examine assemblies and set default
   parameters for executing them.

 * A pair of agents are provided for .NET 4.0 in addition to the existing
   .NET 2.0 agents. In addition, the engine is now built for both runtimes
   and agents use the appropriate version. The GUI itself uses the 4.0 engine.

Issues Resolved

 * 457 Remove UserSettings from the engine
 * 466 Update Copyright headers in all files
 * 475 Engine Tests will only run in process under GUI
 * 476 Eliminate use of Mono.Cecil from engine core assembly
 * 479 Refactor RuntimeFramework to eliminate unneeded selection options
 * 480 Determine versions of .NET Core we want to support.
 * 483 Disable Runtime menu when running in process
 * 487 Determine supported platforms for the engine.
 * 488 Integrate engine build output
 * 489 Run tests for .NET Core
 * 499 Engine Tests don't run under .NET Core 2.1
 * 502 Create new Service to manage PackageSettings
 * 505 Reorganize output to allow agents for various runtimes and both 32-bit and 64-bit execution
 * 513 Modify logic of TestAgency to initiate correct agents
 * 514 Upgrade engine to target .NET 4.0
 * 517 Net40 engine.core build
 * 518 Create agent process executable for .NET Framework 4.0 and higher
 * 522 Update nuget and chocolatey packages
 * 523 Create a nuget package for the GUI
 * 528 Chocolatey package should use TestCentric icon
 * 526 Update nuget package
 * 531 Create tasks in build script for publishing packages

TestCentric Runner for NUnit 1.2.0 - December 17, 2019

This release is primarily marked by the elimination of our 
dependency on the NUnit Engine in preparation for moving
forward with features that require engine changes.

GUI

 * Inprocess test execution has been deprecated

Experimental GUI

 * The GUI font may be changed from the View menu

 * One or more files may be added to those open

 * Rerun on Change has been implemented

Test Model
 
Engine

 * We now use the TestCentric Engine, Version 0.1, replacing the NUnit Engine. 
 The new engine is based on the NUnit 3.11 engine, with modifications.

 * Engine recognizes and runs assemblies that target .NET Framework 4.6 and up.

 * Engine now recognizes .NET Core assemblies and gives an error message
 if the user attempts to open one.

 * The RecentFilesService is no longer available.

Issues Resolved

 * 215 Experimental GUI: Allow setting the gui font
 * 217 Experimental GUI: Add files to those already open
 * 233 Experimental GUI: Rerun on Change
 * 426 Switch to use of separate TestCentric Engine build
 * 445 Better error message when attempting to load .NET Core assemblies
 * 447 FIXED: Engine will not recognize .NET Framework versions beyond 4.5
 * 449 FIXED: GUI window doesn't retain size between runs
 * 454 Deprecate in-process execution
 * 455 Remove RecentFilesService from engine
 * 456 Rename engine to testcentric engine
 * 461 Convert all projects to use Package References
 * 470 Remove deprecated "Single" option for ProcessModel
 * 473 Establish Initial Version for TestCentric engine

TestCentric Runner for NUnit 1.1.0 - November 9, 2019

General

This release includes new features beyond the 1.0 release, together with some bug fixes.

Features
 * The configuration to be loaded may be specified in the GUI.
 * A new dialog allows setting parameters for the test run.
 * Test Results may be saved in any format for which an extension has been installed.
 * Additional test label options are supported.
 * The GUI uses a custom build of the latest version of the NUnit engine.
 * Includes version 0.16 of the experimental GUI.

Issues Resolved

 *   4 Save test results in alternative formats
 *  77 Setting up test parameters from gui
 * 193 Experimental GUI: Passing parameters from GUI to Tests
 * 216 Experimental GUI: Set project configuration to use
 * 275 Add --debug-agent option to the TestCentric GUI
 * 276 Deprecate old nunit-gui application on Chocolatey
 * 315 Reorganize Settings
 * 340 FIXED: Unable to run selected NUnit V2 tests
 * 347 Add TextOutput labelling of final test result
 * 372 Add command line option for specifying results file location
 * 394 Update engine
 * 395 Display version and path of loaded extensions
 * 397 Fix unhandled NullReferenceException thrown when test fails with Assert.Fail()
 * 399 Show the test assembly name in the main view's title bar.
 * 402 Set Project Configuration to use
 * 406 FIXED: Appveyor rebuild causes error
 * 412 Update link to Chocolatey package
 * 414 FIXED: Testcentric.exe needs icon
 * 415 Better installation documentation
 * 424 Use common dialog for extensions
 * 427 Ensure that agent exes are copied as part of building the project
 * 430 FIXED: Index out of range exception when adding a test file
 * 432 FIXED: TestParametersDialog enables Remove and Edit on startup

TestCentric Runner for NUnit 1.0.1 - August 15, 2019

General

This release fixes a critical error discovered after the release of 1.0.0.

Features

 * Includes version 0.15.1 of the experimental GUI

Issues Resolved

 * 325 Deploy development builds automatically
 * 380 Automate testing of packages
 * 388 FIXED: NUnit process with multiple assemblies will not load

TestCentric Runner for NUnit 1.0.0 - July 27, 2019

General

This is the final release of version 1.0 of the TestCentric Runner for NUnit, which is
primarily based on the layout and feature set of the original NUnit V2 GUI runner with
internals modified so as to run NUnit3 tests. Certain changes were made because of 
differences in how NUnit3 works and are described below under Features.

This new GUI runner was created by the TestCentric team: Charlie Poole, Mikkel Bundgaard,
Manfred Lange, Stefano Nuzzo and Robert Snyder. Community members who contributed code to
this release include Jeff Kryzer, zBrianW, Joseph Musser and Mattias Karlsson. Countless
other folks contributed by filing issues, asking questions and making suggestions.
 
Features

 * TestCentric relies on the NUnit engine to load and run tests. Features that require 
 an engine extension are only available if the appropriate extension is installed. In
 particular, this includes the ability to open both NUnit and Visual Studio projects,
 run NUNit V2 tests and save results in V2 format.
 
 * All direct access to NUnit project contents, such as editing, saving and adding
 configurations, has been removed. The user should use a separate editor such as
 the NUnit Project Editor to perform those tasks.

 * Because the GUI runs under .NET 4.5 or higher, any tests that you cause to execute
 in-process will run under that version of the framework. In some cases, this may give
 different results. By default, tests are run in a separate process and use the target
 framework for which they were built. We recommend you stick with the default.

 * The File menu no longer has entries for Load Fixture or Clear Fixture. New menu 
 items to select Process and AppDomain options for loading have been added and the
 corresponding Settings pages removed.

 * The Project top level menu has been removed since it was mostly used to contain
 entries related to NUnit projects. The "Add Projects" entry has been replaced by 
 "Add Files" on the File menu.

 * The Tools menu no longer has entries for Exception Details or Test Assemblies. 
 The Open Log Directory entry has been replaced with Open Work Directory.

 * The Result Tabs (Errors and Failures, Tests Not Run, and Text Output) may no 
 longer be hidden. The Text Output tab only displays Console output and the ability 
 to tailor it's contents has been removed with the exception of the option to label
 tests by name in various ways.

 * Version 0.15 of the Experimental GUI is included.

Known Problems

 * TestCentric uses the test id to select individual tests to be run. This is not 
 currently supported by the V2 framework driver, which throws an exception when 
 an id filter is encountered. The result for the GUI is that it is not possible
 to select individual tests for execution if any V2 framework tests are loaded.
 For that reason, we recommend that you only use this release for NUnit 3 tests.
 This problem will be fixed when a new version of the V2 driver is available,
 which includes support for an id filter.

Issues Resolved

 * 7 Credit for all contributors
 * 8 Icon and Logo for TestCentric
 * 224 FIXED: Appveyor build doesn't use generated identifier to tag packages 
 * 375 Clean up GUI About box
 * 378 Ensure that error message displays when exception is thrown in engine

TestCentric Runner for NUnit 1.0.0-Beta4 - July 17, 2019

General

This is the fourth beta release of the TestCentric Runner for NUnit. While it is still beta,
it is feature-complete. Since the actual execution of tests is done by the NUnit engine
rather than the GUI itself, it's probably reasonable for developers to use this on the
desktop, provided their CI is based on a stable production-level NUnit runner, such as
the NUnit 3 Console Runner or the NUnit 3 VS adapter.

Features

 * Version 0.14 of the Experimental GUI is included.

Issues Resolved

 * 368 FIXED: Arguments to --process option for GUI don't match NUnit console.
 * 369 Merge Options classes for two GUIs and move to common assembly.
 * 370 FIXED: Beta3: unhandled .net exception

TestCentric Runner for NUnit 1.0.0-Beta3 - July 14, 2019

General

This is the third beta release of the TestCentric Runner for NUnit. While it is still beta,
it is feature-complete. Since the actual execution of tests is done by the NUnit engine
rather than the GUI itself, it's probably reasonable for developers to use this on the
desktop, provided their CI is based on a stable production-level NUnit runner, such as
the NUnit 3 Console Runner or the NUnit 3 VS adapter.

Features

 * Version 0.13 of the Experimental GUI is included.
 * Added command-line options --process, --domain, --inprocess, --x86 and --agents.

Issues Resolved

 * 139 FIXED: Stop Button to interrupt infinite loop
 * 287 Assembly or project full name not shown
 * 337 FIXED: Stopping a long running test from TestCentric gui does not stop right away
 * 350 FIXED: Installed Extensions fields not cleared
 * 352 Incorporate NUnit Engine as a subtree
 * 357 Review whether File menu settings should be saved
 * 358 FIXED: Assemblies Running in Parallel (Regardless of Settings)
 * 361 FIXED: Process Model setting includes Single rather than Separate
 * 364 FIXED: Experimental GUI: Proper icons are not displayed for warnings and failures

TestCentric Runner for NUnit 1.0.0-Beta2 - May 30, 2019

General

This is the second beta release of the TestCentric Runner for NUnit. While it is still beta,
it is feature-complete. Since the actual execution of tests is done by the NUnit engine
rather than the GUI itself, it's probably reasonable for developers to use this on the
desktop, provided their CI is based on a stable production-level NUnit runner, such as
the NUnit 3 Console Runner or the NUnit 3 VS adapter.

Features

 * Version 0.12 of the Experimental GUI is included with support for user-defined icons
   and immediate text output display.

Issues Resolved
 *   5 Add online docs for the GUI
 * 229 Experimental GUI: Multiple and user-defined tree icons
 * 236 Experimental GUI: missing test output
 * 326 Update CONTRIBUTING.md
 * 328 FIXED: Reloading loads the assembly multiple times
 * 327 Document how TestCentric GUI is versioned
 * 333 FIXED: InvalidOperationException is thrown from RunStarting event handler
 * 336 FIXED: In TestCentric gui, Selected Categories are cleared on Reload
 * 345 Show names of settings in Text Output settings dialog

TestCentric Runner for NUnit 1.0.0-Beta - April 13, 2019

General

This is the beta release of the TestCentric Runner for NUnit. While it is still beta,
it is feature-complete. Since the actual execution of tests is done by the NUnit engine
rather than the GUI itself, it's probably reasonable for developers to use this on the
desktop, provided their CI is based on a stable production-level NUnit runner, such as
the NUnit 3 Console Runner or the NUnit 3 VS adapter.

Features

 * Version 0.11 of the Experimental GUI is included with support for saving test results,
   reload on change and reload on run.

Issues Resolved

 22 Create new signing key for TestCentric
212 Experimental GUI: Need SaveResults menu item
213 Experimental GUI: Reload on change
226 Display time in a more natural format
232 Experimental GUI: Reload on Run
306 FIXED: Save TestResult Dialog not initialized correctly
318 Disable ReRun on Change setting

TestCentric Runner for NUnit 1.0.0-Alpha4 - April 5, 2019

General

This is the fourth alpha release of the TestCentric Runner for NUnit. It is not yet recommended
for use in production work.

Features

 * Entries now appear in the tree display for any projects loaded
 * The GUI now uses a custom built version of the engine, based on the NUnit 3.10 engine.

Issues Resolved

164 Update NSubstitute to version 4.0
241 Terminate nunit-agent.exe / nunit-agent-x86.exe once they are no longer in use
273 FIXED: No project elements are present in the test XML received from the engine
285 FIXED: NUnit Agent locks dll
288 FIXED: Property dialog not showing assembly process id or appdomain name
290 Need a way to locate and examine log files
292 Remove project editor integration
294 Document differences from the NUnit V2 GUI
299 FIXED: Choosing "Run as X86" from menu doesn't actually load the X86 agent.
301 FIXED Tree icons of previous run do not clear when starting second run
304 FIXED Use new 3.10 release of NUnit engine

TestCentric Runner for NUnit 1.0.0-Alpha3 - February 27, 2019

General

This is the third alpha release of the TestCentric Runner for NUnit. It is not yet recommended
for use in production work.

Features

 * The Experimental GUI, which was previously a separate project, is now included along with the standard TestCentric GUI.
 * Assemblies and projects are now loadable using all process and domain settings.
 * Process and domain settings are now part of the File menu.
 * A custom engine build is included while waiting for the next NUnit engine release.
 * The zip and chocolatey packagegs now include pdb files.

Issues Resolved

 18 FIXED: Reload on Change not working
138 Double click test to start it
153 Changing font should affect status bar
154 FIXED: When opening solution file non-test assemblies cause an error message
155 FIXED: Redundant menu items under View | Tree
156 FIXED: Changing checkbox setting should not change default
159 FIXED: Project name not shown in tree
161 Create separate GUI Components assembly
163 Create Linux build.
165 Review and merge build script with experimental GUI script
170 Review and merge components assembly
175 FIXED: Start and stop button are misaligned
178 Status Bar height should adjust to font
182 Integrate ToolStripItem and ToolStripMenuItem Elements
185 FIXED: Not building Mono 5.10 or 4.6 under Travis
189 Merge experimental GUI into standard GUI project
238 FIXED: Categories on test fixtures not considered in test list design (Experimental)
251 Show file names when loading
253 FIXED: Add file to open files is broken
256 Use DialogManager to display open and save dialogs
257 FIXED: Error on reload when running in process
261 Run tests under 3.9 console runner
263 FIXED: Cannot load nunit test solution in process
264 Use custom build of NUnit engine
269 FIXED: No option to run using default process model or domain usage
274 Eliminate Default Setting Page for process model and domain usage
278 Include pdb files in packages
279 Remove engine version hack in build script

TestCentric Runner for NUnit 1.0.0-Alpha2 - November 11, 2018

General

This is the second alpha release of the TestCentric Runner for NUnit. It is not yet recommended
for use in production work.

Features

 * The GUI now uses the NUnit 3.9 engine
 * Reloading on each Run is now functional.
 * Alternate images for the tree are now implemented.
 * Saving and Restoring the visual state is now implemented.

Issues Resolved

 12 Use UpDown counter for number of recent files to display
 15 FIXED: Alternate Tree Images not working
 21 FIXED: Disabling Shadow Copy is Ignored
 76 FIXED: Exception "Cross-thread operation not valid: Control 'progressBar' accessed from a thread other than the thread it was created on."
 93 FIXED: NRE when starting the GUI
 95 Implement MVP for main form and sub-views
 99 FIXED: Scrolling not working correctly for ErrorDisplay
100 Don't display "Test-Run" as root node in tree with only one assembly
115 FIXED: Zero Length VisualState.xml file results in exception
132 Create TestCentric.Common assembly
144 Update NUnit Engine to 3.9

TestCentric Runner for NUnit 1.0.0-Alpha1 - August 3, 2018

General

This is the initial alpha release of the TestCentric Runner for NUnit. It is not yet recommended
for use in production work.

Features

This GUI runner resembles the NUnit V2 GUI, but since it runs NUnit 3 tests the internal implementation
is entirely new. In addition, features not available or not easily supported in NUnit 3 have been
removed. Some key differences from the V2 GUI are...

 * The GUI itself targets .NET 4.5, rather than 2.0.
 * We use chocolatey as the primary distribution method for the GUI. This makes extensions that are
 also installed through chocolatey available when running under the GUI. A zip file is also provided.
 * Displaying tests as a flat list of fixtures is not supported.
 * Merging tests in the same namespace across assemblies is not supported.
 * The GUI no longer understands the layout of NUnit project files, which is taken care of by the 
 NUnit test engine. Consequently, menu items relating to creating, editiong and saving such files 
 are no longer present.
 * The ability to open project files, including NUnit and VS projects, is dependent on the presence
 of the approprate engine extensions, which are not bundled with the GUI.

Issues Resolved

  1 Select Target Framework for the GUI
  2 Review of Initial Upload
  9 Update the About box
 10 Correct name for program in --help option
 13 FIXED: Number of Recent Files has no effect
 14 FIXED: Tree always cleared of results on reload
 16 FIXED: Flat list of TestFixtures not working
 17 FIXED: Reload on Run not working
 19 FIXED: Principal Policy not working
 20 FIXED: InternalTrace level not honored
 24 FIXED: Setting number of agents has no effect
 26 FIXED: Clear Results Setting is on wrong page
 27 Create CI Build Script
 28 FIXED: "Clear All" and "Check Failed" has no effect
 29 FIXED: "Run" context menu is never enabled
 32 Renaming test-centric to testcentric
 33 Restore Tree-based Setting Dialog
 39 FIXED: Cannot run the tests in TestCentric.Gui.Model.Tests.dll more than once
 42 FIXED: Not possible to run explicit tests using the GUI
 50 Review and reorganize Settings for NUnit 3
 52 FIXED: Show CheckBoxes throws NRE
 61 Disable or remove non-functional elements on Settings pages
 62 FIXED: Switching between full and mini gui display doesn't happen immediately
 63 FIXED: Check files exist setting has no effect
 64 Better error message when an assembly is not found
 66 FIXED: Project editor menu item not working.
 67 FIXED: Show Checkboxes menu and settings elements are inconsistent
 68 Save results menu should be disabled when no test has been run
 71 FIXED: Multiple files on command-line or in file open dialog not opened
 73 Multiple loaded files have no root in tree
 80 Standardize naming of TestCentric packages and executables
 83 Update tests to use NUnit 3.10.1
tools\Images\DebugTests.png
 
tools\Images\GroupBy_16x.png
 
tools\Images\RunTests.png
 
tools\Images\StopRun.png
 
tools\Images\SummaryReport.png
 
tools\Images\Tree\Circles\Failure.jpg
 
tools\Images\Tree\Circles\Ignored.jpg
 
tools\Images\Tree\Circles\Inconclusive.jpg
 
tools\Images\Tree\Circles\Skipped.jpg
 
tools\Images\Tree\Circles\Success.jpg
 
tools\Images\Tree\Classic\Failure.jpg
 
tools\Images\Tree\Classic\Ignored.jpg
 
tools\Images\Tree\Classic\Inconclusive.jpg
 
tools\Images\Tree\Classic\Skipped.jpg
 
tools\Images\Tree\Classic\Success.jpg
 
tools\Images\Tree\Default\Failure.png
 
tools\Images\Tree\Default\Ignored.png
 
tools\Images\Tree\Default\Inconclusive.png
 
tools\Images\Tree\Default\Skipped.png
 
tools\Images\Tree\Default\Success.png
 
tools\Images\Tree\Visual Studio\Failure.png
 
tools\Images\Tree\Visual Studio\Ignored.png
 
tools\Images\Tree\Visual Studio\Inconclusive.png
 
tools\Images\Tree\Visual Studio\Skipped.png
 
tools\Images\Tree\Visual Studio\Success.png
 
tools\LICENSE.txt
Copyright (c) 2018-2019 Charlie Poole

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

tools\Mono.Options.dll
md5: 9915460C3376FD883C2B53487A5F9EF1 | sha1: EB5AADE056D17AA71584B89E42FECD84A0248382 | sha256: 02F97BD6698C9F073F97F83157AAB223C7F15FF5B39EE0D82C89FCF5A1BDE315 | sha512: 5EF923C200582F37238B291BE16926EE58F5AF75F49E7B21900CDCB41CB5D97D9527508B443F5D3C416DC7969B6A5537DAD717B4315F75698206654EE6AA0541
tools\NOTICES.txt
The TestCentric GUI Runner 1.0 is based in part on the NUnit 2.x GUI Runner, 
with portions of the code...

    Copyright (c) 2002-2014 Charlie Poole or 
    Copyright (c) 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov or 
    Copyright (c) 2000-2002 Philip A. Craig

The TestCentric GUI Runner uses the NUnit 3 Test Engine to run tests...

    Copyright (c) 2017-2019 Charlie Poole, Rob Prouse
tools\nunit.engine.api.dll
md5: 7E15F91EF58AC443F7170E2AFAE03087 | sha1: 9A2AE27FD58B019CF9104289074B8571FCE81270 | sha256: 2191097317CEAF4E4D62AEF9B3A73965B2640FA810C1D08374A14CA2EF35D2B6 | sha512: 0DF7281D2FC8D06CAA7650385B342CC08BE2238ED1318ED9929302309E972F2E0FC19D063DD3554ACD64C865F5EA2E97DB3A29B9309833B50FA748C8F23E27E2
tools\nunit.uiexception.dll
md5: 9FE0BE469A3B2DFDB1909EF9EF691488 | sha1: 3815C8C28E32B8FE7881F51B2A18842019B3127F | sha256: 6E575F8B0DD477FD4D96E13DBE7BF01BF90D7DA55550365BC31400B944AF54F3 | sha512: AB90C18750CD194DD57A7A2147045AF758B13BFD1F1D1DA63F50EF2A9BCC129BE0134282AD34C3EA0C6D1A3577B99D500BCEBFB7AE1B8A626FF43C9FB295DC2B
tools\testcentric-agent-x86.exe.ignore
 
tools\testcentric-agent.exe.ignore
 
tools\testcentric.choco.addins
 
tools\testcentric.engine.api.dll
md5: B25ED68163BE01F659A02FF084B566B7 | sha1: AF53DE785A6B8BB2A53E5536F2B3D041C2805AA2 | sha256: CAD84B5D6EC1F81EF5C2D086AD827788179FDF51744C76143CA763E8DEE55F70 | sha512: 46E3A7503151E32182C15197E27B83237B3D1C8EDC10549D52696049222059B29B8F6C835F233E06C784F8BC13C1FF3702C35E480315FA28170C87DA316C4EC2
tools\testcentric.engine.core.dll
md5: AAA1A47BEA1AA78DDF8B23326E8637B3 | sha1: 22A1218D07D8A8ACB36E18BB05FBF286B4A2F71F | sha256: D098E36171C817E57FAC222FB498C8874BC61C62B59F45912F5BB8AB866B7F05 | sha512: 3DEE16A373635126CA7CE6949A00223D5EDD90481E760CBD43D83D9284D81024C4D15DCFB8154C25876DA79FF570A312C754DBA5640A7714EE4F7A0A770EEC1E
tools\testcentric.engine.dll
md5: 777111C540D4DC2AAD7692D7EA9C7AF1 | sha1: 6DB380DEAD8D32C0D21E6DD01ED8374880275619 | sha256: B6486D9712D86D76AEAAE0165F9DC6412BC29F25D8BB47149CBD27D7248840A5 | sha512: 4CC8FB5E660F72D647E5E25F7D60AFD178907715BCEFD2D083D85721BC9FD2813209A10023CB0757D1EBEED773AFEA15E6F38D4B972927DF984E0C1CE4CEEDB3
tools\testcentric.engine.metadata.dll
tools\testcentric.exe
md5: B509DB406D31C32532998A7FF321A016 | sha1: DD0A6B05CBA3BC3E5E4D7D550565812C1DCE1DB0 | sha256: 823AD33B3CD5D9C7B6AB5266311222324D1CAA6B259921D212B8DF5B73494D23 | sha512: 727496FFEC38FA9F4B659837D5D6790AE1B3AE27AFFF0301D79ED65452D094586A053545CFA8ACA519328FCB260CC0DB78D8270254CB73087F6B5CF730B434F8
tools\testcentric.exe.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!--
   The GUI only runs under .NET 2.0 or higher. The
   useLegacyV2RuntimeActivationPolicy setting only
   applies under .NET 4.0 and permits use of mixed 
   mode assemblies, which would otherwise not load 
   correctly.
  -->
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <!-- Comment out the next line to force use of .NET 4.0 -->
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
  </startup>
  <runtime>
    <!-- Ensure that test exceptions don't crash NUnit -->
    <legacyUnhandledExceptionPolicy enabled="1" />
    <!-- Run partial trust V2 assemblies in full trust under .NET 4.0 -->
    <loadFromRemoteSources enabled="true" />
    <!-- Look for addins in the addins directory for now -->
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="lib;addins" />
    </assemblyBinding>
  </runtime>
</configuration>
tools\TestCentric.Gui.Model.dll
md5: 11F9D529BC290E1E758F9F636BCD5727 | sha1: D08DD46B6CEE5078E24401FBC2482CB1315B4C24 | sha256: C44318D9496F6338B0F66E7200CBDE56C89A0E0F8587445D17E91F2243E26FBA | sha512: 2EA0916991F5F9DE02FE9F53DDCDF9395F662AA47492C6257D983DE5B0EF1AF2FF5A52BF76A72F5AD266DEFEAB1AF14C4DD9BC40D893F25F5AFDCAF3BBE3C200
tools\TestCentric.Gui.Runner.dll
md5: 50AA32D59DBD77F6A888DCBBADA35A7B | sha1: 87514BB9DC191296F7893BF3DD274235031D7B9E | sha256: 885345F904E31B11435B89BE3A83F00F4CEA13928B70BC0561F3CEC1B5DFDC9C | sha512: 8C759B0394A31126AA88EE94DA8FB8976DEE406B971AD17D8324D9F9E6BC70002219798D581B52DA50F2B368211DD34BAF37317A4DD7D60E826667ECCAEB6BC5
tools\testcentric.png
 
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

This package is published by the author of the software, Charlie Poole.
Any binaries will be identical to other package types published by the 
author at https://github.com/TestCentric/testcentric-gui.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
testcentric-gui 2.0.0-beta6 48 Wednesday, October 16, 2024 Approved
testcentric-gui 2.0.0-beta5 128 Thursday, May 16, 2024 Approved
testcentric-gui 2.0.0-beta4 557 Thursday, November 23, 2023 Approved
testcentric-gui 2.0.0-beta3-1 73 Wednesday, October 25, 2023 Approved
testcentric-gui 2.0.0-beta3 28 Sunday, October 22, 2023 Exempted
testcentric-gui 2.0.0-beta2 73 Monday, September 4, 2023 Approved
TestCentric Runner for NUnit 2.0.0-beta1 147 Tuesday, May 9, 2023 Exempted
TestCentric Runner for NUnit 2.0.0-alpha8 111 Tuesday, April 25, 2023 Approved
TestCentric Runner for NUnit 2.0.0-alpha7 65 Monday, February 6, 2023 Approved
TestCentric Runner for NUnit 2.0.0-alpha6 102 Saturday, June 18, 2022 Approved
TestCentric Runner for NUnit 2.0.0-alpha5 92 Saturday, May 14, 2022 Approved
TestCentric Runner for NUnit 2.0.0-alpha4 192 Sunday, October 3, 2021 Approved
TestCentric Runner for NUnit 2.0.0-alpha3 84 Thursday, September 30, 2021 Approved
TestCentric Runner for NUnit 2.0.0-alpha2 230 Sunday, August 15, 2021 Approved
TestCentric Runner for NUnit 2.0.0-alpha1 130 Thursday, July 1, 2021 Approved
TestCentric Runner for NUnit 1.6.4 1060 Friday, December 2, 2022 Approved
TestCentric Runner for NUnit 1.6.3 183 Monday, August 1, 2022 Approved
TestCentric Runner for NUnit 1.6.2 630 Thursday, March 25, 2021 Approved
TestCentric Runner for NUnit 1.6.1 231 Sunday, January 17, 2021 Approved
TestCentric Runner for NUnit 1.6.0 160 Monday, January 11, 2021 Approved
TestCentric Runner for NUnit 1.5.3 156 Thursday, December 24, 2020 Approved
TestCentric Runner for NUnit 1.5.2 170 Thursday, December 17, 2020 Approved
TestCentric Runner for NUnit 1.5.1 149 Tuesday, December 15, 2020 Approved
TestCentric Runner for NUnit 1.5.0 141 Wednesday, December 9, 2020 Approved
TestCentric Runner for NUnit 1.4.1 289 Friday, September 4, 2020 Approved
TestCentric Runner for NUnit 1.4.0 473 Friday, May 1, 2020 Approved
TestCentric Runner for NUnit 1.3.3 207 Saturday, April 18, 2020 Approved
TestCentric Runner for NUnit 1.3.3-rc1 160 Friday, April 17, 2020 Approved
TestCentric Runner for NUnit 1.3.2 238 Tuesday, April 7, 2020 Approved
TestCentric Runner for NUnit 1.3.1 269 Saturday, March 7, 2020 Approved
TestCentric Runner for NUnit 1.3.0 213 Tuesday, February 25, 2020 Approved
TestCentric Runner for NUnit 1.2.0 227 Sunday, February 16, 2020 Approved
TestCentric Runner for NUnit 1.1.0 415 Saturday, November 9, 2019 Approved
TestCentric Runner for NUnit 1.0.1 297 Friday, August 16, 2019 Approved
TestCentric Runner for NUnit 1.0.0 270 Saturday, July 27, 2019 Approved
TestCentric Runner for NUnit 1.0-beta4 213 Wednesday, July 17, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta3 182 Sunday, July 14, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta2 216 Thursday, May 30, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta 221 Saturday, April 13, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha4 229 Saturday, April 6, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha3 218 Wednesday, February 27, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha2 237 Tuesday, November 13, 2018 Exempted
TestCentric Runner for NUnit 1.0-alpha1 244 Friday, August 3, 2018 Exempted

This package has no dependencies.

Discussion for the TestCentric Runner for NUnit Package

Ground Rules:

  • This discussion is only about TestCentric Runner for NUnit and the TestCentric Runner for NUnit package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or TestCentric Runner for NUnit, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus