http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/runningTests.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/runningTests.html b/lib/NUnit.org/NUnit/2.5.9/doc/runningTests.html deleted file mode 100644 index 1982cad..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/runningTests.html +++ /dev/null @@ -1,108 +0,0 @@ - - - - -NUnit - RunningTests - - - - - - - - - - - - - -
- -

Running Tests

- -

Nunit provides three different runners, which may be used to load and -run your tests. - -

- -

NUnit Agent

- -

When running tests in a separate process, the console and gui runners - make use of the nunit-agent program, nunit-agent.exe. Although not directly run by users, nunit-agent - does load and execute tests and users need to be aware of it, especially - when debugging is involved. - -

Third-Party Runners

- -

Various third-party applications are available for loading and running - NUnit tests. Some of these actually use NUnit to load the tests, while - others provide their own emulation and may not work in the same way - that NUnit does. - -

Because the status of such projects may change from time to time, we don't - discuss them individually here. For the latest information, consult the - manufacturer of any third-party software or ask other users on our - discussion list. - -

Additional Information

- -

For additional general information on how tests are loaded and run, see - -

- -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/runtimeSelection.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/runtimeSelection.html b/lib/NUnit.org/NUnit/2.5.9/doc/runtimeSelection.html deleted file mode 100644 index 95a8a98..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/runtimeSelection.html +++ /dev/null @@ -1,121 +0,0 @@ - - - - -NUnit - RuntimeSelection - - - - - - - - - - - - - -
- -

Runtime Selection

- -

Before loading an assembly, NUnit must determine what runtime to use. By default -(see below for exceptions) the following rules are used: - -

    -
  1. If the assembly was built for the same runtime under which NUnit is currently -running, then that runtime is used. - -

  2. If the assembly was built for a different runtime version and that version -is available, NUnit uses it, running out of process if necessary. - -

  3. If the assembly was built for a different runtime version, which is not -available, then the result depends on whether the build version is earlier or -later than the current version. If earlier, the test will be run using the -same runtime version under which NUnit is running. If later, then it is not -possible to load the test and NUnit gives an error message. - -

  4. If multiple assemblies are being run at the same time, NUnit first -determines the runtime under which each assembly was built. The highest version -is then selected for the entire group, and rules 1 through 3 are applied. -

- -

Note: For versions 2.5.4 and 2.5.5, automatic runtime selection only -works in the Gui runner. Use the /framework option to select the appropriate -runtime under the Console runner. - -

Overriding the Defaults

- -

The default runtime framework may be overridden using command line arguments, - menu items in the Gui or settings in an NUnit project file. Provided that the - requested framework is available, it will be used. If it isn't available, - NUnit will issue an error message. - -

Note: To use version 1.x runtimes, you must have NUnit's support - for those runtimes installed, in addition to the runtime itself. This - support is an option of the NUnit installation. - -

Command Line Options

- -

The /framework option of console runner allows you to specify - the framework type and version to be used for a test run. See - NUnit-Console Command Line Options for more information. - -

Gui Menu Selection

- -

The main menu provides File | Select Runtime sub-items allowing you - to reload the tests under a specific runtime. See - Main Menu for more info. - -

Project Settings

- -

The NUnit project format supports specification of a specific runtime to - be used with a project at the configuration level. See - Project Editor for more information. -

- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/sameasConstraint.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/sameasConstraint.html b/lib/NUnit.org/NUnit/2.5.9/doc/sameasConstraint.html deleted file mode 100644 index 6eed701..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/sameasConstraint.html +++ /dev/null @@ -1,100 +0,0 @@ - - - - -NUnit - SameasConstraint - - - - - - - - - - - - - -
- -

Same As Constraint (NUnit 2.4)

- -

A SameAsConstraint is used to test whether the object passed - as an actual value has the same identity as the object supplied - in its constructor. - -

Constructor

- -
-SameAsConstraint( object expected )
-
- -

Syntax

- -
-Is.SameAs( object expected )
-
- -

Examples of Use

- -
-Exception ex1 = new Exception();
-Exception ex2 = ex1;
-Assert.That( ex2, Is.SameAs( ex1 ) );
-
-Exception ex3 = new Exception();
-Assert.That( ex3, Is.Not.SameAs( ex1 ) );
-
-
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/samples.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/samples.html b/lib/NUnit.org/NUnit/2.5.9/doc/samples.html deleted file mode 100644 index 24e3aa9..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/samples.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - -NUnit - Samples - - - - - - - - - - - - - -
- - -

Samples

- -NUnit 2.5 samples continue to be organized by language, with an additional -folder for Extensibility examples. The 'money-port' example has been -removed. - -

C# Samples

-
-
Failures -
This sample written in C# demonstrates 4 failing unit tests and one test - that is not run. -
Money -
This is a C# version of the money example which is found in most xUnit - implementations. Thanks to Kent Beck. -
- -

J# Samples

-
-
Failures -
This has three failing tests and one ignored test written in J#. -
- -

VB.NET Samples

-
-
Failures -
This sample written in VB.NET demonstrates 4 failing unit tests and - one test that is not run. -
Money -
This is a VB.NET version of the money example which is found in most xUnit - implementations. Thanks to Kent Beck. -
- -

Managed C++ Samples

-
-
Failures -
This is the same example as the others with four failing unit - tests and one ignored test. NOTE:  The results are as expected when - compiled in Debug mode. In Release mode the divide by zero test succeeds. -
- -

C++/CLI Samples

-
-
Failures -
This is the same example as the others with four failing unit - tests and one ignored test. -
- -

Extensibility Examples

-
-
Minimal -
The smallest possible Addin: it does nothing but is - recognized by NUnit and listed in the Addins dialog. -
SampleSuiteExtension -
A "toy" SuiteBuilder. It recognizes a special attribute - and identifies tests right in the suite extension. This example - uses separate objects for the addin and the suite builder. -
SampleFixtureExtension -
A slightly more involved SuiteBuilder. It recognizes - a special attribute and registers a test case builder to - identify its tests. It inherits from NUnitTestFixture and - so gets all the features of that class as well for free. - This example uses the same object to implement both the - addin and the suite builder. -
- -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/sequential.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/sequential.html b/lib/NUnit.org/NUnit/2.5.9/doc/sequential.html deleted file mode 100644 index 9a322dc..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/sequential.html +++ /dev/null @@ -1,127 +0,0 @@ - - - - -NUnit - Sequential - - - - - - - - - - - - - -
- -

SequentialAttribute (NUnit 2.5)

- -

The SequentialAttribute is used on a test to specify that NUnit should - generate test cases by selecting individual data items provided - for the parameters of the test, without generating additional - combinations. - -

Note: If parameter data is provided by multiple attributes, -the order in which NUnit uses the data items is not guaranteed. However, -it can be expected to remain constant for a given runtime and operating -system. - -

Example

- -

The following test will be executed three times, as follows: -

-	MyTest(1, "A")
-	MyTest(2, "B")
-	MyTest(3, null)
-
-
-[Test, Sequential]
-public void MyTest(
-    [Values(1,2,3)] int x,
-    [Values("A","B")] string s)
-{
-    ...
-}
-
- -

See also...

- - -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/setCulture.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/setCulture.html b/lib/NUnit.org/NUnit/2.5.9/doc/setCulture.html deleted file mode 100644 index b09a3e8..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/setCulture.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - -NUnit - SetCulture - - - - - - - - - - - - - -
- - - - - -

SetCultureAttribute (NUnit 2.4.2)

-

The SetCulture attribute is used to set the current Culture for the duration -of a test. It may be specified at the level of a test or a fixture. The culture -remains set until the test or fixture completes and is then reset to its original -value. If you wish to use the current culture setting to decide whether to run -a test, use the Culture attribute instead of this one.

- -

Only one culture may be specified. Running a test under -multiple cultures is a planned future enhancement. At this time, you can -achieve the same result by factoring out your test code into a private method -that is called by each individual test method.

- -

Examples:

- -
- -
- Language Filter - -
- -
namespace NUnit.Tests
-{
-  using System;
-  using NUnit.Framework;
-
-  [TestFixture]
-  [SetCulture("fr-FR")]
-  public class FrenchCultureTests
-  {
-    // ...
-  }
-}
-
- -
Imports System
-Imports Nunit.Framework
-
-Namespace Nunit.Tests
-
-  <TestFixture(), SetCulture("fr-FR")>
-  Public Class FrenchCultureTests
-    ' ...
-  End Class
-End Namespace
-
- -
#using <Nunit.Framework.dll>
-using namespace System;
-using namespace NUnit::Framework;
-
-namespace NUnitTests
-{
-  [TestFixture]
-  [SetCulture("fr-FR")]
-  public __gc class FrenchCultureTests
-  {
-    // ...
-  };
-}
-
-#include "cppsample.h"
-
-namespace NUnitTests {
-  // ...
-}
-
- -
package NUnit.Tests;
-
-import System.*;
-import NUnit.Framework.TestFixture;
-
-
-/** @attribute NUnit.Framework.TestFixture() */
-/** @attribute NUnit.Framework.SetCulture("fr-FR") */
-public class FrenchCultureTests
-{
-  // ...
-}
-
-
- -

See also...

- - -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/setUICulture.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/setUICulture.html b/lib/NUnit.org/NUnit/2.5.9/doc/setUICulture.html deleted file mode 100644 index 87edb20..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/setUICulture.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - -NUnit - SetUICulture - - - - - - - - - - - - - -
- - - - - -

SetUICultureAttribute (NUnit 2.5.2)

-

The SetUICulture attribute is used to set the current UI Culture for the duration -of a test. It may be specified at the level of a test or a fixture. The UI culture -remains set until the test or fixture completes and is then reset to its original -value. If you wish to use the current culture setting to decide whether to run -a test, use the Culture attribute instead of this one.

- -

Only one culture may be specified. Running a test under -multiple cultures is a planned future enhancement. At this time, you can -achieve the same result by factoring out your test code into a private method -that is called by each individual test method.

- -

Examples:

- -
- -
- Language Filter - -
- -
namespace NUnit.Tests
-{
-  using System;
-  using NUnit.Framework;
-
-  [TestFixture]
-  [SetUICulture("fr-FR")]
-  public class FrenchCultureTests
-  {
-    // ...
-  }
-}
-
- -
Imports System
-Imports Nunit.Framework
-
-Namespace Nunit.Tests
-
-  <TestFixture(), SetUICulture("fr-FR")>
-  Public Class FrenchCultureTests
-    ' ...
-  End Class
-End Namespace
-
- -
#using <Nunit.Framework.dll>
-using namespace System;
-using namespace NUnit::Framework;
-
-namespace NUnitTests
-{
-  [TestFixture]
-  [SetUICulture("fr-FR")]
-  public __gc class FrenchCultureTests
-  {
-    // ...
-  };
-}
-
-#include "cppsample.h"
-
-namespace NUnitTests {
-  // ...
-}
-
- -
package NUnit.Tests;
-
-import System.*;
-import NUnit.Framework.TestFixture;
-
-
-/** @attribute NUnit.Framework.TestFixture() */
-/** @attribute NUnit.Framework.SetUICulture("fr-FR") */
-public class FrenchCultureTests
-{
-  // ...
-}
-
-
- -

See also...

- - -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/settingsDialog.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/settingsDialog.html b/lib/NUnit.org/NUnit/2.5.9/doc/settingsDialog.html deleted file mode 100644 index 75369ee..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/settingsDialog.html +++ /dev/null @@ -1,320 +0,0 @@ - - - - -NUnit - SettingsDialog - - - - - - - - - - - - - -
- -

Settings Dialog

- -

The Settings Dialog is displayed using the Tools | Settings menu item and allows the user to -control some aspects of NUnit�s operation. Beginning with NUnit 2.4.4, a tree-based dialog -replaced the older tabbed format.

- -

Gui Settings - General


- -
-
- -

Gui Display

- -

Full Gui

-

Displays the complete gui - as in prior versions of NUnit. This includes the - test result tabs and the progress bar.

- -

Mini Gui

-

Switches the display to the mini-gui, which consists of the tree display - only.

-

Recent Files

- -

The Display ... files in list TextBox allows the user to choose the number -of entries to display in the recent files list. - -

Normally, NUnit checks that project files still exist before -displaying them in the recent files list. This can cause long delays if the -file is on a network connection that is no longer available. Unchecking -Check that files exist before listing will avoid this delay, so -long as the missing file is not actually selected. - -

If Load most recent project at startup is checked, the GUI will load the -last file opened unless it is run with a specific filename or with the -/noload parameter.

- -

Gui Settings - Tree Display


- -
-
- -

Tree View

- -

The list box allows selecting the degree of expansion of the tree when tests are loaded:

-
-

Auto � selects a setting based on the space available for the tree display.

-

Expand � expands all tests

-

Collapse � collapses all tests

-

Hide Tests � expands all suites except for the fixtures themselves.

-
- -

If Clear results when reloading is checked, an automatic or manual reload will reinitialize all -test nodes in the tree (grey display) � if it is not checked, result information for tests that do -not seem to have changed will be retained.

- -

If Save visual state of each project is checked, NUnit saves the state of the tree -and restores it when the project is next opened. The information saved includes which -branches of the tree are expanded, the selected node, any checked nodes and any -category selection. - -

If Show Checkboxes is checked, the tree includes checkboxes, which may - be used to select multiple tests for running. This setting is also available - in the View | Tree menu.

- -

Test Structure

- -

If Automatic Namespace suites is selected, tests will be - shown in a hierarchical listing based on namespaces. This is the - standard display as used in versions prior to NUnit 2.4. - -

If Flat list of TestFixtures is selected, tests will be - shown as a sequential list of fixtures. - -


Gui Settings - Test Results


- -
-
- -

Errors Tab

- -

Check Display Errors and Failures Tab to display the -Errors and Failures tab, which shows information about failing tests. - -

Check Enable Failure ToolTips to display the tip window over the -Errors and Failures display and the stack trace. Clear it if you prefer not -to see the tip window.

- -

Check Enable Word Wrap to turn on word wrapping -in the Errors and Failures display. While you can select this item and the -preceding one at the same time, they do not interact well, so you will -normally choose one or the other.

- -

Not Run Tab

- -

Check Display Tests Not Run Tab to display the -Tests Not Run tab, which shows information about tests that were -skipped or ignored. - -


Gui Settings - Text Output


- -
-
- -

Select Tab

- -

The Select Tab dropdown list is used to select one of the output tabs, for which -settings are to be viewed or changed. It also contains entries that allow -you to add a new tab or edit the list of tabs. - -

The Restore Defaults button is used to restore the default -setting, which is a single tab labeled "Text Output." The default tab -displays all types of output and includes a label for each test that -displays text. - -

The Title text box is used to modify the title displayed -for the selected output tab. - -

Enabled is checked by default. If you uncheck it, -the selected tab will be removed from the tab control. This allows you to temporarily -suppress output to a tab without actually removing its definition. - -

Content

- -

The four check boxes enable or disable a particular type of output -on the selected output window. For each type, the display captures -output produced while your test is running - either by the test -itself or by the program you are testing. - -

Standard Output

-

Captures all output written to Console.Out. - -

Error Output

-

Captures all output written to Console.Error. - -

Trace Output

-

Captures all output written to Trace or Debug. - -

Log Output

-

Captures output written to a log4net log. NUnit captures -all output at the Error level or above unless another level -is specified for the DefaultLogThreshold setting in the -configuration file for the test assembly or project. - -

Test Labels

- -

Check Display TestCase Labels to precede text in the output window -with the name of the test that produced it.

- -

Check Suppress label if no output is displayed to eliminate display -of labels for tests that produce no output in the window. - - -


Test Loader Settings - Assembly Isolation


- -
-
- -

Default Process Model

- -

These settings determine NUnit's default use of operating system -processes and may be overridden by settings in the NUnit project. - -

If Run tests directly in the NUnit process is selected, -all tests are run in a test domain in the same process as NUnit. -This is the way previous versions of NUnit ran tests and is the -default setting. - -

If Run tests in a single separate process is selected, -a separate process is used for all tests. - -

If Run tests in a separate process per Assembly is selected, -a separate process is used for each test assembly. - -

Default Domain Usage

- -

If Use a separate AppDomain per Assembly is selected, each assembly - in a multiple-assembly test run will be loaded in a separate AppDomain. - This setting is not available when Run tests in a separate process - per Assembly is selected above. - -

If Use a single AppDomain for all tests is selected, all assemblies in - a multiple-assembly test run will use the same AppDomain. This was - the standard behavior of NUnit prior to version 2.4 and is the - default setting. - -

If Merge tests across assemblies is checked, the display of tests - will not be divided across assemblies. If automatic namespace suites are - used, they will be merged across all assemblies. This option is only - available when tests are run in the same appdomain. - -


Test Loader Settings - Assembly Reload


- -
-
- -

Assembly Reload

- -

If Reload before each test run is checked, a reload will occur whenever the run button is -pressed whether the assemblies appear to have changed or not.

- -

If Reload when test assembly changes is checked, assemblies are watched for any change and -an automatic reload is initiated. This item is disabled on Windows 98 or ME.

- -

If Re-run last tests run is checked, tests are re-run whenever a Reload - takes place.

- -

Test Loader Settings - Advanced


- -
-
- -

Shadow Copy

- -

NUnit normally uses .Net shadow-copying in order to allow you to edit -and recompile assemblies while it is running. Uncheck this box to disable -shadow-copy only if you have a particular problem that requires it.

- -

Note: If you are tempted to disable shadow copy in order to access -files in the same directory as your assembly, you should be aware that there -are alternatives. Consider using the Assembly.Codebase property rather than -Assembly.Location. - - -


IDE Support Settings - Visual Studio


- -
-
- -

Visual Studio

- -

If Enable Visual Studio Support is checked, the user will be able to open Visual Studio projects -and solutions and add Visual Studio projects to existing test projects.

- -

Advanced Settings - Internal Trace


- -
-
- -

Internal Trace

- -

The Trace Level dropdown controls the level of internal trace output.

- - - - -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/setup.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/setup.html b/lib/NUnit.org/NUnit/2.5.9/doc/setup.html deleted file mode 100644 index 34cefdf..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/setup.html +++ /dev/null @@ -1,239 +0,0 @@ - - - - -NUnit - Setup - - - - - - - - - - - - - -
- - - -

SetUpAttribute (NUnit 2.0 / 2.5)

- -

This attribute is used inside a TestFixture to provide a common set of - functions that are performed just before each test method is called. - -

Before NUnit 2.5, a TestFixture could have only one SetUp method - and it was required to be an instance method. - -

Beginning with NUnit 2.5, SetUp methods may be either static or - instance methods and you may define more than one of them in a fixture. - Normally, multiple SetUp methods are only defined at different levels - of an inheritance hierarchy, as explained below. - -

If a SetUp method fails or throws an exception, the test is not executed - and a failure or error is reported. - - -

Example:

- -
- -
- Language Filter - -
- -
namespace NUnit.Tests
-{
-  using System;
-  using NUnit.Framework;
-
-  [TestFixture]
-  public class SuccessTests
-  {
-    [SetUp] public void Init()
-    { /* ... */ }
-
-    [TearDown] public void Cleanup()
-    { /* ... */ }
-
-    [Test] public void Add()
-    { /* ... */ }
-  }
-}
-
- -
Imports System
-Imports Nunit.Framework
-
-Namespace Nunit.Tests
-
-  <TestFixture()> Public Class SuccessTests
-    <SetUp()> Public Sub Init()
-    ' ...
-    End Sub
-
-    <TearDown()> Public Sub Cleanup()
-    ' ...
-    End Sub
-
-    <Test()> Public Sub Add()
-    ' ...
-    End Sub
-  End Class
-End Namespace
-
- -
#using <Nunit.Framework.dll>
-using namespace System;
-using namespace NUnit::Framework;
-
-namespace NUnitTests
-{
-  [TestFixture]
-  public __gc class SuccessTests
-  {
-    [SetUp] void Init();
-    [TearDown] void Cleanup();
-
-    [Test] void Add();
-  };
-}
-
-#include "cppsample.h"
-
-namespace NUnitTests {
-  // ...
-}
-
- -
package NUnit.Tests;
-
-import System.*;
-import NUnit.Framework.TestFixture;
-
-
-/** @attribute NUnit.Framework.TestFixture() */
-public class SuccessTests
-{
-  /** @attribute NUnit.Framework.SetUp() */
-  public void Init()
-  { /* ... */ }
-
-  /** @attribute NUnit.Framework.TearDown() */
-  public void Cleanup()
-  { /* ... */ }
-
-  /** @attribute NUnit.Framework.Test() */
-  public void Add()
-  { /* ... */ }
-}
-
- -
- -

Inheritance

- -

The SetUp attribute is inherited from any base class. Therefore, if a base - class has defined a SetUp method, that method will be called - before each test method in the derived class. - -

Before NUnit 2.5, you were permitted only one SetUp method. If you wanted to - have some SetUp functionality in the base class and add more in the derived - class you needed to call the base class method yourself. - -

With NUnit 2.5, you can achieve the same result by defining a SetUp method - in the base class and another in the derived class. NUnit will call base - class SetUp methods before those in the derived classes. - -

Note: Although it is possible to define multiple SetUp methods - in the same class, you should rarely do so. Unlike methods defined in - separate classes in the inheritance hierarchy, the order in which they - are executed is not guaranteed. - -

See also...

- - - -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/setupFixture.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/setupFixture.html b/lib/NUnit.org/NUnit/2.5.9/doc/setupFixture.html deleted file mode 100644 index c2a7f8c..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/setupFixture.html +++ /dev/null @@ -1,216 +0,0 @@ - - - - -NUnit - SetupFixture - - - - - - - - - - - - - -
- - - -

SetUpFixtureAttribute (NUnit 2.4)

- -

This is the attribute that marks a class that contains the one-time - setup or teardown methods for all the test fixtures under a given - namespace. The class may contain at most one method marked with the - SetUpAttribute and one method marked with the TearDownAttribute.

- -

There are a few restrictions on a class that is used as a setup fixture. -

-

- -

The SetUp method in a SetUpFixture is executed once before any of the fixtures -contained in its namespace. The TearDown method is executed once after all the -fixtures have completed execution. In the examples below, the method RunBeforeAnyTests() -is called before any tests or setup methods in the NUnit.Tests namespace. The method -RunAfterAnyTests() is called after all the tests in the namespace as well as their -individual or fixture teardowns have completed exection.

- -

Only one SetUpFixture should be created in a given namespace. A SetUpFixture -outside of any namespace provides SetUp and TearDown for the entire assembly. - -

Example:

- -
- -
- Language Filter - -
- -
namespace NUnit.Tests
-{
-  using System;
-  using NUnit.Framework;
-
-  [SetUpFixture]
-  public class MySetUpClass
-  {
-    [SetUp]
-	RunBeforeAnyTests()
-	{
-	  // ...
-	}
-
-    [TearDown]
-	RunAfterAnyTests()
-	{
-	  // ...
-	}
-  }
-}
-
- -
Imports System
-Imports Nunit.Framework
-
-Namespace Nunit.Tests
-
-  <TestFixture()> Public Class MySetUpClass
-    <SetUp()> Public Sub RunBeforeAnyTests()
-	  ' ...
-	End Sub
-	
-	<TearDown()> Public Sub RunAfterAnyTests()
-	  ' ...
-	End Sub
-  End Class
-End Namespace
-
- -
#using <Nunit.Framework.dll>
-using namespace System;
-using namespace NUnit::Framework;
-
-namespace NUnitTests
-{
-  [TestFixture]
-  public __gc class MySetUpClass
-  {
-    [SetUp] public void RunBeforeAnyTests();
-	[TearDown] public void RunAfterAnyTests();
-  };
-}
-
-#include "cppsample.h"
-
-namespace NUnitTests {
-  // ...
-}
-
- -
package NUnit.Tests;
-
-import System.*;
-import NUnit.Framework.TestFixture;
-
-
-/** @attribute NUnit.Framework.TestFixture() */
-public class MySetUpClass
-{
-  /** @attribute NUnit.Framework.SetUp() */
-  public void RunBeforeAnyTests()
-  { /* ... */ }
-
-  /** @attribute NUnit.Framework.TearDown() */
-  public void RunAfterAnyTests()
-  { /* ... */ }
-}
-
- -
-
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/stringAssert.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/stringAssert.html b/lib/NUnit.org/NUnit/2.5.9/doc/stringAssert.html deleted file mode 100644 index e5f3068..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/stringAssert.html +++ /dev/null @@ -1,105 +0,0 @@ - - - - -NUnit - StringAssert - - - - - - - - - - - - - -
- -

StringAssert (NUnit 2.2.3)

-

The StringAssert class provides a number of methods that are useful -when examining string values.

- -
-
StringAssert.Contains( string expected, string actual );
-StringAssert.Contains( string expected, string actual, 
-                string message );
-StringAssert.Contains( string expected, string actual,
-                string message, params object[] args );
-
-StringAssert.StartsWith( string expected, string actual );
-StringAssert.StartsWith( string expected, string actual, 
-                string message );
-StringAssert.StartsWith( string expected, string actual,
-                string message, params object[] args );
-
-StringAssert.EndsWith( string expected, string actual );
-StringAssert.EndsWith( string expected, string actual, 
-                string message );
-StringAssert.EndsWith( string expected, string actual,
-                string message, params object[] args );
-
-StringAssert.AreEqualIgnoringCase( string expected, string actual );
-StringAssert.AreEqualIgnoringCase( string expected, string actual, 
-                string message );
-StringAssert.AreEqualIgnoringCase( string expected, string actual,
-                string message params object[] args );
-				
-StringAssert.IsMatch( string regexPattern, string actual );
-StringAssert.IsMatch( string regexPattern, string actual, 
-                string message );
-StringAssert.IsMatch( string regexPattern, string actual,
-                string message, params object[] args );
-
- -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/stringConstraints.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/stringConstraints.html b/lib/NUnit.org/NUnit/2.5.9/doc/stringConstraints.html deleted file mode 100644 index 0b7d535..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/stringConstraints.html +++ /dev/null @@ -1,243 +0,0 @@ - - - - -NUnit - StringConstraints - - - - - - - - - - - - - -
- -

String Constraints (NUnit 2.4)

- -

String constraints perform tests that are specific to strings. - Attempting to test a non-string value with a string constraint - is an error and gives an exception. - -

The Text prefix is deprecated beginning with NUnit 2.5.1 - and will be removed in NUnit 3.0. - -

SubstringConstraint

- -

Action

-

Tests for a substring. - -

Constructor

-
-SubstringConstraint(string expected)
-
- -

Syntax

-
-Is.StringContaining(string expected)
-Contains.Substring(string expected)
-ContainsSubstring(string expected)
-Contains(string expected)
-[Obsolete] Text.Contains(string expected)
-[Obsolete] Text.DoesNotContain(string expected)
-
- -

Modifiers

-
-...IgnoreCase
-
- -

Examples of Use

-
-string phrase = "Make your tests fail before passing!"
-
-Assert.That( phrase, Is.StringContaining( "tests fail" ) );
-Assert.That( phrase, Contains.Substring( "tests fail" ) );
-Assert.That( phrase, Is.Not.StringContaining( "tests pass" ) );
-Assert.That( phrase, Is.StringContaining( "make" ).IgnoreCase );
-Expect (phrase, Contains.Substring( "make" ).IgnoreCase );
-
- -

Notes

-
    -
  1. ContainsSubstring and Contains may appear only in the - body of a constraint expression or when the inherited syntax is used. -
  2. Contains is not actually a string constraint but is converted - to one when a string is being tested. -
- -

StartsWithConstraint

- -

Action

-

Tests for an initial string. - -

Constructor

-
-StartsWithConstraint(string expected)
-
- -

Syntax

-
-Is.StringStarting(string expected)
-StartsWith(string expected)
-[Obsolete] Text.StartsWith(string expected)
-[Obsolete] Text.DoesNotStartWith(string expected)
-
- -

Modifiers

-
-...IgnoreCase
-
- -

Examples of Use

-
-string phrase = "Make your tests fail before passing!"
-
-Assert.That( phrase, Is.StringStarting( "Make" ) );
-Assert.That( phrase, Is.Not.StringStarting( "Break" ) );
-Assert.That( phrase, Has.Length.GreaterThan(10)
-                .And.Not.StartsWith( "Break" ) );
-Expect( phrase, StartsWith( "Make" ) );
-
- -

Notes

-
    -
  1. StartsWith may appear only in the body of a constraint - expression or when the inherited syntax is used. -
- -

EndsWithConstraint

- -

Action

-

Tests for an ending string. - -

Constructor

-
-EndsWithConstraint(string expected)
-
- -

Syntax

-
-Is.StringEnding(string expected)
-EndsWith(string expected)
-[Obsolete] Text.EndsWith(string expected)
-[Obsolete] Text.DoesNotEndWith(string expected)
-
- -

Modifiers

-
-...IgnoreCase
-
- -

Examples of Use

-
-string phrase = "Make your tests fail before passing!"
-
-Assert.That( phrase, Is.StringEnding( "!" ) );
-Assert.That( phrase, Is.StringEnding( "PASSING!" ).IgnoreCase );
-Expect( phrase, EndsWith( "!" ) );
-
- -

Notes

-
    -
  1. EndsWith may appear only in the body of a constraint - expression or when the inherited syntax is used. -
- -

RegexConstraint

- -

Action

-

Tests that a pattern is matched. - -

Constructor

-
-RegexConstraint(string pattern)
-
- -

Syntax

-
-Is.StringMatching(string pattern)
-Matches(string pattern)
-[Obsolete] Text.Matches(string pattern)
-[Obsolete] Text.DoesNotMatch(string pattern)
-
- -

Modifiers

-
-...IgnoreCase
-
- -

Examples of Use

-
-string phrase = "Make your tests fail before passing!"
-
-Assert.That( phrase, Is.StringMatching( "Make.*tests.*pass" ) );
-Assert.That( phrase, Is.Not.StringMatching( "your.*passing.*tests" ) );
-Assert.That( phrase, Has.Length.GreaterThan(10)
-                .And.Not.Matches( "your.*passing.*tests" ) );
-Expect( phrase, Matches( "Make.*pass" ) );
-
- -

Notes

-
    -
  1. Matches may appear only in the body of a constraint - expression or when the inherited syntax is used. -
- -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/suite.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/suite.html b/lib/NUnit.org/NUnit/2.5.9/doc/suite.html deleted file mode 100644 index 45b5fcf..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/suite.html +++ /dev/null @@ -1,238 +0,0 @@ - - - - -NUnit - Suite - - - - - - - - - - - - - -
- -
Update: August 22, 2007
-

SuiteAttribute (NUnit 2.0/2.4.4)

- -

The Suite Attribute is used to define subsets of test to be run from the - command-line, using the /fixture option. It was introduced in NUnit - 2.0 to replace the older approach of inheriting from the TestSuite class.

- -

Originally, the NUnit developers believed that the need for the Suite - mechanism would diminish because of the dynamic creation of suites based - on namespaces. It was provided for backwards compatibility.

- -

That has not proven to be true. Suites are still used today by many people, - so we are making an effort to revive them in terms of usability. - -

The Suite mechanism depends on a static property marked with the SuiteAttribute. - In the clasic implementation, supported by all releases since 2.0, that property - returns a TestSuite, populated with the tests that are to be executed. - -

Old Approach

- -
- -
namespace NUnit.Tests
-{
-  using System;
-  using NUnit.Framework;
-  using NUnit.Core;
-
-  public class AllTests
-  {
-    [Suite]
-    public static TestSuite Suite
-    {
-      get
-      {
-        TestSuite suite = new TestSuite("All Tests");
-        suite.Add(new OneTestCase());
-        suite.Add(new Assemblies.AssemblyTests());
-        suite.Add(new AssertionTest());
-        return suite;
-      }
-    }
-  }
-}
-
- -
- -

This approach has a serious problem: it requires a reference to the nunit.core assembly, - which is not normally referenced by user tests. This means that the tests - cannot be ported across versions of NUnit without recompilation. In some cases, - introducing more than one version of the core assembly can prevent NUnit - from running correctly. - -

Beginning with NUnit 2.4.4, a new approach is available. The property marked - with the SuiteAttribute may simply return a collection containing test - fixture objects or Types. - If a Type is provided, NUnit creates an object of that type for use - as a fixture. Any other object is assumed to be a pre-created fixture object. - This allows objects with parameterized constructors or settable - properties to be used as fixtures. - -

Test suites created through use of the SuiteAttribute may contain TestFixtureSetUp and - TestFixtureTearDown methods, to perform one-time setup and teardown - for the tests included in the suite. - -

New Approach - Fixture Objects

- -
- -
namespace NUnit.Tests
-{
-  using System;
-  using NUnit.Framework;
-
-  private class AllTests
-  {
-    [Suite]
-    public static IEnumerable Suite
-    {
-      get
-      {
-        ArrayList suite = new ArrayList();
-        suite.Add(new OneTestCase());
-        suite.Add(new AssemblyTests());
-        suite.Add(new NoNamespaceTestFixture());
-        return suite;
-      }
-    }
-  }
-}
-
- -
- -

New Approach - Fixture Types

- -
- -
namespace NUnit.Tests
-{
-  using System;
-  using NUnit.Framework;
-
-  private class AllTests
-  {
-    [Suite]
-    public static IEnumerable Suite
-    {
-      get
-      {
-        ArrayList suite = new ArrayList();
-        suite.Add(typeof(OneTestCase));
-        suite.Add(typeof(AssemblyTests));
-        suite.Add(typeof(NoNamespaceTestFixture));
-        return suite;
-      }
-    }
-  }
-}
-
- -
- -

Limitations

- -NUnit support for user-defined Suites currently has two limitations: - -
    -
  1. It is not possible to include individual test cases directly - in a Suite using the new approach. Anyone wanting to do so will - need to use the old approach and create an object derive from - NUnit.Core.TestCase. This is not recommended, since it requires - a reference to the core assembly. - -
  2. Suites are currently not displayed in the Gui or run automatically - by either runner when they are encountered. The historical purpose of - the Suite mechanism was to provide a way of aggregating tests at the - top level of each run. Hence, they are only supported when used with - the /fixture option on the console or gui command line. -
- -Approaches to removing these limitations are being investigated as part -of the planning for future NUnit releases. - -
- - - - - - - - - - - - http://git-wip-us.apache.org/repos/asf/lucenenet/blob/f63ba31d/lib/NUnit.org/NUnit/2.5.9/doc/suiteBuilders.html ---------------------------------------------------------------------- diff --git a/lib/NUnit.org/NUnit/2.5.9/doc/suiteBuilders.html b/lib/NUnit.org/NUnit/2.5.9/doc/suiteBuilders.html deleted file mode 100644 index fa8b8d9..0000000 --- a/lib/NUnit.org/NUnit/2.5.9/doc/suiteBuilders.html +++ /dev/null @@ -1,101 +0,0 @@ - - - - -NUnit - SuiteBuilders - - - - - - - - - - - - - -
- -

SuiteBuilders (NUnit 2.4)

- -

Purpose

-

A SuiteBuilder is an addin used to build a test fixture from a type. NUnit itself -uses a SuiteBuilder to recognize and build TestFixtures. - -

Extension Point

-

An addin may use the host to access this extension point by name: - -

-	IExtensionPoint suiteBuilders = host.GetExtensionPoint( "SuiteBuilders" );
- -

Interface

-

The extension object passed to Install must implement the ISuiteBuilder interface: - -

-	public interface ISuiteBuilder
-	{
-		bool CanBuildFrom( Type type );
-		Test BuildFrom( Type type );
-	}
-
- -

CanBuildFrom should return true if the specified Type is one from which -the builder is able to create a fixture. This usually involve examining -the Type and its attriutes. - -

The BuildFrom method should return a test fixture completely populated -with its contained test cases. Return null if it is not possible to -build a fixture using the provided Type. - - -

- - - - - - - - - - - -