Downloads:
9,933
Downloads of v 1.0-alpha2:
237
Last Update:
13 Nov 2018
Package Maintainer(s):
Software Author(s):
- Charlie Poole
Tags:
testcentric nunit gui runner test centric testing tddTestCentric Runner for NUnit
This is a prerelease version of TestCentric Runner for NUnit.
- 1
- 2
- 3
1.0-alpha2 | Updated: 13 Nov 2018
Downloads:
9,933
Downloads of v 1.0-alpha2:
237
Maintainer(s):
Software Author(s):
- Charlie Poole
TestCentric Runner for NUnit 1.0-alpha2
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
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
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:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download testcentric-gui --internalize --version=1.0-alpha2 --pre --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade testcentric-gui -y --source="'INTERNAL REPO URL'" --version="'1.0-alpha2'" --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="'1.0-alpha2'" --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: '1.0-alpha2'
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 '1.0-alpha2'
options '--prerelease'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller testcentric-gui
{
Name = "testcentric-gui"
Version = "1.0-alpha2"
Source = "INTERNAL REPO URL"
chocoParams = "--prerelease"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'testcentric-gui':
ensure => '1.0-alpha2',
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.
This package is exempt from moderation. While it is likely safe for you, there is more risk involved.
This package includes the TestCentric GUI runner and incorporates the NUnit 3.9 test engine.
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 Alternate Tree Images not working
21 Disabling Shadow Copy is Ignored
76 Exception "Cross-thread operation not valid: Control 'progressBar' accessed from a thread other than the thread it was created on."
93 NRE when starting the GUI
95 Implement MVP for main form and sub-views
99 Scrolling not working correctly for ErrorDisplay
100 Don't display "Test-Run" as root node in tree with only one assembly
115 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 Number of Recent Files has no effect
14 Tree always cleared of results on reload
16 Flat list of TestFixtures not working
17 Reload on Run not working
19 Principal Policy not working
20 InternalTrace level not honored
24 Setting number of agents has no effect
26 Clear Results Setting is on wrong page
27 Create CI Build Script
28 "Clear All" and "Check Failed" has no effect
29 "Run" context menu is never enabled
32 Renaming test-centric to testcentric
33 Restore Tree-based Setting Dialog
39 Cannot run the tests in TestCentric.Gui.Model.Tests.dll more than once
42 Not possible to run explicit tests using the GUI
50 Review and reorganize Settings for NUnit 3
52 Show CheckBoxes throws NRE
61 Disable or remove non-functional elements on Settings pages
62 Switching between full and mini gui display doesn't happen immediately
63 Check files exist setting has no effect
64 Better error message when an assembly is not found
66 Project editor menu item not working.
67 Show Checkboxes menu and settings elements are inconsistent
68 Save results menu should be disabled when no test has been run
71 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
Copyright (c) 2018 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.
md5: 4DA5A3500C6F8B8F7823F7D65316B184 | sha1: 7C26061C0A2902E532A626CAD2F506AAA13B9C8F | sha256: AA16074961DB13EBE44EB4A0127A85947DFC975EEA4034F2319526E27DFDDA42 | sha512: 0940257582891CBB0F51823AE0F0DE31C97FEC4293A87F48067CB9C10A1A8D3A12C70ACCA6D626A58CFCA7443B241013AC3F8ED30D39201CF186DCC61C590599
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
md5: F8A994042AD8AF58055644A83EF22476 | sha1: CA00E4F98009D6A9A101F5726CC2B698D83CA4DF | sha256: 9C534C99453B8320CE8963FA3E2DECE8B5C744B94FA3D1368FA8F9B50752C1A2 | sha512: 21FE745A6E554B002F830924B44DA3D0BC139A1763D999746578A17AEB18025F279C26EE30D0F88588DAB11B844CB9C179E177D4EE4D5E46083855A8FADAE507
<?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>
md5: 543E0F08D9C4AAA63FF3A24D9B58CBC7 | sha1: D028871E9F96035CDD6CEE2A0804430E2428FE11 | sha256: 2B336D8371C3F91CB6B92A978E41607807A89B28FA6F1FC9A6DD5C39C5AEA355 | sha512: FF8545639900D774319457C2F89EE53D14111D4AAF86FEC037A6526EA24C650101C5C97B8124FCF5D722E047FB601C6ECE25E61BD4C67AA65A9D6BCB674E26C2
<?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>
md5: 46306DCBCF2D3C440247F32F93095314 | sha1: 0A4764324B83DF99425AC7DEDA21E56CA19050AC | sha256: 01726629283DB14B5EB5614B7230985CE547E6C99C8E62248E68A5AEA4940F30 | sha512: ADD59C25FEB792E1EF03C2B3C68663E5CDD045ED08D0575D069E6C9D2BFA3124BD7660DF6C693B0825FF9A8C1DE24F732F678DEC72498148D61EF4DA1BCFC5BE
md5: 30ED547A3F3051AFCB969E2C961D6EB3 | sha1: D5006752C5AF05062D35DF4FC4225188354ACD00 | sha256: 44D2817A2BE4E8AF4F7C0FE5BC424C77CAE940251AB3AD44FF6D4EA497C8F914 | sha512: F4154C2FCFF0BD477E08FBF7100C5FD5B72B10945D7B3408D668859986CFF7EA2F1792B44D299F70F575C1D8E0B005C38D66C0DACEEF7E83197F25A8D43180BE
md5: 47D8A9311D7EEBE80D254297BCB0EAAA | sha1: 53C03A2D8511357425000E3429231A9313BDC90D | sha256: C585BD6CA1AB2C56E95DA6B48F63DC179B4FCD8F9C085A9FBE011B4F19D14D57 | sha512: 4CD6BC9C9AF30CC3F91E9CF98F3002D2E8875D5914900CACC37E32C3ECE02C7ABE7912D8753960A5D66E393AD7D1632CA9F2D1E5AC7C9E1BB114317D5EEBC89A
md5: 667198F9FE4CF1375AF53F3713B8BA9A | sha1: C32162A18ADD3A617A1A85B11EB38C402FDA9029 | sha256: 5A87973EE2B0EA93332B2196F6EF195868EEBF91E4636EE932E0E785FE1CFCE0 | sha512: C36249EBBC1C122055411CEF5B28BDDA9E640DA05AC2B07568D54FA8F353034F8B58BA6B60D7C5F88DBAABF172CD63AC6B4DCB7C5FAC1DBEC0D1A9C603ABB582
md5: F2664DD6AF7BFC0F091F0230FC105173 | sha1: B16C9A8BF767A9ABB6A0E3F8E517C37F3EB2AD87 | sha256: 29181EB99FCBFFAE9076B8BDB398D4AAA8A9EDBC906353E90AFD7F411353531C | sha512: 43B8904BBB5A0FA87981897158942E51B57716D02230FC992F2A4E28EA85960A33BFAE8B2F799C34AC00EADDD86A56BE14ADA2476124C08DFBFF1DD2C0C4B94C
<?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>
md5: B3EDED2913E898DD884F9DFFF4F92A74 | sha1: 84E4622137408AD059194660D8F01BDB1C8D0BCB | sha256: 6A665191FF57A57E832DF6A09381F06194FAD1203A8CAC9E46BFA9EF4E327EA6 | sha512: D82FD9F3DD985BC160508C53A6CD05DF4F098CD0D75E7540D3A1314C0C8A5F14AA9EA261DEBBD04C08FAD265273F506B9D41DB443E282F878172C0D62D9E5F26
md5: BE4902548A307184D2CCE3E507DB51B1 | sha1: 8DE02B3D33FCA9D92D017CDBEC42539DE684900D | sha256: B817FFA90DB35A5E33E11E8BCC84589419A07F8EAD1954DA270FE1764CF3E7E8 | sha512: EDDC6F57031151D5A665EA8FA49CD481E137E0EA45204AF752DF18877BE58C419F5CBD1BFB0FAC456F17D2CA968D181FDDDFB60893793E0251F282834F3D673D
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.
- Mono.Cecil.dll (aa16074961db) - ## / 71
- nunit-agent-x86.exe (9c534c99453b) - ## / 71
- nunit-agent.exe (2b336d8371c3) - ## / 70
- nunit.engine.api.dll (01726629283d) - ## / 67
- nunit.engine.dll (44d2817a2be4) - ## / 67
- testcentric-gui.1.0-alpha2.nupkg (4037fd9d6f53) - ## / 61
- nunit.uiexception.dll (c585bd6ca1ab) - ## / 66
- TestCentric.Common.dll (5a87973ee2b0) - ## / 65
- testcentric.exe (29181eb99fcb) - ## / 67
- TestCentric.Gui.Model.dll (6a665191ff57) - ## / 66
- TestCentric.Gui.Runner.dll (b817ffa90db3) - ## / 65
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-gui 1.7.0 | 110 | Saturday, September 28, 2024 | Approved | |
TestCentric Runner for NUnit 1.6.4 | 1059 | 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 |
Copyright (c) 2018 Charlie Poole
This package has no dependencies.
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.