Downloads:

1,452

Downloads of v 0.6.0:

946

Last Update:

9/22/2017

Package Maintainer(s):

Software Author(s):

  • Charlie Poole

Tags:

nunit gui runner test testing tdd

NUnit 3 GUI Runner

This is not the latest version of NUnit 3 GUI Runner available.

0.6.0 | Updated: 9/22/2017

Downloads:

1,452

Downloads of v 0.6.0:

946

Maintainer(s):

Software Author(s):

  • Charlie Poole

NUnit 3 GUI Runner 0.6.0

This is not the latest version of NUnit 3 GUI Runner available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install NUnit 3 GUI Runner, run the following command from the command line or from PowerShell:

>

To upgrade NUnit 3 GUI Runner, run the following command from the command line or from PowerShell:

>

To uninstall NUnit 3 GUI Runner, 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 nunit-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 nunit-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 nunit-gui installed
  win_chocolatey:
    name: nunit-gui
    state: present
    version: 0.6.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 'nunit-gui' do
  action    :install
  version  '0.6.0'
  source   'STEP 3 URL'
end

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


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

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


cChocoPackageInstaller nunit-gui
{
   Name     = 'nunit-gui'
   Ensure   = 'Present'
   Version  = '0.6.0'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install nunit-gui version="0.6.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 11/1/2019.

Description

This package includes the nunit-gui runner and test engine for version 3 of the NUnit unit-testing framework.


tools\CHANGES.txt
NUnit-Gui 0.6 - September 10, 2017

Issues Resolved

 * 96	Show message of some kind while tests are loading.
 * 189	Move View to a separate Assembly
 * 199	Some compilation problem in tests...
 * 206	Use GitVersion for the GUI builds
 * 209	Utilise IAvailableFrameworks interface over RuntimeFramework class in engine
 * 223	ReportContainsStartAndEndDateAndDuration is dependent on the culture
 * 229	Create separate assembly for the model alone

NUnit-Gui 0.5 - August 12, 2017

Issues Resolved

 * 60	Get extensions working for the GUI
 * 137	Allow changing ProcessModel and DomainUsage
 * 204	Move the GUI repository
 * 205	Create a Chocolatey package for the GUI

NUnit-Gui 0.4 - June 21, 2017

Issues Resolved

 * 14     Display relative path in GUI's tree (option)
 * 26     Explicit tests are executed if a category is excluded
 * 112    Add icons to solution
 * 127    Decide Framework and C# levels for the gui project
 * 130    Corrupted NUNit30Settings file
 * 131    Initial Tree Display setting is not honored
 * 140    Add support for Multiple Asserts
 * 154    Change default to run in a separate process, allowing 32-bit processes to work among other things
 * 155    Cannot drag and drop test assemblies
 * 156    Fix RunTree image for transparency.
 * 163    No validation of tracelevel
 * 164    Missing escaping of content of CDATA in AddXmlCDataSection
 * 170    Test assembly locked
 * 173    Test result message and stacktrace not always updated
 * 176    Upgrade to version 3.6.1 of engine
 * 179    Compiling the project on a machine with only VS 2017
 * 184    The path is not of a legal form exception on load
 * 192    Nuget package for engine doesn't have agent config files

NUnit-Gui 0.3 - January 1, 2017

Issues Resolved

 * 61     When loading tests using an agent, a cmd window is opened
 * 86     Review and Revise Settings Panels
 * 101    Bug Fix when viewing by category
 * 102    Add Extension Manager dialog
 * 117    System.FormatException on parsing duration
 * 122    Update package references to latest versions
 * 123    Create temporary thread to run tests
 * 126    Need an easier way to make Engine changes for the Gui
 * 133    Initial NUnit Tree display should show top of tree
 * 134    File Exit command doesn't work
 * 146    Remove additional unused settings

NUnit-Gui 0.2 - April 12, 2016

Issues Resolved

 * 93 Crash on startup if newer NUnit installation
 * 94 BadImageFormatException loading dlls targeting .NET 4.0 and higher

NUnit-Gui 0.1 - April 8, 2016

General

This is the initial release of the NUnit GUI runner. This is pre-alpha code we are releasing
primarily for the purpose of getting feedback on the user interface itself. It is not suitable
for use in production.

Features

 * The left-hand panel displays the tests in a variety of ways.
   * As a traditional NUnit tree
   * As a list of fixtures
   * As a list of test cases

 * When displaying a list of fixtures or test cases, you may select various groupings. 
   This is similar to how the Visual Studio test explorer window works.

 * The right-hand panel displays information about the individual test selected in the 
   left-hand panel. It has two tabs.
   * Properties - shows the information about the test (upper pane) and it's result (lower pane)
   * XML - shows the XML representation for the test or test result

Issues Resolved

 * 17 Gui should highlight not-runnable and ignored tests immediately upon load
 * 19 CI Server for nunit-gui
 * 32 Load last test on startup
 * 33 Command-line with assemblies and projects specified
 * 34 Command-line run option
 * 35 Command-line noload option
 * 36 Gui Layout
 * 37 File Open Menu Item
 * 38 File Close Menu Item
 * 41 File Reload menu item
 * 44 Select Runtime Menu Item
 * 45 Test List Display
 * 46 Status Bar Content
 * 47 View Status Bar Menu Item
 * 48 Support checkboxes in the gui tree display
 * 49 Recent Files Menu
 * 55 Running tests from the gui
 * 58 Test details
 * 59 Invalid file (non-assembly) is displayed as an assembly.
 * 62 Group headings are not shown with correct icon
 * 66 Remove unsupported options from GuiOptions class
 * 68 Implement XML view of test details
 * 69 Reloading nunit project file causes engine error
 * 72 ReloadProject versus ReloadTests
 * 84 Add context menu to XmlView
 * 85 Display test result info in XmlView
tools\LICENSE.txt
Copyright (c) 2016 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\nunit-agent-x86.exe
md5: 76666990B9E194F495DBB18ED90F0EC4 | sha1: 290B0606940FF217C7E6E40B3637260DC6FF798A | sha256: F96E06C08EDBA966D73ECB8E0AE9A554437C41A34781E3385F270EBDF490BE90 | sha512: 167DEF9C5C806FA670E3978CBB3FEA28823E49F85508CBB46C98AE64762FDDE4E5C9C5155DD4DC697EF87FD7DCA843818C8C1446E110F074D7ECD33E9F2CBE71
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" />

  </runtime>
  
</configuration>
tools\nunit-agent-x86.exe.ignore
 
tools\nunit-agent.exe
md5: BB6ECA28FB632226E3D23C4C61D05D50 | sha1: F5B4D07A07D3FB8D4418EB945A2AC532D7964825 | sha256: 09A53B846FC9C1FBA0BC28643F79F87F868AC68DE5C9E70195307987E24047CF | sha512: 4893B8B55606CB07841579FDD058AE4583EEA26E6A2560EC4D1AC9FE57B482B57D6FB149B86C02C40BF2A4DDE14920D37FC876EF64313E5822E6FEF5C2599E1F
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" />

  </runtime>
  
</configuration>
tools\nunit-agent.exe.ignore
 
tools\nunit-gui.exe
md5: 42801DF6B29A00D59DBFF7C5E47CDA4E | sha1: 136E5C9509184B2340F05195A756F774939386BB | sha256: 43CDD89905738479FF0A5C45DDF514D8FC2C5BDC5B877058BB5B0B31293975A7 | sha512: E714B098110EE69E05E117CBB77E90829DDAF47CCBE99834F8FBEAFD338409AE4AF308DB8DB321657228FF322E9E21D03F4BD4AD66F03F052F602957A47CAEF8
tools\nunit-gui.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\nunit.choco.addins
 
tools\nunit.engine.api.dll
md5: 5C9FF4023E1ED14A0A44A17717B7FF29 | sha1: 4D3AF82137BF6C4007B1F2B3C14095028B29D6BF | sha256: 1E8D5946C80CECFDFC644871ED160F19C8C38E3890CD45A5BB4CAAF2F39D5A03 | sha512: 3E5C935606C3BD491060F77CC38093437DC14F31B96B4D13F5177E998D0CA341A221174BC27AFB7D24C6775600656BC2FCD9A6DE966A50F63000FFD576D5C103
tools\nunit.engine.dll
md5: E1C13F316E321BA08B69750BDA2DAF62 | sha1: 788A37551D1CA61369DBA2FA8C58E662DB70B5E7 | sha256: 9E70F8F8A152F95EF1475CEBAAC622EF66F2DFE7A612791268178EB89AC56A8C | sha512: BFBA2DF39E692334C90004A61277BD6283B62431CE959B51A5BD9C0559476316A57D88CBDADD9862170CCA102006B0119BB84E724197C5B9404D4AC14A4AD555
tools\nunit.testmodel.dll
md5: F0060E89747A7C3E96CF9D9EC68C1758 | sha1: 5BD530DCBCC3DFDEC3FB61016B1C928F4048093F | sha256: 2F06BFF66BBEEE7434F43CF94E25A84AF3C10B8221E44405F5E340766E83B0CD | sha512: 61F218EEC789A274504CBE459B720C0DC6A7810F673E91F92C1EDA4ABD697AE75B14C356767023566B285472BB7D3BF99F2264624834253E753BC21CCEFCEBE0
tools\nunit.uikit.dll
md5: C690288FA034EBA1413A2E0732920639 | sha1: 993DCA9FFD5857BE79EDD6546386B77D4486B617 | sha256: 241285660AAF3E99482016204B009F38F6E0B73C29DD9F3E8DF185D8F3546A74 | sha512: 307AF93D25B06C3B9E348FD5A22CC6F0E838B653787ED59482DA5DD958352CE0C6FD4AFB9052FF87E6A93E1F9DE3C9B1312B71B3DF6E686EB9653CD161FF625B
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/NUnitSoftware/nunit-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
NUnit 3 GUI Runner 0.6.0 946 Friday, September 22, 2017 Approved
NUnit 3 GUI Runner 0.5 221 Thursday, August 24, 2017 Approved
NUnit 3 GUI Runner 0.4 255 Thursday, July 6, 2017 Approved

This package has no dependencies.

Discussion for the NUnit 3 GUI Runner Package

Ground Rules:

  • This discussion is only about NUnit 3 GUI Runner and the NUnit 3 GUI Runner 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 NUnit 3 GUI Runner, 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