forked from kdfrie/SpecFlow.VisualStudio
-
Notifications
You must be signed in to change notification settings - Fork 0
/
changelog.txt
173 lines (109 loc) · 5.55 KB
/
changelog.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
Upcoming
+ Update nunit package reference in project templates
+ Fix specflow.json template to generate a valid configuration
+ Update MSTest package references in project templates
2019.0.83 - 2021-04-01
+ Update guidance sequence
2019.0.80 - 2021-02-17
+ Update project templates
2019.0.79 - 2021-02-16
+ Add all supported .NET Implementations in the Project Template Wizard
+ Update the feature file templates
2019.0.77 - 2021-01-25
+ Update the feature file templates
2019.0.76 - 2021-01-18
+ Fix styling issues in the Project Template Wizard
2019.0.71 - 2020-12-09
+ Fix: Renaming a step should not change the parameters
2019.0.68 - 2020-11-13
+ Add prerequisite for the SpecFlow project wizard
+ Marketplace release automation
2019.0.65 - 2020-10-16
+ Add FluentAssertions to project template
2019.0.58 - 2020-07-23
+ Add SpecFlow project template for Visual Studio 2017 and 2019
+ Fix ObjectDisposedException when opening and closing a second window for the same feature file
+ Changed default directory for generating steps file to the same directory as the .feature file
2019.0 - 2019-04-25
+ Add error message to generated code-behind when SpecFlow is not installed in the project
+ Improved error message when the SpecFlow version of generated code does not match the installed SpecFlow version
2017.3.0?- 2018/xx/xx
+ Remove Visual Studio 2013 support
+ Move SpecFlow item templates into their own category in "Add New Item" dialog
+ Create item template for "default.srprofile"
2017.2.8 - 2018/xx/xx
Bugfixes:
+ Fix Wrong text in step in feature file italicized https://github.com/techtalk/SpecFlow/issues/483
2017.2.7 - 2018/08/22
Bugfixes:
+ hopefully fix https://github.com/techtalk/SpecFlow/issues/1234
2017.2.6 - 2018/08/20
Bugfixes:
+ update CommandLineParser dependency
2017.2.5 - 2018/08/20
Bugfixes:
+ enhancment to error logging
2017.2.2 - 2018/07/25
New Features:
+ possibility to specific path to TechTalk.SpecFlow.VisualStudio.CodeBehindGenerator.exe
Bugfix:
+ fix encoding problems with special chars https://github.com/techtalk/SpecFlow/issues/1205
+ Add Newtonsoft.Json to VSIX
2017.2.1 - 2018/07/10
Changed behaviour:
+ Set out of process as default generation mode
2017.1.13 - 2018/03/30
New Features:
+ Add option to use an out of process tool to generate the code behind files
2017.1.12 - 2018/02/16
Public release to Visual Studio Marketplace
2017.1.11
Fixed issues:
+ Visual Studio 2017 Generation error: Could not load file or assembly 'Microsoft.Build.Framework, Version=15.1.0.0 - https://github.com/techtalk/SpecFlow/issues/857
2015.1.2 - 2015/05/26
Hotfix for release v2015.1
Fixed issues:
+ "Run SpecFlow Scenarios" does not work with ReSharper 9 (Issue 435)
2015.1.1 - 2015/05/06
Hotfix for release v2015.1
Fixed issues:
+ VS2013 Plugin 2015.1 doesn't find step bindings if there is a base class in other project (Issue 438)
2015.1.0 - 2015/04/30
Supports Visual Studio 2013 and 2015.
Compatible with SpecFlow v1.7 or later.
Fixed issues:
+ 'Go To Definition' does not work if StepArgumentTransformation is used for Table (Issue 340)
+ More stable discovery of step definitions
+ Fix issue for machines having .NET 4.6 installed
1.9.3 - 2013/09/26 (Visual Studio 2013 Integration)
Note: 1.9.3 only improved the Visual Studio integration, but uses the SpecFlow 1.9.0 runtime and generator.
New Features:
+ Visual Studio 2013 support (see http://www.specflow.org/documentation/Visual-Studio-2013-Integration/)
+ SpecRun 1.2 support: run/debug tests from the feature file editor
1.9.2 - 2013/03/25 (Visual Studio Integration update)
Note: 1.9.2 only improved the Visual Studio integration, but uses the SpecFlow 1.9.0 runtime and generator.
Fixed issues:
+ VS2010/VS2012: Visual Studio freezes while editing keywords (Issue 128)
+ VS2010/VS2012: Linked app.config now works (Issue 255, by ArildF)
+ VS2012: Run SpecFlow Scenarios didn't work in VS2012 Update 1 (Issue 273)
+ VS2012: Support execution of scenarios from editor, that are generated with <generator allowDebugGeneratedFiles="true" /> setting. (related to Issue 275)
The generator setting above can be used as a workaround for VS2012 test runner issues, for example that Scenario Outline and Example tables show up as "External"
+ VS2010/VS2012: Parameter is not colorized correctly when part of the keyword (Issue 276)
+ VS2010/VS2012: 'Go To Definition' does not work with partial classes (Issue 53)
+ VS2010/VS2012: ReSharper shortcuts (comment, go to definition, run test) do not work
+ VS2010/VS2012: Test class generation fails when installed SpecFlow and SpecFlow.CustomPlugin packages in one project (Issue 279)
New Features:
+ VS2010/VS2012: Table outlining support in the editor (Issue 244, by RaringCoder)
1.9.1 - 2012/10/12 (Visual Studio Integration update)
Note: 1.9.1 only improved the Visual Studio integration, but uses the SpecFlow 1.9.0 runtime and generator.
Fixed issues:
+ VS2012: Run specflow scenarios does not work: works as for RC, but still runs all scenarios from the file (Issue 210)
+ VS2010: VS stops showing context menus if code window contains C++ code (Issue 209)
+ VS2010: Use < and > around variables in Intellisense for steps (Issue 203)
+ VS2010: SpecFlow incorrectly detected changes in the configuration (Issue 215)
+ VS2008: Support for VB code generation
+ VS2010: Exception during project load
+ VS2010: InvalidComObjectException: COM object that has been separated from its underlying RCW cannot be used. (Issue 230)
+ VS2010/VS2012: improve stability, more tracing
1.9.0 - 2012/08/06
For detailed change log of versions 1.9.0 or earlier please check SpecFlow change log.