TestCentric 1.3

TestCentric Runner for NUnit 1.3.0 - February 23, 2019

General

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

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

GUI

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

Engine

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

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

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

Issues Resolved

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

TestCentric 1.2

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

GUI

• Inprocess test execution has been deprecated

Experimental GUI

• The GUI font may be changed from the View menu

• One or more files may be added to those open

• Rerun on Change has been implemented

Test Model

Engine

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

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

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

• The RecentFilesService is no longer available.

Issues Resolved

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

TestCentric 1.1

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 1.0.1

This release fixes a critical error discovered in the 1.0..0 release, which affects the loading and running of .nunit or other project types when the project contains multiple test assemblies. Users affected should install this release and others may also install it without affecting current use.

TestCentric 1.0

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 1.0 Beta4

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 1.0 Beta3

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.

Unless something unexpected comes up, this will be the final beta.

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 1.0 Beta2

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 1.0 Beta

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 1.0 Alpha4

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