Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

This repository has been archived by the owner on Jun 12, 2021. It is now read-only.

adamralph / xbehave.net Public archive

Notifications You must be signed in to change notification settings
Fork 46
Star 381

Code
Issues 15
Pull requests 1
Discussions
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security
Insights

Extending xBehave.net

Jump to bottom

Adam Ralph edited this page Oct 12, 2013 · 12 revisions

Defining a custom step method
Defining a custom syntax

Toggle table of contents Pages 38

Home
A test class instance is created for each step
Assertions
Async steps
Backgrounds
Can I use xBehave.net with ApprovalTests?
Can I use xBehave.net with continuous test tools?
Can I use xbehave.net with fluent assertion libraries?
Can I use xbehave.net with isolation (faking mocking substitution) libraries?
Can I use xBehave.net without introducing xunit.assert, xunit.analyzers, etc.?
Can't access fixture data when using IUseFixture
Changes in version 2.0
Continuing on failure
Debugging scenarios
Defining a custom step method
Defining a custom syntax
Documentation
Extending xBehave.net
FAQ
How can I reuse steps?
Known Issues
Object disposal
Package dependencies
Quick start
Quickstart
Running scenarios
Scenarios are shown as a single test in ReSharper instead of a test for each step
Scenarios with examples
Skipping steps and scenarios
Step filters
Step metadata
Step names
Steps which return tasks that never complete, are never completed
Teardown
Tests are not found when using the xunit.runner.msbuild in TeamCity
What kind of tests can I write using xBehave.net?
Why do my tests succeed in one test runner but fail in another?
Writing scenarios

Home
Quick start
Documentation
Extending xBehave.net
- Defining a custom step method
- Defining a custom syntax
FAQ
Known Issues

Clone this wiki locally

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.