Description
Dead simple, test framework independent, without any magic, a library for annotating steps of test case scenarios. Please read "Readable and clear tests for ASP.NET Core services" article for better explanation and example use cases https://cezarypiatek.github.io/post/component-tests-scenarios/
NScenario alternatives and similar packages
Based on the "Testing" category.
Alternatively, view NScenario alternatives based on common mentions on social networks and blogs.
-
Bogus
:card_index: A simple fake data generator for C#, F#, and VB.NET. Based on and ported from the famed faker.js. -
xUnit
xUnit.net is a free, open source, community-focused unit testing tool for the .NET Framework. -
Fluent Assertions
A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3. -
SpecFlow
#1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration -
AutoFixture
AutoFixture is an open source library for .NET designed to minimize the 'Arrange' phase of your unit tests in order to maximize maintainability. Its primary goal is to allow developers to focus on what is being tested rather than how to setup the test scenario, by making it easier to create object graphs containing test data. -
NBomber
Modern and flexible load testing framework for Pull and Push scenarios, designed to test any system regardless a protocol (HTTP/WebSockets/AMQP etc) or a semantic model (Pull/Push). -
Verify
Verify is a snapshot tool that simplifies the assertion of complex data models and documents. -
Machine.Specifications
Machine.Specifications is a Context/Specification framework for .NET that removes language noise and simplifies tests. -
Compare-Net-Objects
What you have been waiting for :+1: Perform a deep compare of any two .NET objects using reflection. Shows the differences between the two objects. -
WireMock.Net
WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality. -
GenFu
GenFu is a library you can use to generate realistic test data. It is composed of several property fillers that can populate commonly named properties through reflection using an internal database of values or randomly created data. You can override any of the fillers, give GenFu hints on how to fill them. -
Canopy
f# web automation and testing library, built on top of Selenium (friendly to c# also) -
Expecto
A smooth testing lib for F#. APIs made for humans! Strong testing methodologies for everyone! -
NFluent
Smooth your .NET TDD experience with NFluent! NFluent is an ergonomic assertion library which aims to fluent your .NET TDD experience (based on simple Check.That() assertion statements). NFluent aims your tests to be fluent to write (with a super-duper-happy 'dot' auto-completion experience), fluent to read (i.e. as close as possible to plain English expression), but also fluent to troubleshoot, in a less-error-prone way comparing to the classical .NET test frameworks. NFluent is also directly inspired by the awesome Java FEST Fluent assertion/reflection library (http://fest.easytesting.org/) -
xBehave.net
✖ An xUnit.net extension for describing each step in a test with natural language. -
NSpec
A battle hardened testing framework for C# that's heavily inspired by Mocha and RSpec. -
SpecsFor
SpecsFor is a light-weight Behavior-Driven Development framework that focuses on ease of use for *developers* by minimizing testing friction. -
LightBDD
BDD framework allowing to create easy to read and maintain tests. -
ArchUnitNET
A C# architecture test library to specify and assert architecture rules in C# for automated testing. -
Fine Code Coverage
Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too) -
snapshooter
Snapshooter is a snapshot testing tool for .NET Core and .NET Framework -
Xunit.Gherkin.Quick
BDD in .NET Core - using Xunit and Gherkin (compatible with both .NET Core and .NET) -
ExpressionToCode
Generates valid, readable C# from an Expression Tree. -
SimpleStubs
*SimpleStubs* is a simple mocking framework that supports Universal Windows Platform (UWP), .NET Core and .NET framework. SimpleStubs is currently developed and maintained by Microsoft BigPark Studios in Vancouver. -
Moq.Contrib.HttpClient
A set of extension methods for mocking HttpClient and IHttpClientFactory with Moq. -
NCrunch
An automated continuous & concurrent testing tool for Visual Studio. [$] -
ReportPortal
AI-powered Test Automation Dashboard. Acquire, aggregate and analyze test reports to ascertain release health.
Clean code begins in your IDE with SonarLint
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of NScenario or a related project?
README
NScenario
Dead simple, test framework independent, without any magic, a library for annotating steps of test case scenarios. Please read Readable and clear tests for ASP.NET Core services article for better exaplanation and example use cases.
How to install
NScenario
is distribute as a nuget package NScenario
How to use it
Just create an instance of NScenario.TestScenario
class and start annotating your test steps by wrapping it in Step
method call.
You can create TestScenario
instance manually by providing a desired composition of IScenarioStepExecutor
instances or simply by calling TestScenarioFactory.Default()
method.
Example test can look as follows:
[Test]
public async Task should_activate_community_supporter_license_when_eligible()
{
using var driver = await LicenseServerTestDriver.Create();
var scenario = TestScenarioFactory.Default();
var activationData = new
{
email = "[email protected]",
licenseKey = "WTKP4-66NL5-HMKQW-GFSCZ"
};
await scenario.Step("Import supporters", async () =>
{
await driver.ImportSupporters("BuyMeCoffee", new[] { "[email protected]", "[email protected]", activationData.email });
});
await scenario.Step("Register purchase for supporter email", async () =>
{
await driver.RegisterPurchaseWithCoupon("Extension for VS2017", activationData.email, activationData.licenseKey, "OssSupporter");
});
await scenario.Step("Activate the license with supporter email", async () =>
{
var activationResult = await scenario.Step("Call active license endpoint" () =>
{
return await driver.ActivateLicense(activationData.email, activationData.licenseKey);
});
await scenario.Step("Verify that license activated properly", () =>
{
Assert.AreEqual(true, activationResult.Activated);
Assert.AreEqual("Unlimited", activationResult.Capabilities["VsVersion"]);
});
});
}
Console output
SCENARIO: should activate community supporter license when eligible
STEP 1: Import supporters
STEP 2: Register purchase for supporter email
STEP 3: Activate the license with supporter email
STEP 3.1: Call active license endpoint
STEP 3.2: Verify that license activated properly
Benefits:
- Obvious way to enforce step descriptions
- More readable test scenario
- Sub-scopes for repeatable steps
- Readable output that facilitates broken scenario investigation
Console output
Some test runners are hijacking console output and provide a custom stream for logging. By default NScenario
is writing scenario description to the console, but this can be overridden by providing a custom TextWriter
stream to TestScenarioFactory.Default()
method. For example, in case of problems with NUnit
you can initialize TestScenario
as follows:
var scenario = TestScenarioFactory.Default(TestContext.Out);
Test scenario description
Test scenario description is generated by removing underscores from the test method name ([CallerMemberName]
is used to retrieve that name). This allows for immediate review of the test name (I saw many, extremely long and totally ridiculous test method names. A good test method name should reveal the intention of the test case, not its details).
NScenario
is prefixing scenario title with SCENARIO:
prefix and every step is prefixed with STEP
. If you are writing step descriptions in other languages than English, you can override those prefixes by specifing them explicitly why calling TestScenarioFactory.Default()
method.
var scenario = TestScenarioFactory.Default(scenarioPrefix: "SCENARIUSZ", stepPrefix: "KROK");
Why not XBehave.net
xBehave.net is the XUnit
extension so it can be used only with XUnit based tests. In my opinion, it is also quite cryptic (string extension methods called with single letter might not obvious) and a little bit over-complicated. BUT THIS IS MY PERSONAL OPINION
*Note that all licence references and agreements mentioned in the NScenario README section above
are relevant to that project's source code only.