Downloads:

626

Downloads of v 1.1.0:

49

Last Update:

09 Nov 2019

Package Maintainer(s):

Software Author(s):

  • Charlie Poole

Tags:

testcentric nunit gui runner test centric testing tdd

TestCentric Runner for NUnit

1.1.0 | Updated: 09 Nov 2019

Downloads:

626

Downloads of v 1.1.0:

49

Maintainer(s):

Software Author(s):

  • Charlie Poole

TestCentric Runner for NUnit 1.1.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade testcentric-gui -y --source="'STEP 3 URL'" [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="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure testcentric-gui installed
  win_chocolatey:
    name: testcentric-gui
    state: present
    version: 1.1.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'testcentric-gui' do
  action    :install
  version  '1.1.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: testcentric-gui,
    Version: 1.1.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller testcentric-gui
{
   Name     = 'testcentric-gui'
   Ensure   = 'Present'
   Version  = '1.1.0'
   Source   = 'STEP 3 URL'
}

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


package { 'testcentric-gui':
  provider => 'chocolatey',
  ensure   => '1.1.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install testcentric-gui version="1.1.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 09 Nov 2019.

Description

This package includes the TestCentric GUI runner and incorporates the NUnit test engine.


tools\CHANGES.txt
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\Experimental.Gui.Runner.dll
md5: 122CF8E8C2F724339321F5CF41DB13CA | sha1: 1BEF3D473568C1FBB83B8201947875288B541DF5 | sha256: 35F601A102DCAAF8870021B09ED549AC682F60CDC0E3B41BB0D6CD1255AE6629 | sha512: C11030427DEE8589440A4DF76EE99365406D86C0F0C33C24553A7C580CDF40CDAD759EEA5A1A2EC6FBE4FA60F2E4EDCB18F64F5D9068D6D78165286864E6FCFE
tools\Experimental.Gui.Runner.pdb
 
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.Cecil.dll
md5: F7785642F7488172853A3C03F6FCB8EA | sha1: 8A2E8FD69D39024A2F30FC0642F70FA832690772 | sha256: 79AA6C41BF35EF59CD7DED94715B7AE2B9DFF5C3DAAF18047255D31BF1D7C77E | sha512: 201F22CAC7BE81B41918DADB59FB7EF0AAF1F3CC1381558988A969A708C7F632D0D8546E9A52258CE2402933C2965FFC4BDB8484A75E8468C6868914C12EAF4C
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-agent-x86.exe
md5: 7C5C52B35B38EE4F100599FA24F9A00E | sha1: 726198A5B9415CD075AE86460982A3D851ED5A8A | sha256: A818BC96F03D90BFCF90EE5E0A3A4078C203F170C911652C0E062B34A79812B2 | sha512: D28D28A388A4C3B469FA3190D0F68EADBC292388CA27F461DBE0736CB26BC2908B0E623DFB5387A2F10D427DB316AA12712254A7EF67E710B0EA6747F5FD2D4D
tools\nunit-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\nunit-agent-x86.exe.ignore
 
tools\nunit-agent.exe
md5: 60327C212D47AC165C1EE5059CE963A3 | sha1: 46956E61F27C1A9849B9CAD872CB774A7009CAB5 | sha256: 80411E047D3CE6409EBD7A9AC33C249E940B2ADA7BFFAD9060531E6B27A42FF9 | sha512: F081AF0706E9251F99E5D9CA3213EF76A05387AAA71C9D1C65431AB97A391AB76446B87D81F7FCE5FB884D7F01CCDAA6E6FDE9DF14F0ADFD1C42D2D93342A44B
tools\nunit-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\nunit-agent.exe.ignore
 
tools\nunit.choco.addins
 
tools\nunit.engine.api.dll
md5: 64A052F2B77F17B7DAFB6C78797A1F5A | sha1: AFE7F584F89CE2E37B65E38470DBA1E8F23F41F6 | sha256: 6F760A3A0AD30B0102BC74C948FD238A4A516A3F649C1D33E4038D1C3B31CDCA | sha512: 2E80741584BD5485B4E67BB18BEA6B5749C78BA68CE432F45BA4A33B9250507E24E3EB0DD52A057CBA420001164C08D27EB840D09FE37E462B7B1A2EE75325A8
tools\nunit.engine.dll
md5: F34B5745E8450C90EE3DCF8847A00F55 | sha1: 73DABD5C99EB539383248A448E35BAA6BA5C3DFD | sha256: 2300F3D95E878AAD65F77CF1754DC7A4FE07FA34974F126D81D540A5651F09BE | sha512: 9BAFD11A4BEE3E414912989050A93BE12F144AFCAE2169EEE899CA33C46B8C415A8C34520C182B3521C5AC4BD0B683BB4576572CFF11ECCE699FEF289A0EA0BF
tools\nunit.uiexception.dll
md5: 178795E94307327DAD0457C9B6F8B893 | sha1: 05DEC4EBD8146BBEDD309A97C3D6F3C6C0AEAF66 | sha256: B8D93031E3B26FC1CDAAED595590B931796CC922B0E7854A2EFAA37C63AA45EC | sha512: 8D68303458555DBBFC283C935396E0690CE35B4E30014B4AE976477FE29F1912338B28F1795827F9E3807AFCC9155D4624201D35563F6917BA12230F1DFCF88C
tools\nunit.uiexception.pdb
 
tools\tc-next.exe
md5: 91318E6B6DB19B4CB3D8533338890FBB | sha1: C0781247216841DA5C55BE4D3379BD208A1C598F | sha256: 87FABD5C2BFC32C9F6D1747BA9CC9526FC806AAC61BAF65679F79DDC766B47B0 | sha512: 983A0894B583C2176FB472A13113AD362A7C04A2E2040A669F0D5C13094FAE38FDE2D704D2116A49C841A55168002823369A3BCE68AA958940BA6F9267A7B4C5
tools\tc-next.exe.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!--
   The gui runner runs under .NET 2.0 or higher, selecting the
   highest version runtime available.
   
   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">
    <supportedRuntime version="v4.0.30319" />
    <supportedRuntime version="v2.0.50727" />
  </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" />

  </runtime>

</configuration>
tools\tc-next.pdb
 
tools\TestCentric.Common.dll
md5: 03BC2CF1CC540767E9D1AA5F64BE2C88 | sha1: CA498BD80FB1ECB87D44885AF81A6E4DDD3AA314 | sha256: 0591B9E0516A12B4A1490E0636B0CCA1CDC5C614532D5AE4FF29AFF955BD1424 | sha512: CFA83B478CAACBA683CC620C88C60D616B61641E6EFAFE93B9310A9FFBE0834FDCF7282D62C0B3D260BD1DD8B01C33BD72F101A41796510B9AFB5BB416049D62
tools\TestCentric.Common.pdb
 
tools\testcentric.exe
md5: 2F44EF392514EEF050AFDA23C77779A0 | sha1: A51DACF485DC39A3300C486DD36F924536BF5F16 | sha256: 5B64C7FF503964EC6E032E1DB7CB1692043B97974AFB510F9141D3CE1C03A820 | sha512: 89A42A01B2130FA759CB1B4AF9C5B98D6C67525A774C017DDD5D7090ABFAC8B5C5ABA1D4A9298206ECF41A50615A3BC4FD0EC49143D33525E8689FBBE41B4A96
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.Components.dll
md5: C8C4829D81DE3526D56940E13C0B29DF | sha1: 99F8B4335D3840E924613C26B49EC94FC5F0C1C4 | sha256: F0893A93E536702C3858920DBBA8D1D710F547AD83BEB916E35259712BE359B9 | sha512: A1CDD9DC039D5A6F89DCBD50BDB801480553D3E086362DBF7757A35DF67D44D12E0490A581EB29D76E6701015E74D5A2E2F2A76F08F2B1812A6AF0097DD1382D
tools\TestCentric.Gui.Components.pdb
 
tools\TestCentric.Gui.Model.dll
md5: F8E00FFB5B62D547A779FF6CAB01524C | sha1: 1733E16D37F4A08CD9E8883963042F21DE4F1F25 | sha256: 1B68C2771332943E5E4EBDEA85B853DC7E6B97EC3CD9A2FE09F1D1C082C54062 | sha512: CE578A9B66C1FFFC35C543C0269FC1F1ADA650678252665EF13818D5823DB2704D0712CCA735C8BA342BCA78F9949AAD9C65EC6C21C352BB3681C537D72FABED
tools\TestCentric.Gui.Model.pdb
 
tools\TestCentric.Gui.Runner.dll
md5: 5BF0BB76345A19ABCF61309E3E5077C9 | sha1: 67D1D72B38131B302DDE4637DB5471254C62B752 | sha256: 49493A45561DCD0F00939733B5EFE12D4FB9EA608FDEEAACD0A4A5F772C3B7B6 | sha512: CB7DB667C7DB34F567B04A73348D101E5F26ED3EBF79684C2E62254674FB654A7210CFAEF3B0F6A905E47949108790FA90BBFB1DBAB55403D8223695D098D215
tools\TestCentric.Gui.Runner.pdb
 
tools\testcentric.pdb
 
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.

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.

Version Downloads Last Updated Status
TestCentric Runner for NUnit 1.0.1 139 Friday, August 16, 2019 Approved
TestCentric Runner for NUnit 1.0.0 75 Saturday, July 27, 2019 Approved
TestCentric Runner for NUnit 1.0-beta4 33 Wednesday, July 17, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta3 30 Sunday, July 14, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta2 44 Thursday, May 30, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta 47 Saturday, April 13, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha4 45 Saturday, April 6, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha3 46 Wednesday, February 27, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha2 54 Tuesday, November 13, 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