SpecUnit    9 concerns, 40 contexts, 81 specifications

Concern specifications    4 contexts, 4 specifications

Concern, when creating a concern based on a type    1 specification

behaves like: context with concern

• should be named for the type

Concern, after adding a context for a type    1 specification

behaves like: context with concern

• should have the context in its list of contexts

Concern, when a context does not belong to a concern    1 specification

behaves like: context with concern

• should not have the context in its list of contexts

Concern, when adding a context to a concern that it does not belong to    1 specification

• should cause an error

Console specifications    3 contexts, 3 specifications

Console, when no arguments are provided    1 specification

• should display an error message

Console, when there is no assembly that corresponds to the assembly name provided as a console argument    1 specification

• should display an error message

Console, when given a valid assembly file path    1 specification

• should write the spec report for the assembly indicated by the file path

Context specifications    7 contexts, 13 specifications

Context, when a test fixture class is a concern    3 specifications

• should be attributed with the ConcernAttribute
• should have a name that is prefixed with the concern name
• should have a concern name that is the name specified by the concern attribute

Context, when a test fixture class is not a concern    3 specifications

• should not be attributed with the ConcernAttribute
• should not have a name that is prefixed with the concern name
• should not have a concern name

Context, when building a context for a test fixture type    2 specifications

• should collect and build the specifications
• should create a specification for each test method in the type

Context, when creating a context for a type that is not a test fixture    1 specification

• should cause an error

Context, when two contexts represent the same test fixture    1 specification

• they should be equal

Context, when a context behaves like another context    1 specification

• should have a subclass whose name begins with "behaves like"

Context, when a context does not behave like another context    2 specifications

• should not have a subclass whose name begins with "behaves like"
• may not have a subclass

ReportGenerator specifications    11 contexts, 19 specifications

ReportGenerator, when rendering the report title    5 specifications

• should include the specification dataset name
• should inlude the counts of the concerns
• should inlude the counts of the contexts
• should inlude the counts of the specifications
• should render the name in an H1

ReportGenerator, when rendering a concern header    3 specifications

• should include the counts of the contexts
• should include the counts of the specifications
• should render the name in an H2

ReportGenerator, when rendering a concern    1 specification

• should render its contexts

ReportGenerator, when rendering a context header    2 specifications

• should render the count of specifications
• should render the name in an H3

ReportGenerator, when rendering a context that behaves like another context    1 specification

• should indicate that it behaves like another context

ReportGenerator, when rendering a context that does not behaves like another context    1 specification

• should indicate that it behaves like another context

ReportGenerator, when rendering a context    2 specifications

• should render each specification
• should render specifications as a bulletted list

ReportGenerator, when writing the spec report for an assembly    1 specification

• should write an html file named for the assembly that the report is created for

ReportGenerator, when pluralizing a caption for a count where the count is greater than one    1 specification

• should append "s" to the caption to indicate the plurality

ReportGenerator, when pluralizing a caption for a count where the count is zero    1 specification

• should append "s" to the caption to indicate the plurality

ReportGenerator, when pluralizing a caption for a count where the count is equal to one    1 specification

• should not append "s" to the caption

Specification specifications    4 contexts, 4 specifications

Specification, when a test method is a specificaition    1 specification

• should have an attribute in the SpecificationAttribute family

Specification, when a creating a specification for a method    1 specification

• should be a method that has an attribute in the SpecificationAttribute family

Specification, when a specification name contains "when"    1 specification

• should add a warning to the specification name indicating that the specification may be a context

Specification, when a specification name contains "if"    1 specification

• should add a warning to the specification name indicating that the specification may be a context

SpecificationDataset specifications    3 contexts, 5 specifications

SpecificationDataset, when building a dataset for an assembly    2 specifications

• should collect and build the assembly's concerns
• should be named for the file stem of the of the assembly name

SpecificationDataset, when collecting concerns from an assembly    1 specification

• should include one concern for each unique concern found

SpecificationDataset, when selecting context classes from a list of types    2 specifications

• should ignore abstract types
• should include concrete classes with the TestFixture attribute

SpecificationExtensions specifications    2 contexts, 27 specifications

SpecificationExtensions, when expressing assertions as BDD style extension methods    26 specifications

• should allow "ShouldBeFalse" to be used in place of "Assert IsFalse"
• should allow "ShouldBeTrue" to be used in place of "Assert IsTrue"
• should allow "ShouldEqual" to be used in place of "Assert AreEqual"
• should allow "ShouldNotEqual" to be used in place of "Assert AreNotEqual"
• should allow "ShouldBeNull" to be used in place of "Assert IsNull"
• should allow "ShouldNotBeNull" to be used in place of "Assert IsNotNull"
• should allow "ShouldBeTheSameAs" to be used in place of "Assert AreSame"
• should allow "ShouldNotBeTheSameAs" to be used in place of Assert AreNotSame
• should allow "ShouldBeOfType" to be used in place of "Assert IsInstanceOfType"
• should allow "ShouldNotBeOfType" to be used in place of "Assert IsNotInstanceOfType"
• should allow "ShouldContain" to be used in place of "Assert Contains"
• should allow "ShouldNotContain" to be used in place of "Assert NotContains"
• should allow "ShouldBeEmpty" to be used on a collection in place of "Assert IsEmpty"
• should allow "ShouldBeEmpty" to be used on a string in place of "Assert IsEmpty"
• should allow "ShouldNotBeEmpty" to be used on a string in place of "Assert IsNotEmpty"
• should allow "ShouldNotBeEmpty" to be used on a collection in place of "Assert IsNotEmpty"
• should allow "ShouldBeGreaterThan" to be used in place of "Assert Greater"
• should allow "ShouldBeLessThan" to be used in place of "Assert Less"
• should allow "ShouldContain" to be used in place of "StringAssert Contains"
• should allow "ShouldBeEqualIgnoringCase" to be used in place of "StringAssert AreEqualIgnoringCase"
• should allow "ShouldStartWith" to be used in place of "StringAssert StartsWith"
• should allow "ShouldEndWith" to be used in place of "StringAssert EndsWith"
• should allow "ShouldBeSurroundedWith" to be used in place of "StringAssert StartsWith" and "StringAssert EndsWith"
• should allow "ShouldBeSurroundedWith" with a single delimiter to be used in place of "StringAssert StartsWith" and "StringAssert EndsWith"
• should allow "ShouldBeThrownBy" to be used in place of "ExpectedExceptionAttribute"
• should allow "ShouldContainErrorMessage" to be used on an exception in place of "StringAssert Contains"

SpecificationExtensions, when the ShouldBeThrownBy assertion is not satisfied    1 specification

• should fail the test

SpecificationExtensions (GetException extention) specifications    1 context, 1 specification

SpecificationExtensions (GetException extention), when a delegate throws an exception    1 specification

• should retrieve the exception

SpecificationName specifications    5 contexts, 5 specifications

SpecificationName, when the name has underscores    1 specification

• should replace underscores with spaces

SpecificationName, when the name has a leading underscore    1 specification

• should replace underscores with spaces

SpecificationName, when the name has a trailing underscore    1 specification

• should replace underscores with spaces

SpecificationName, when the name has two consecutive underscores    1 specification

• should replace the underscores with a quotation mark

SpecificationName, when the name has an underscore followed by an "S" followed by an underscore    1 specification

• should replace it with appostrophy "S"