Closed 304NotModified closed 4 years ago
I think the answer is currently not :)
I've made a PR for date support, some guidance would be great. -> https://github.com/SpecFlowOSS/SpecFlow/pull/1958
If merged, I could also made a PR for datetimes.
Thanks for the PR. But at the moment it wouldn't change anything. AFAIK the SpecFlow VS extension is calling the code in the used SpecFlow 1.9 in the extension and not the version that is used in the project. And updating the SpecFlow version in the VS Extension is a lot of work that we didn't do in the last years.
We started the work on it (https://github.com/SpecFlowOSS/SpecFlow.VisualStudio/tree/update_specflow_version) but never finished it.
That's a bummer!
Could we still merge the PR? I think it's good and that's another reason to get the VS extension up-to-date. Maybe I have time to check it then.
The PR is merged @304NotModified. As written there, this PR increased my motivation to find a solution for the Visual Studio Extension and its old SpecFlow version.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
SpecFlow Version:
Used Test Runner
Version number:
Project Format of the SpecFlow project
packages.config
<PackageReference>
tags.feature.cs files are generated using
SpecFlow.Tools.MsBuild.Generation
NuGet packageSpecFlowSingleFileGenerator
custom toolVisual Studio Version
Enable SpecFlowSingleFileGenerator Custom Tool
option in Visual Studio extension settingsAre the latest Visual Studio updates installed?
<Major>.<Minor>.<Patch>
.NET Framework:
Test Execution Method:
<SpecFlow> Section in app.config or content of specflow.json
none
Repro Project
Issue Description
Is there a date format in the scenario which is recognized as date?
Steps to Reproduce
Tested these examples:
And that will give:
So int/string and no datetimes