nunit-core team mailing list archive
-
nunit-core team
-
Mailing list archive
-
Message #00061
[Blueprint setup-and-teardown] SetUp and TearDown Changes
Blueprint changed by Mark Levison:
Whiteboard changed to:
A few quick thoughts:
- Most/Many users don't know what a Fixture is - this happened when we stop requiring inheritance from a base class
- The existing naming convention is confusing for people coming the java world (Gerard and I - maybe the only two people in the world who switch back and forth).
We might want to consider adopting the JUnit 4.x style naming:
Before/After - for before and after each test
BeforeClass/AfterClass - for before and after each class
BeforeNamespace/AfterNamespace - .... - I don't know why you would want to do this
BeforeAssembly/AfterAssembly -
Now it might useful to have one more: BeforeEverything/AfterEverything -
I might use this to load a large file into RAM that I want to persist
across all tests, in all assemblies. Yes I know very UnitTest
--
SetUp and TearDown Changes
https://blueprints.launchpad.net/nunit-3.0/+spec/setup-and-teardown