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
{{ message }}
This repository was archived by the owner on Nov 7, 2019. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,19 +40,23 @@ Update your `project.json`:
40
40
41
41
0. Build for your tests to be discovered. **Note:** there is [a bug with the .NET Core CLI requiring a second build for newly added files to be discovered](https://github.com/stajs/SpecFlow.NetCore/issues/22).
42
42
43
-
### Supported frameworks
43
+
### Samples
44
+
45
+
If you build the [samples](https://github.com/stajs/SpecFlow.NetCore/tree/master/samples/) solution, you should see `.feature.cs` files and an `app.config` being generated.
46
+
47
+
## Supported frameworks
48
+
49
+
### .NET Core
44
50
45
51
-`netcoreapp1.0`
46
52
-`net46`
47
53
-`net461`
48
54
49
-
### Samples
50
-
51
-
If you build the [samples](https://github.com/stajs/SpecFlow.NetCore/tree/master/samples/) solution, you should see `.feature.cs` files and an `app.config` being generated.
55
+
### Test frameworks
52
56
53
-
## Test Frameworks
57
+
-[xUnit](https://xunit.github.io/)
54
58
55
-
The auto-generated `app.config` is configured to use [xUnit](https://xunit.github.io/). This can be changed as per the [SpecFlow Configuration Documentation](https://github.com/techtalk/SpecFlow/wiki/Configuration), however (at time of writing) no other test frameworks are available for .NET Core.
59
+
xUnit was the first cab off the rank with support for DNX and then .NET Core. Since then, MsTest and NUnit have become available. Support for these may be added in the future.
0 commit comments