-
Notifications
You must be signed in to change notification settings - Fork 40
Feature Fixture (v2.x)
Suremaker edited this page Jan 13, 2019
·
2 revisions
The FeatureFixture class is a recommended class to be used for feature tests.
Its implementation is slightly different between integration projects (depending on test framework nature), but in general it's responsibility is to:
- provide IBddRunner instance, that would be used to run scenarios for given test class,
- annotate the test class with FeatureFixtureAttribute to indicate that class contains LightBDD scenarios (it is required by NUnit3 and XUnit2 integration and optional for MsTest2 one),
- dispose the underlying feature runner instance after all tests belonging for the class have finished (NUnit3),
- provide helper properties like TestOutput in XUnit2.
It is possible to write tests without usage of this class. In order to do that, please check FeatureFixture implementation for specific test framework and repeat it in the test class:
- LightBDD.NUnit2/FeatureFixture.cs,
- LightBDD.NUnit3/FeatureFixture.cs,
- LightBDD.MsTest2/FeatureFixture.cs,
- LightBDD.XUnit2/FeatureFixture.cs,
- LightBDD.Fixie2/FeatureFixture.cs.
Please note that it is possible to install class templates and project templates from Visual Studio Gallery.
Continue reading: Step Comments
- What Is New
- Quick Start
- Tests Structure and Conventions
- Scenario Steps Definition
- Composite Steps Definition
- SetUp and TearDown
- DI Containers
- Step parameters
- Test Progress Notification
- Generating Reports
- Execution Time Measurement
- Feature Fixture
- Step Comments
- Step Attachments
- Extending Test Behavior
- Test Utilities
- Test Framework Integrations
- LightBDD Configuration
- Visual Studio Extensions
- How to