blocks|key|2534448|text|请允许我推荐一个替代方案--+Xunit.Gherkin.Quick。当我发现SpecFlow与.NET核心不兼容时，我写了这篇文章，我需要在.NET核心中使用Xunit进行基于小黄瓜的BDD测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2534449|除了与.NET核心和常规.NET兼容(因为它是一个.NET标准库)，它的工作方式几乎与specflow类似：|2534450|2534451|支持带有小黄瓜语言的功能文件。|unordered-list-item|2534452|为您提供了给定的/When/Then等属性来实现方案步骤。|2534453|2534454|与SpecFlow相比，它不能做的是：|2534455|2534456|它不会基于特征文件自动为您生成空的给定/当/则等方法。相反，您需要从Feature基类派生并手动编写场景步骤。(我认为手动编写带有属性的方法签名没什么大不了的)|2534457|它只支持Xunit，不支持其他测试框架。|2534458|2534459|在我看来可以接受的折衷方案。|2534460|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ttutisani/Xunit.Gherkin.Quick^0|F|J|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|19|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|1A|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|1B|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]|$1|P|3|Q|5|I|7|1F|8|@]|9|@]|C|$]]|$1|R|3|S|5|I|7|1G|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|1I|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

Allow me suggest an alternative - <a href="https://github.com/ttutisani/Xunit.Gherkin.Quick" rel="noreferrer">Xunit.Gherkin.Quick</a>. I wrote it when I discovered that SpecFlow is not compatible with .NET Core, and I needed to do Gherkin based BDD tests in .NET Core with Xunit.

Besides being compatible with .NET Core and regular .NET too (since it's a .NET Standard library), it works almost like specflow:

<ul>
<li>Supports feature files with Gherkin language in it.</li>
<li>gives you Given/When/Then etc. attributes to implement scenario steps.</li>
</ul>

What it does not do, compared to SpecFlow:

<ul>
<li>It does not automatically generate empty Given/When/Then etc. methods for you based on feature file. Instead, you need to derive from Feature base class and write scenario steps manually. (I think not a big deal to manually write a method signature with attribute on it)</li>
<li>It only supports Xunit and no other test frameworks.</li>
</ul>

Acceptable compromise in my opinion.

blocks|key|2534440|text|来自Their+website:|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2534441|目前尚不支持|2534442|+.NET核心，但我们正在努力。|blockquote|2534443|2534444|entityMap|0|LINK|mutability|MUTABLE|url|http://specflow.org/documentation/.NET-Support/^0|2|E|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|W|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

From <a href="http://specflow.org/documentation/.NET-Support/" rel="nofollow noreferrer">Their website:</a>

<blockquote>
 .NET Core is not yet supported, but we are working on it.
</blockquote>

blocks|key|622328|text|现在有了支持.NET核心的preview+version+of+SpecFlow+3。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|622329|entityMap|0|LINK|mutability|MUTABLE|url|https://specflow.org/2018/specflow-3-public-preview-now-available/^0|D|T|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There is now a <a href="https://specflow.org/2018/specflow-3-public-preview-now-available/" rel="nofollow noreferrer">preview version of SpecFlow 3</a> available with support for .NET Core.

blocks|key|2534478|text|SpecFlow+3支持.NET核心：SpecFlow+3|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2534479|entityMap|0|LINK|mutability|MUTABLE|url|https://specflow.org/2019/specflow-3-is-here/^0|J|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

SpecFlow 3 supports .NET Core: <a href="https://specflow.org/2019/specflow-3-is-here/" rel="nofollow noreferrer">SpecFlow 3</a>

blocks|key|630600|text|来自Their+website|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|630601|630602|从.NET核心项目中的SpecFlow功能文件生成测试。|blockquote|630603|630604|630605|在包管理器控制台中插入此命令|630606|PM>+Install-Package+SpecFlow.NetCore+-Version+1.3.2|code-block|syntax|javascript|630607|entityMap|0|LINK|mutability|MUTABLE|url|https://www.nuget.org/packages/SpecFlow.NetCore/^0|2|D|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|13|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|14|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|15|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@]|C|$]]|$1|L|3|M|5|N|7|17|8|@]|9|@]|C|$O|P]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

From <a href="https://www.nuget.org/packages/SpecFlow.NetCore/" rel="nofollow noreferrer">Their website</a>:

<blockquote>
 Generate tests from SpecFlow feature files inside .NET Core projects.
</blockquote>

Insert this command in Package Manager Console

<pre><code>PM&gt; Install-Package SpecFlow.NetCore -Version 1.3.2
</code></pre>

I need to install nuget package SpecFlow 2.1.0 on .net core 2.0 project but i get issue.

<img src="https://i.stack.imgur.com/W82qb.png" alt="enter image description here">

SpecFlow on .net core 2.0

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我需要在.net Core2.0项目上安装nuget package SpecFlow 2.1.0，但是我得到了问题。​​

问.net Core2.0上的SpecFlow
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.net Core2.0上的SpecFlowEN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.net Core2.0上的SpecFlow
EN