Downloads:

567

Downloads of v 1.0-alpha3:

44

Last Update:

2/27/2019

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.0-alpha3 | Updated: 2/27/2019

Downloads:

567

Downloads of v 1.0-alpha3:

44

Maintainer(s):

Software Author(s):

  • Charlie Poole

TestCentric Runner for NUnit 1.0-alpha3

This is a prerelease version of TestCentric Runner for NUnit.

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.0-alpha3
    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.0-alpha3'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: testcentric-gui,
    Version: 1.0-alpha3,
    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.0-alpha3'
   Source   = 'STEP 3 URL'
}

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


package { 'testcentric-gui':
  provider => 'chocolatey',
  ensure   => '1.0-alpha3',
  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.0-alpha3" 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 is exempt from moderation. While it is likely safe for you, there is more risk involved.
Description

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


tools\CHANGES.txt
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: 0F5A9A5AEF6F966C02480CDB7BD027A8 | sha1: DB39604035ED1FB029C9EF15FA91A327E8F56399 | sha256: 63520F79BF5A5AF24F08C3EDC39A0B2D3967633F22103EC1BE41AE90CB84761F | sha512: 16682AD7AA4445D8ADAADF698699F14D5170E9940A6FB15FE7F1D3CF29B61A601AAE8FE1E1357005B36E8660D3344B6496785F35B1C30A2E56FD84BF08630D16
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 NUnit 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 NUnit Runner uses the NUnit 3 Test Engine to run tests...

    Copyright (c) 2017-2018 Charlie Poole, Rob Prouse
tools\nunit-agent-x86.exe
md5: EB57EE0672E9E7F15FBD82A1F5A7738D | sha1: C5E47B2066C2491BB07B7B70E7746DAA04B3CFC9 | sha256: E5D59EFA51B0EB7860334779C4BE1E3FA4AC22F2873F876BF3251408BCF0C772 | sha512: E04FFE8E5DEA2416E74DBA70973C7AD0A88131733099EDDCD41F61A7D0E9E700BA3FABBEA70CC10ED9DD2C0993B6655627A7C3E1DC9376FD5F0C4568A0C51AE0
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" />

    <!-- 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
md5: C393C067AC23D1113848493FAC832EF8 | sha1: 53792F7406BFFCF26E32B1F8D7462B42470FA6D0 | sha256: 3E877A5982627182C57FD45E95AD19B2FB115EA00722BAEE8CF2ADA7AF47F2C9 | sha512: E0D518DA7F6542C8B4A1AE7A95AC32B8E6DB78E16E615479B2CDA377BDC528EABF0D0DE998C0D4C56F045DDF4D8DF502E5F8DC601829CB381249D8CEA190B8BF
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" />

    <!-- 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.engine.api.dll
md5: 07CD8874A6FDC4D8551226DEDAF46863 | sha1: 2ABD22777A0D204E8C4371870F45B2FBC9DAD5EF | sha256: 1FF299B5D4D23301DF6DEA807888B047F12DA7E4183D496EC116EE5B0DDF0CE7 | sha512: 1DAE204861D2CE6997F3DE85B8B3378EF5BBA8EE168DBF7DCAA2D4B171ADF69AF62D144BAFF2BA0180E4A82D38D05F534286DCD1ED9EF8C58C580E4072524ED6
tools\nunit.engine.dll
md5: 9A6DD1031B925D4D3BA97DBB7ED470B0 | sha1: C2407D062FA6F5034C97DB40A76726295F90685A | sha256: E1CD32FA17395C88F828B320D4F9A8B791D8D8A079E15D25695867FB0539EAC2 | sha512: D0335542FC554AD325C2CC966B47B7B35EEBF2C208122B1D0855F00AF73D80B0892AD57CD061D20CC5ED92127807FAEF566D0492265080DEDBA48A11F3D10A90
tools\nunit.uiexception.dll
md5: 14BE83A1C2362403321B9C891C8EF770 | sha1: 87C0FFB1495EFF802D655A93A9D84F3EF7312A8B | sha256: E3745AE3BF20A041CEFC842FAF7FE0EFD5E13C7893DDC45F11796C661AE0FAE9 | sha512: 635877976E7DFFE42A397D5A6FF418658EBFB431BFB1A04D18593EB90823B9A20D9FE05D67463E9B2463E2C0CA35C40907B921153421852B19A06EFC5993E4C4
tools\tc-next.exe
md5: D049E232C7CEF96D25B5B0ED95E3F24C | sha1: FD363C6A8D3E500E4FB59AABE21580945C0E55CA | sha256: B4D59CA3C2F860A1258B588552DB35DEE9F5B3793821304555D22DD520D25BFD | sha512: 4ACB437132F80E6ED7A868D6B561728856719AE4E801D1CEE6B718D837415B9137BE8D59B6677DF5828D1800E7DC1C2755E25516C37B55C177F07E07F219DA4D
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\TestCentric.Common.dll
md5: 83B7AD8D749728334B760F2B76FF9DAC | sha1: 9540C3C4EA0A2CD840510282F1B687DB734DB600 | sha256: A464ED56F5DF14F81012F8B0749E1C981CC9D550F7DF4A520359324E5B749ACC | sha512: 915E22861738BC9D3D883D4BF85B9370513385DA02E8E72B26ABB537335D28DF729EB8467A73560760450C29FA63CFCA13CDEDA6406DDED9D517C8C869303652
tools\testcentric.exe
md5: EE2230E545A43D38FDE923C4B8096F4F | sha1: 027A95C73D7437E52FE375FEE9DE54599938C8AB | sha256: 0C48698767478EF3285A545E9A629493FF38D9764B061C97E1D14791F798997B | sha512: 6E08A02D923E70DDCDC5AC3E587A5A91D69DFB47026FFB088F2C0D36D31AF786CA9572AD59A7D8E392A779A3D5FBCF4BF5B055156D70516D05EF4B5B38A81539
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: D62EF7D595F916DD860EB5A26A02DDAF | sha1: F51FA78983C543D7799AB97D4EF8DDB0D7A06E95 | sha256: 84513A1B52EA26333BDF46BD2937405C7E0A6B35BC08D5ABC8E4746D2FA6226F | sha512: B95D11CFA0F523DA07E0D3577FF94218984B39D2A14B42A34C8125F79C6F8B84CBB059B71525D511DBC870EBFB920240FD8F0B78F2624CD1207BFEB3DB948737
tools\TestCentric.Gui.Model.dll
md5: FFE758450C72B2461C0D221ED7B2D43C | sha1: 6962FD5688B261B3D22A37ED04F7891C3FD5168D | sha256: 7AD0689118406726FFCF77275836E3AA808784D55DB94AA104A36B74FA128FBA | sha512: A812069197BB0C04D6632A7F7FDA4DB809D298E1175D66A1E80063C66B25DCAB4D3E1A9C6E8F2B60CAEDA49BCC1E3881675A868524554354FBD9505136BA013F
tools\TestCentric.Gui.Runner.dll
md5: 7DDB803AE11791B748C551CA5CFB55D9 | sha1: 2953763A0FDF56D0D70F56B30905D32747B1425F | sha256: AA44C5A22D71329741EF7D6EA17A1FA1C7DBC95420B25FC01C1D4AA0000A9467 | sha512: C36D85198CE60B75C57099BCB5D0BCB836E9C1437BFC51DE3C35A06AD4FBF0F9A5FB9AC0F96020FFE17B4FC4824AD4E3672FCB18E3A9FC90995046A3AEE660D9
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 135 Friday, August 16, 2019 Approved
TestCentric Runner for NUnit 1.0.0 66 Saturday, July 27, 2019 Approved
TestCentric Runner for NUnit 1.0-beta4 30 Wednesday, July 17, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta3 28 Sunday, July 14, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta2 40 Thursday, May 30, 2019 Exempted
TestCentric Runner for NUnit 1.0-beta 44 Saturday, April 13, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha4 42 Saturday, April 6, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha3 44 Wednesday, February 27, 2019 Exempted
TestCentric Runner for NUnit 1.0-alpha2 52 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