SpecFlow 1.2.0 released
37 views
Skip to first unread message
jbandi
Nov 28, 2009, 4:03:11 PM11/28/09
to SpecFlow Announcements
New features:
+ Generate #line pragmas to the output file (Issue 26)
+ Allow transformation of feature files from command-line and MsBuild
(Issue 3)
+ Merge all command-line tool (generation, reports) to a single
executable: specflow.exe
+ Support for Dutch and Swedish language
+ Support enumerations in step binding arguments (Issue 28)
Fixed issues:
+ MsTest does not refresh tests automatically (Issue 25)
+ Fixes in report localization
+ Non-string parameters for bindings are not converted using the
feature language (Issue 26)
Additional Info:
- we have a specflow.exe now, that can be used to execute all goodies
from command-line (generation, reports)
- the command-line for regenerate all is the following:
- usage: specflow.exe generateall projectFile [/force] [/verbose]
- you can also setup your project, to do this automatically on build:
it is smart:
on “build” only regenerates the files that are outdated (the .cs is
older than the .feature) or if there is a new specflow version
installed
on “rebuild” it regenerates all the files (but actually it touches
the files only if the new version is not the same)
o to do this, you have to add this line to the project file (with
notepad), after the CSharp.targets import:
<Import Project="C:\Program Files\TechTalk\SpecFlow
\TechTalk.SpecFlow.targets" />
- we are generating #line pragmas by default to the test files
o with that, you can debug the feature files!!! Try it out: set a
breakpoint to the feature file (on a step), and debug the test
o you can switch off this feature in the app.config:
<specFlow>
<generator allowDebugGeneratedFiles="true" />
</specFlow>
+ Generate #line pragmas to the output file (Issue 26)
+ Allow transformation of feature files from command-line and MsBuild
(Issue 3)
+ Merge all command-line tool (generation, reports) to a single
executable: specflow.exe
+ Support for Dutch and Swedish language
+ Support enumerations in step binding arguments (Issue 28)
Fixed issues:
+ MsTest does not refresh tests automatically (Issue 25)
+ Fixes in report localization
+ Non-string parameters for bindings are not converted using the
feature language (Issue 26)
Additional Info:
- we have a specflow.exe now, that can be used to execute all goodies
from command-line (generation, reports)
- the command-line for regenerate all is the following:
- usage: specflow.exe generateall projectFile [/force] [/verbose]
- you can also setup your project, to do this automatically on build:
it is smart:
on “build” only regenerates the files that are outdated (the .cs is
older than the .feature) or if there is a new specflow version
installed
on “rebuild” it regenerates all the files (but actually it touches
the files only if the new version is not the same)
o to do this, you have to add this line to the project file (with
notepad), after the CSharp.targets import:
<Import Project="C:\Program Files\TechTalk\SpecFlow
\TechTalk.SpecFlow.targets" />
- we are generating #line pragmas by default to the test files
o with that, you can debug the feature files!!! Try it out: set a
breakpoint to the feature file (on a step), and debug the test
o you can switch off this feature in the app.config:
<specFlow>
<generator allowDebugGeneratedFiles="true" />
</specFlow>
jbandi
Nov 28, 2009, 4:06:21 PM11/28/09
to SpecFlow Announcements
New features:
+ Generate #line pragmas to the output file (Issue 26)
+ Allow transformation of feature files from command-line and MsBuild
(Issue 3)
+ Merge all command-line tool (generation, reports) to a single
executable: specflow.exe
+ Support for Dutch and Swedish language
+ Support enumerations in step binding arguments (Issue 28)
Fixed issues:
+ MsTest does not refresh tests automatically (Issue 25)
+ Fixes in report localization
+ Non-string parameters for bindings are not converted using the
feature language (Issue 26)
Additional Info:
- we have a specflow.exe now, that can be used to execute all goodies
from command-line (generation, reports)
- the command-line for regenerate all is the following:
* usage: specflow.exe generateall projectFile [/force] [/verbose]
+ Generate #line pragmas to the output file (Issue 26)
+ Allow transformation of feature files from command-line and MsBuild
(Issue 3)
+ Merge all command-line tool (generation, reports) to a single
executable: specflow.exe
+ Support for Dutch and Swedish language
+ Support enumerations in step binding arguments (Issue 28)
Fixed issues:
+ MsTest does not refresh tests automatically (Issue 25)
+ Fixes in report localization
+ Non-string parameters for bindings are not converted using the
feature language (Issue 26)
Additional Info:
- we have a specflow.exe now, that can be used to execute all goodies
from command-line (generation, reports)
- the command-line for regenerate all is the following:
- you can also setup your project, to do this automatically on build:
* it is smart:
- on “build” only regenerates the files that are outdated
(the .cs is older than the .feature) or if there is a new specflow
version installed
- on “rebuild” it regenerates all the files (but actually it
version installed
touches the files only if the new version is not the same)
* to do this, you have to add this line to the project file (with
notepad), after the CSharp.targets import:
<Import Project="C:\Program Files\TechTalk\SpecFlow
\TechTalk.SpecFlow.targets" />
- we are generating #line pragmas by default to the test files
* with that, you can debug the feature files!!! Try it out: set a
<Import Project="C:\Program Files\TechTalk\SpecFlow
\TechTalk.SpecFlow.targets" />
- we are generating #line pragmas by default to the test files
breakpoint to the feature file (on a step), and debug the test
* you can switch off this feature in the app.config:
Reply all
Reply to author
Forward
0 new messages