stajs/SpecFlow.NetCore issues and pull requests

#85 - Can you please add support for net core 3

Issue - State: closed - Opened by ssunkari almost 5 years ago - 2 comments

#84 - Version for package 'Specflow.NetCore' could not be resolved

Issue - State: closed - Opened by chinookproject over 5 years ago - 3 comments

#83 - Add .net core 2.1 target

Pull Request - State: closed - Opened by ajeckmans almost 6 years ago - 1 comment

#82 - Add SpecFlowVersion argument

Pull Request - State: closed - Opened by SlowLogicBoy almost 6 years ago - 1 comment

#81 - When specifying --specflow-path it doesn't detect SpecFlow Version.

Issue - State: closed - Opened by SlowLogicBoy almost 6 years ago

#80 - Different result locally and on CI server

Issue - State: closed - Opened by voroninp about 6 years ago - 3 comments

#79 - SpecFlow 2.4.0 does not work with Specflow.NetCore

Pull Request - State: closed - Opened by thomasbruggink about 6 years ago - 1 comment

#78 - Project not rebuilding when changing .feature file in VS 2017 (15.7.1)

Issue - State: closed - Opened by andrebires over 6 years ago - 3 comments

#77 - Use Project's namespace instead of SpecFlow.GeneratedTests

Issue - State: closed - Opened by ayoung over 6 years ago - 2 comments

#76 - Updated README.md

Pull Request - State: closed - Opened by DalSoft over 6 years ago - 1 comment

#75 - Added documentation for running SpecFlowNetCore cross platform

Pull Request - State: closed - Opened by DalSoft over 6 years ago - 2 comments

#74 - Building with Mono doesn't generate files.

Issue - State: closed - Opened by alexl0gan over 6 years ago - 3 comments

#73 - Added support for csproj's import tag.

Pull Request - State: closed - Opened by Soarc over 6 years ago - 1 comment

#72 - Linux path is case sensitive

Pull Request - State: closed - Opened by zdeneksejcek over 6 years ago - 1 comment

#71 - New NuGet package

Issue - State: closed - Opened by zdeneksejcek over 6 years ago - 2 comments

#70 - SpecFlow path compatibility fix for Linux and Mac systems

Pull Request - State: closed - Opened by zdeneksejcek over 6 years ago - 1 comment

#69 - Attempt to reduce the confusion of the project name

Issue - State: closed - Opened by stajs over 6 years ago - 7 comments

#68 - Updated handling of arguments

Pull Request - State: closed - Opened by dresdor over 6 years ago - 10 comments

#67 - Updated handling of Arguments with spaces

Pull Request - State: closed - Opened by dresdor over 6 years ago - 3 comments

#66 - Consider netcoreapp ONLY compatiblity

Issue - State: closed - Opened by smudge202 over 6 years ago - 2 comments

#65 - Error in SpecFlow.NetCore tool during print messages

Issue - State: closed - Opened by aensidhe over 6 years ago - 15 comments

#64 - adding Links items to be discovered

Pull Request - State: closed - Opened by cheesemacfly almost 7 years ago - 3 comments

#63 - does not work with SpecFlow 2.2.1

Issue - State: closed - Opened by MovGP0 almost 7 years ago - 5 comments

#62 - Get SpecFlow tool version from csproj file

Pull Request - State: closed - Opened by oakio almost 7 years ago - 1 comment

#61 - .net core 2.0 (CLI)

Issue - State: closed - Opened by AbrahamAlcaina almost 7 years ago - 2 comments

#60 - Update SpecFlow.NetCore version in README.md

Pull Request - State: closed - Opened by TimMurphy almost 7 years ago - 1 comment

#59 - Make tools version configurable

Pull Request - State: closed - Opened by TimMurphy almost 7 years ago - 4 comments

#58 - Fixed fail during Fix() caused build to fail

Pull Request - State: closed - Opened by freljung almost 7 years ago - 1 comment

#57 - Build fails when there is an existing fake.csproj file (or any extra csproj file)

Issue - State: closed - Opened by freljung almost 7 years ago - 4 comments

#56 - Tools version is unsupported

Issue - State: closed - Opened by TimMurphy about 7 years ago - 6 comments
Labels: help wanted

#55 - Fixed the regex for removing MSTest descriptions

Pull Request - State: closed - Opened by thomasbruggink about 7 years ago

#54 - Scenarios break when the name is too long

Issue - State: closed - Opened by thomasbruggink about 7 years ago - 1 comment

#53 - dotnet SpecFlow.NetCore does not work on linux

Issue - State: closed - Opened by estaphorsius about 7 years ago - 6 comments

#52 - Do not hardcode to SpecFlow 2.1.0

Issue - State: closed - Opened by skorunka about 7 years ago - 2 comments

#51 - Support for relative paths

Pull Request - State: closed - Opened by kant2002 about 7 years ago - 2 comments

#50 - Made change required for working with .NET Core 2.0

Pull Request - State: closed - Opened by kant2002 about 7 years ago - 1 comment

#49 - Tools version is unsupported

Issue - State: closed - Opened by MovGP0 about 7 years ago - 3 comments

#48 - dotnet core 2.0 support

Issue - State: closed - Opened by alastairtree about 7 years ago - 5 comments

#47 - steps in folder are not binding

Issue - State: closed - Opened by kongres over 7 years ago - 5 comments

#46 - testing a dotnet core class library with Specflow

Issue - State: closed - Opened by jimdeane over 7 years ago - 4 comments

#45 - This repo is misleading

Issue - State: closed - Opened by gegana over 7 years ago - 5 comments

#44 - Updated readme and package version for migration to csproj tooling

Pull Request - State: closed - Opened by richardjharding over 7 years ago - 1 comment

#43 - Convert to cs proj

Pull Request - State: closed - Opened by richardjharding over 7 years ago - 3 comments

#42 - Is it possible to take this aprroach with latest tooling 1.0.0-preview3-004056

Issue - State: closed - Opened by richardjharding over 7 years ago - 21 comments

#41 - attempts to resolve latest specflow version to assist with #40

Pull Request - State: closed - Opened by smudge202 almost 8 years ago - 3 comments

#40 - Missing SpecFlow 2.1.0

Issue - State: closed - Opened by georgeonofrei almost 8 years ago - 7 comments

#39 - Sample project without net461 framework

Issue - State: closed - Opened by akmn almost 8 years ago - 1 comment

#38 - Importing external bindings doesn't seem to work

Issue - State: closed - Opened by erik-am almost 8 years ago - 3 comments
Labels: can't-fix

#37 - 'test-nunit' returned '-100'.

Issue - State: closed - Opened by ghost almost 8 years ago - 5 comments

#36 - Scenario Outline tests are correctly categorized

Pull Request - State: closed - Opened by erik-inkapool almost 8 years ago - 1 comment

#35 - Updated readme and added sample projects for supported test frameworks

Pull Request - State: closed - Opened by erik-inkapool almost 8 years ago - 1 comment

#34 - MsTest doesn't categorize correctly in test explorer for Scenario Outlines

Issue - State: closed - Opened by erik-inkapool almost 8 years ago - 1 comment

#33 - How to install specflow for .net core?

Issue - State: closed - Opened by milla about 8 years ago - 7 comments

#32 - Doesn't honor the NUGET_PACKAGES environment variable

Issue - State: closed - Opened by alexsaare about 8 years ago - 7 comments

#31 - Added support for multiple test frameworks

Pull Request - State: closed - Opened by erik-inkapool about 8 years ago - 6 comments

#30 - Other test frameworks

Issue - State: closed - Opened by smudge202 about 8 years ago - 7 comments

#29 - Consolidate formatting settings

Issue - State: closed - Opened by smudge202 about 8 years ago - 4 comments

#28 - Added warning when generating new files

Pull Request - State: closed - Opened by erik-inkapool about 8 years ago - 3 comments

#27 - Restore "Test is pending" message

Issue - State: closed - Opened by erik-inkapool about 8 years ago - 31 comments
Labels: can't-fix

#26 - Fix project.json framework targets

Pull Request - State: closed - Opened by erik-inkapool about 8 years ago - 1 comment

#25 - Emit warning if a new file is created

Issue - State: closed - Opened by stajs about 8 years ago

#24 - Clarification of RTM project.json

Issue - State: closed - Opened by smudge202 about 8 years ago - 6 comments

#23 - Update readme for dotnetcore

Issue - State: closed - Opened by erik-inkapool about 8 years ago - 2 comments

#22 - New test files require rebuild to be picked up by VS Test explorer

Issue - State: closed - Opened by erik-inkapool about 8 years ago - 15 comments
Labels: can't-fix

#21 - Rename DNX ->NetCore

Issue - State: closed - Opened by stajs about 8 years ago

#20 - Dotnetcore

Pull Request - State: closed - Opened by erik-inkapool about 8 years ago - 1 comment

#19 - Update to dotnet core 1.0.0

Issue - State: closed - Opened by erik-inkapool about 8 years ago - 12 comments
Labels: enhancement

#18 - Error with sample project of SpecFlow.Dnx and french localization

Issue - State: closed - Opened by GregH44 over 8 years ago - 2 comments

#17 - Tags don't generate traits

Issue - State: closed - Opened by smudge202 over 8 years ago - 2 comments

#16 - Update samples for SpecFlow 2.0

Issue - State: closed - Opened by stajs over 8 years ago - 3 comments

#15 - added support for SpecFlow 2.0.0

Pull Request - State: closed - Opened by revlucio over 8 years ago - 3 comments

#14 - Error on Visual Studio Team Services

Issue - State: closed - Opened by devdigital over 8 years ago - 2 comments

#13 - Allows for use of Scenario Outlines in SpecFlow with Xunit 2.0

Pull Request - State: closed - Opened by bowman-jm almost 9 years ago - 1 comment

#12 - Support Scenario Outlines

Issue - State: closed - Opened by bowman-jm almost 9 years ago - 9 comments

#11 - Should samples mimic the specflow samples?

Issue - State: closed - Opened by smudge202 almost 9 years ago - 5 comments

#10 - Figure out if moving to net40 is a good thing

Issue - State: closed - Opened by stajs almost 9 years ago - 4 comments

#9 - Features/8 dnx451 samples

Pull Request - State: closed - Opened by smudge202 almost 9 years ago - 5 comments

#8 - dnx451 samples

Issue - State: closed - Opened by smudge202 almost 9 years ago - 3 comments

#7 - Features/6 dnx compatibility

Pull Request - State: closed - Opened by smudge202 almost 9 years ago - 10 comments

#6 - dnx451 compatibility

Issue - State: closed - Opened by smudge202 almost 9 years ago - 2 comments

#5 - Features/2 readme update

Pull Request - State: closed - Opened by smudge202 almost 9 years ago - 4 comments

#4 - The 'prebuild' script failed with status code 1

Issue - State: closed - Opened by radwane-h almost 9 years ago - 10 comments

#3 - Generate Step Definitions

Issue - State: closed - Opened by smudge202 almost 9 years ago - 5 comments

#2 - README Update for xunit tips

Issue - State: closed - Opened by smudge202 almost 9 years ago - 3 comments

#1 - Prebuild step not firing

Issue - State: closed - Opened by DenisBiondic almost 9 years ago - 6 comments

GitHub / stajs/SpecFlow.NetCore issues and pull requests