| Version Info | Change Log |
Version 1.5.0.0
Released: 14 May 2008 |
- Upgraded HarnessIt.exe and associated assemblies to support testing projects built with .NET 2.0 to .NET 3.5.
-
Added the ITest interface as an alternate (and prefered) style of testing. Test methods can now be defined as
public void Method(ITest it) { }
The ITest interface supports more natural language test expressions such as:
it.Is.NotNull(myString) and
it.Are.Equal(age, 27).
The older style public void Method(TestMethodRecord tmr) { } methods are still supported.
- Significant improvement in test execution speed - especially for large test sets.
|
| Version Info | Change Log |
Version 1.4.0.3
Released: 16 March 2004 |
- Addressed an issue that could cause HarnessIt to display a confirmation dialog requiring user interaction during an automated build process.
|
| Version Info | Change Log |
Version 1.4.0.2
Released: 14 Jan 2004 |
- IMPORTANT: HarnessIt is now configured to use version 1.1 of the .NET Framework by default. If you wish to alter which runtime version HarnessIt uses, please run the corresponding configuration tool by selecting it from the Configuration Tools menu under the HarnessIt Start menu item. Note: If you only have version 1.0 of the .NET Framework installed, then you must execute the Run on .NET 1.0 Framework configurator in order for HarnessIt to start.
- Improved detection of project file changes.
- Updated the tip regarding forcing HarnessIt to use a specific version of the .NET Framework to cover the addition of the new configuration tools.
|
| Version Info | Change Log |
Version 1.4.0.1
Released: 29 Aug 2003 |
|
| Version Info | Change Log |
Version 1.4.0.0
Released: 14 July 2003 |
- IMPORTANT: The testing framework has been changed. Be sure to recompile any test projects which contain a copy of the UnitedBinary.UnitTests.Framework.TestBasis assembly having a version number less than 1.4.0.0. Only a recompile is necessary; no code changes are required.
- Support for testing multithreaded classes has been improved. HarnessIt now catches exceptions from all threads owned by the testing process. See Appendix B: Multithreaded Testing Considerations for more details.
- Added a new sample which shows how to test multithreaded objects. It is located in the MultiThreadedTest directory in the distribution's Samples directory.
- Updated the Exception Explorer to display the exception's associated thread ID and thread name.
- Added a document detailing the advantages of choosing HarnessIt over NUnit.
- Added a tip about integrating HarnessIt with NAnt.
|
| Version Info | Change Log |
Version 1.3.0.0
Released: 19 May 2003 |
- Added the ability to save test results in XML format. Please see the fully-commented XML Report Sample included in the HarnessIt distribution Samples directory to review the format of the XML output. An XML report may either be saved from HarnessIt's File menu after the tests are executed, or an XML log file can be emitted automatically after test execution by using the appropriate command line option (see the Command Line Reference).
- HarnessIt now features an output pane history. Press Ctrl+B and Ctrl+Shift+B to cycle back and forth, respectively, between the output panes you have visited (or use your fourth and fifth mouse buttons if you own an Intellimouse Explorer).
- Documented the necessary requirements introduced in .NET 1.1 by Microsoft for testing unmanaged C++ code from managed C++. Please read the warning at the bottom of the Testing Unmanaged C++ page for more information.
- Increased the amount of data displayed in the Report Explorer when clicking on methods, classes, and assemblies in the HarnessIt's ClassView.
- Improved the look-and-feel of the Exception Explorer.
- Increased text rendering speed for all output windows.
|
| Version Info | Change Log |
Version 1.2.1.0
Released: 28 Mar 2003 |
- IMPORTANT: The testing framework is now serializable. In order for HarnessIt to load any unit test assemblies created with a prior version of HarnessIt, you will need to recompile your test assemblies. Only a recompile is necessary; no code changes are required.
- IMPORTANT: The Web Context Service error handling has been improved. Please upgrade your Web Context Service installations to the latest version.
- Improved detection of out-of-date test basis assemblies.
- Added a tip on how to share data between tests that are in different classes or assemblies.
- Fixed a problem with the registration reminder form. When attempting to register HarnessIt from the reminder form, the reminder form would remain topmost, and the registration form would be partially obscured beneath the reminder form.
|
| Version Info | Change Log |
Version 1.2.0.0
Released: 14 Feb 2003 |
- IMPORTANT: The testing framework has been changed. In order for HarnessIt to load any unit test assemblies created with a prior version of HarnessIt, you must recompile your test assemblies. Only a recompile is necessary; no code changes are required.
- IMPORTANT: The beta cycles for the Web Test Engine and the Remote Test Engine have concluded. Be sure to revisit the Web Test Engine and Remote Test Engine documentation as many new enhancements have been added since the last beta version. All beta versions of the Web Test Engine and Remote Test Engine will expire on 01 Apr 2003.
- IMPORTANT: If you are using the beta version of the Web Context Service, the web service that the Web Test Engine connects to, you will need to update the beta Web Context Service to the latest version. The latest Web Test Engine is incompatible with all previous beta versions of the Web Context Service.
- The testing framework has been extended with many new features including additional convenience overloads on attribute constructors and a completely new
TestRequired attribute. Please see the Framework Reference for more information.
- Three new command line arguments have been provided to help you automate tests using the Web Test Engine. The new options are
user, pass, and the optional domain. Please see the HarnessIt Command Line Reference for specific examples.
- Improved and beautified the testing framework documentation.
- Added an execution log for HarnessIt when it is run as a scheduled task. HarnessIt will append any errors it encounters to this file during each non-interactive run. The file will be located in the directory that HarnessIt is started in and will be named execution.log.
- The Web Context Service can now be directly integrated with your existing web applications. This markedly reduces the complexity of installing the service and increases the ability to test elements that are location dependent (such as using custom configuration handlers or testing the reading of files relative to your web application's root). This "integrated" configuration is now considered to be the default way of deploying the WCS.
- The Web Context Service and Remote Engine Host now make use of custom configuration section handlers.
- The Web Test Engine and Remote Test Engine now return complete exception information. These exceptions will now be visible on HarnessIt's Exception Explorer tab.
- The Web Test Engine and Remote Test Engine now return tracing and debug information. This output will now be visible on HarnessIt's Trace tab.
- HarnessIt would fail when executed as a scheduled task on Window 2000 Server. This problem was corrected.
- If a user attempted to connect to a Remote Engine Host using the Remote Test Engine and an error occurred, it was possible that HarnessIt would not be able to attempt subsequent connections to the Remote Engine Host until HarnessIt was restarted. This issue was fixed in this release.
- Corrected a problem where old test results were not cleared whenever a test engine failed to initialize.
- If an exception were thrown from an assembly that contained a space in its file name, the Exception Explorer would fail to display the exception information properly. This problem was corrected.
|
| Version Info | Change Log |
Version 1.1.3.2
Released: 19 Dec 2002 |
- Altered some routines that were generating superfluous internal exceptions. This should make HarnessIt less "noisy" when Visual Studio is configured to break when any exceptions are thrown.
- Added two new tips regarding testing using a custom configuration section handler and configuring Visual Studio exception behavior.
- Minor documentation improvements.
|
| Version Info | Change Log |
Version 1.1.3.1
Released: 20 Nov 2002 |
-
Fixed a globalization issue regarding date handling within the registration code system.
|
| Version Info | Change Log |
Version 1.1.3.0
Released: 18 Nov 2002 |
-
IMPORTANT: Our licensing system has changed. Current owners of HarnessIt
will receive new registration codes via email.
-
Added an Exception Explorer that allows for the viewing of detailed exception data.
-
HarnessIt now returns program exit codes to indicate whether all tests were
completed successfully, some tests were completed successfully, or if HarnessIt encountered an error.
This should greatly aid those who are automating HarnessIt from the command line.
-
Added a brief summary of the test results to the end of the Output window. Previously this information was only
available from the Report Explorer window.
-
Changed the values for the
close command line argument. The values are now always,
success, and never. The previous values will still work for backward compatibility.
-
HarnessIt now ignores the
close command line option if the user presses the Stop
button during testing.
-
Fixed a bug where the Class View checkboxes could become inconsistent if a new test method was
added to a disabled (unchecked) class.
-
Added many additional Tips and Tricks to the documentation.
-
Updated the Web Test Engine to version 0.9.1.3.
-
Updated the Remote Test Engine to version 0.9.0.1.
-
Many internal changes and refinements.
|
| Version Info | Change Log |
Version 1.1.0.3
Released: 24 Sep 2002 |
-
Added the initial beta release of the
Remote Test Engine.
-
Updated the Web Test Engine to version 0.9.1.2.
Only minor refinements, however the previous version is incompatible with the latest release of HarnessIt. This means that you
must reinstall the Web Test Engine web service.
-
Added Visual Studio.NET add-in which automates insertion of common code blocks
used in the Unit Test Framework.
-
Added "Failures Only" window. Now HarnessIt displays the test results which
have failed separately as well as intermixed in the Output window.
-
Added "Trace" window. Now HarnessIt displays the trace/debug messages from your
unit tests.
-
Added automatic scrolling to real-time output windows such as Output window.
-
Added a "Tips and Tricks" section to the help files with step by step help for common HarnessIt issues.
-
Added command line argument "close on success" which closes HarnessIt if and only if all tests succeed.
-
Added automatic log cycling to the command line
options. Now HarnessIt can avoid overwriting log files, especially
in scripted situations.
-
Added time, date, and version tag to saved test reports. Now the test report
contains the time and date it was run and the HarnessIt version that ran the
tests.
-
Added performance (timing) information to the output window. Now each test
assembly, test class, and test method report their running time.
-
Added a splash screen.
-
Fixed Reuse mode classes are used across test runs. There was a bug where Reuse
mode classes reused over and over as long as HarnessIt was running. Now each
test run uses a new instance as it should. Note one test run corresponds
to one F5 key press.
-
Fixed
loading test assemblies from a network drive fails to detect test classes and
methods in valid test assembly.
-
Fixed project containing a network linked assembly fails to load completely
(network assemblies were not loaded).
-
Fixed saving empty project fails to retain non-default execution engine
settings.
-
Fixed unhandled exception when loading older project files from the "Load
Project" menu command.
-
Fixed an issue where the test index reported in output window is incorrect when
using comments (
TestMethodRecord.WriteLine).
-
Fixed project name not updated in Report Explorer when saving an open project
with a different name (save as).
-
Fixed project config file may become temporarily disassociated from
project file when saving test reports from HarnessIt menu.
-
Fixed output window flickers excessively when running tests.
-
Fixed (improved) report explorer is slow for large test sets. Reports are
now generated quicker, approximately 2.5 times quicker for large test sets.
-
Changed documentation, a major overhaul.
-
Changed test report (RTF file) content to include information from the new
Trace and Failures windows.
-
Changed Running Tests dialog does not show up in task bar when running in
command line / vs.net integrated mode.
-
Changed error messages concerning loading projects to report the problem more clearly.
-
Changed the project config file format (an auto-generated file for user level
settings). This should be nearly transparent to you as a user.
-
Many internal modifications.
|
| Version Info | Change Log |
Version 1.0.1.2
Released: 23 Jul 2002 |
-
Added beta 1 version of the Web Test Engine. See the Web Test Engine Overview for details.
|
| Version Info | Change Log |
Version 1.0.1.2
Released: 05 Jul 2002 |
-
Fixed bug when loading project with no path information from the
command line (e.g. /proj=TestProject.htp).
-
Fixed bug where project assemblies are not localized when loading the project
from the command line. This affects only limited types of test
classes.
-
Fixed abnormal "Running Tests" form size when running tests on a machine that
has never had HarnessIt installed. Note that this will not override the
settings put in there by previous versions. Just size that form to your liking
and HarnessIt will remember it.
-
Added better error reporting. Now HarnessIt uses a custom error form which lets
you scroll long error messages and copy the error text.
-
Many internal changes.
|
| Version Info | Change Log |
Version 1.0.1.1
Released: 31 May 2002 |
- IMPORTANT: Changed the way HarnessIt
executes the test methods. Now, HarnessIt supports two different modes of
execution: Renew and Reuse. Renew is
identical to how HarnessIt has worked in the past, where HarnessIt creates
a new class instance for every test method called. The new Reuse
mode forces HarnessIt to create only one instance of the
test class and reuse that instance for all tests in a given run.
See the
TestExecutionMode attribute and Setup/Teardown sections of the help for
details.
-
IMPORTANT: HarnessIt now supports
Setup/Teardown functionality. This is a direct consequence of
the Reuse mode discussed above. See the
TestExecutionMode attribute
and Setup/Teardown sections of the help for details.
-
HarnessIt now supports multiple test execution engines. Presently, there
is only one test engine available (which is the same one that HarnessIt
has used from the outset). However, new engines will soon be available that
support a wide range of functionality. In addition to the standard and optional
testing engines provided by United Binary, users will be able to build their
own custom testing engines to suit their individual needs.
-
Improved error reporting for assembly conflicts in the AssemblyTemp directory.
-
Removed support for the older *.tsp project file types.
-
Added test method function signature checking. Now, HarnessIt will explicitly
report methods marked as TestMethods having the wrong function signature as
errors during test runtime.
|
| Version Info | Change Log |
Version 1.0
Released: 22 May 2002 |
-
Redesigned the the GUI to be more "crisp" and more usable. In
particular, the width of the window panes can be adjusted and is
persistent.
-
Added licensing / activation system to HarnessIt to manage your
license(s).
-
The Recent Projects menu now removes links to missing / removed
project files.
-
Added a strong name to HarnessIt.exe. This can be used to validate
the EXE if necessary.
-
Added copy functionality to the report windows.
-
Many internal changes and refinements.
|
| Version Info | Change Log |
Version ß3d
Released: 01 Apr 2002 |
-
Changed the way HarnessIt internally works with Assemblies slighly in order to
solve certain FileNotFound exceptions. Specifically, resolves exceptions
with operations involving PInvoke, Serialization, Remoting, Microsoft
ObjectSpace, and all operations that use these operations involving custom
assemblies.
|
| Version Info | Change Log |
Version ß3c
Released: 04 Mar 2002 |
-
TestMethodRecord now has a WriteLine(string text) method. This
lets you add comments to the test logfile and output window.
-
Added a Framework Programming Guide which gives detailed
documentation of the Unit Test Framework classes.
-
HarnessIt now supresses non-test assemblies, classes, and
methods in the ClassView window.
-
HarnessIt tracks changes to your Test Project and asks you to save
the changes when closing a modified project and quits bugging you when your
project is not modified.
-
The install now adds the Test Basis DLL to Visual Studio.NET's "Add
References" dialog so you don't need to browse for the reference any more.
-
Minor internal changes to improve test execution and reporting performance.
|
| Version Info | Change Log |
Version ß3b
Released: 21 Feb 2002 |
-
Added a strong name to the test basis DLL. This is required
for using the test basis DLL in the GAC and for using it in certain strongly
named projects.
-
Fixed bug where certain types of signaled exceptions were
misidentified as inconsistent. Now TestMethodRecord.RegisterException(string,
type) works the way you would expected to.
-
Fixed bug where certain types of classes are *very* slow loading
projects and assemblies. Should be about 300 times faster loading very
large projects.
-
Added more details to the running tests form. Now you get more
details while the tests are executing.
-
Fixed some minor spelling errors in reports.
|
| Version Info | Change Log |
Version ß3a
Released: 04 Feb 2002 |
-
Added the TestOrder attribute to allow for optional ordering of unit
tests on all levels. You can order assemblies, classes, and methods using
this attribute. See the documentation for details.
-
Added the TestAssembly attribute. This optional attribute
functions the same as TestClass in that it lets you specify a description for
your assembly which will be incorporated HarnessIt outputs.
-
Updated "Running Tests" form to report test results while the tests
are executing.
-
Changed the "Save Project" menu behavior and added a "Save Project
As" menu item.
-
Fixed some minor spelling errors.
-
Moved to Beta 3. While HarnessIt is not yet feature complete,
it is nearly feature complete and its new designation is meant to convey this.
|
| Version Info | Change Log |
Version ß2e
Released: 28 Jan 2002 |
-
Updated Beta expiration method to allow expired versions of older betas to not
expire the current version(s).
|
| Version Info | Change Log |
Version ß2d
Released: 25 Jan 2002 |
-
Updated common controls to use Windows XP style controls on Windows XP systems.
-
Other minor refinements.
|
| Version Info | Change Log |
Version ß2c
Released: 16 Jan 2002 |
-
Beta 2c runs on Microsoft.NET Final Release.
|
| Version Info | Change Log |
Version ß2b
Released: 13 Jan 2002 |
-
Moved expiration date to April, 2002.
-
Improved TestMethodRecord.RegisterException() to support signaling of particular
exception types. For example, you can signal ArgumentNullException and get an
error for any other type.
-
Added Recent Projects menu to the File menu.
-
Changed file extension on project configuration file to .HarnessItConfig. This
file is auto-generated to keep track of which tests are enabled and which are
disabled.
-
Fixed some minor formatting issues in reports.
-
Fixed bug for using /proj=projectfile as the ONLY command line argument.
-
Fixed bug loading projects using relative paths (e.g. /proj=..\..\My
Project.htp, failed under certain conditions).
-
Other minor refinements.
|
| Version Info | Change Log |
Version ß2a
Released: 13 Jan 2002 |
-
Improved the real-time feedback. Now the ClassView is updated while the
tests are executing. This lets you visually see which tests are passing
and which are failing. You don't have to wait until all the test run to see the
results.
-
Added better Windows shell integration. Now the project files are "known
types" and double clicking them will load them into HarnessIt.
|
| Version Info | Change Log |
Version ß1g
Released: 18 Dec 2001 |
-
Added "memory" to the class view tree. Now the tests remember their
enabled or disabled state from session to session. This allows you to focus
more easily on a small group of unit tests.
-
Fixed problem saving project when that project is loaded. HarnessIt was holding
the file open which blocked itself from saving the project when it was loaded.
-
Fixed problem loading assemblies with no classes whatsoever. This
previously caused a series of exceptions to be thrown.
-
Added hot keys for many of the menu items.
-
Added a few more confirmation checks on actions like closing the open projects.
-
Changed test project file extention from .tsp to htp. The tsp files can still
be loaded, but you must pull down the file filter to find them in the open
project dialog box.
-
Changed how the Class View tree expands the nodes. Now it shows the
assemblies and classes by default. It previously just showed the classes.
-
Changed how the methods of the classes in the Class View are shown. Now
all the methods inherited from System.Object are not shown because they only
add clutter to the list of methods.
-
Added the ability to cancel the unit tests while they are running and improved
the multithreading behavior during the test execution.
|
| Version Info | Change Log |
Version ß1f
Released: 04 Dec 2001 |
-
Fixed critical "Beta Copy Expired" when installing HarnessIt on a fresh OS
(HarnessIt hasn't been installed before).
-
Added improved exception handling to the unit testing framework (See
TestMethodRecord.SignalExeption()).
|
| Version Info | Change Log |
Version ß1e
Released: 03 Dec 2001 |
-
Fixed problem with test progress progress bar. Now the
progress bar should move smoothly as the tests run, not blocky and jumpy as
before.
-
Added a Visual Basic.NET sample unit test project. We converted the
C# RMatrix sample to VB.NET.
|
| Version Info | Change Log |
Version ß1d
Released: 30 Oct 2001 |
-
Renamed the test attribute
UBTestClass to TestClass
and UBTestMethod to TestMethod.
-
Fixed error where saving a project would not change the name in the title
bar.
|
| Version Info | Change Log |
Version ß1c
Released: 25 Oct 2001 |
-
Beta 1c runs on Microsoft.NET Release Candidate 1.
-
Fixed a problem resolving file names in projects under certain conditions.
|
| Version Info | Change Log |
Version ß1b
Released: 24 Oct 2001 |
-
Added validation for command line arguments. Previously HarnessIt had
ignored incorrect arguments. Now it notifies the user and attempts to
help them resolve the issue.
-
The readme file now shows up as a solution item when HarnessIt is installed to
the non-default location. Previously it just vanished.
-
Error checking was added during assembly loading. Now the user gets a
nicer, more explanatory message when errors occur.
-
Project files now use relative path names so it is more likely that the project
file will remain valid when moving projects around.
-
Added extended version information in the help about box. In future versions,
this will become useful when checking for updates.
-
Updated the sample unit test project to require less tweaking when installing
to non-default locations.
-
Other minor internal changes.
|
| Version Info | Change Log |
Version ß1a
Released: 14 Oct 2001 |
-
Initial beta release. No changes.
|