|
1 | 1 | ##V4 In Development |
2 | 2 |
|
3 | 3 | ####Improvements |
4 | | - - [#61](https://github.com/TestStack/TestStack.BDDfy/pull/61) & [#62](https://github.com/TestStack/TestStack.BDDfy/pull/62) - rationalized BDDfy namespaces to require less namespaces for some features and to make features more discoverable |
5 | | - |
6 | | -**Breaking Change** |
7 | | - |
8 | | -Some long namespaces were removed from the framework so the API becomes more discoverable. You just need to delete the now-removed namespaces from your using statements. |
9 | | -Also the `Reporters` namespaces that you would use when configuring BDDfy's reports through the `Configurator` class has been moved around to the root namespace. |
10 | | - |
11 | | - - [#63](https://github.com/TestStack/TestStack.BDDfy/pull/63) - renames a number of types to more accurately reflect their role and usage |
12 | | - |
13 | | -**Breaking Change** |
14 | | - |
15 | | - - renames ExecutionStep to Step & its StepTitle to Title |
16 | | - - renames StepExecutionResult to Result |
17 | | - - renames StepAction in Step to Action |
18 | | - - moves RunStepWithArgs from root to StepScanners |
19 | | - - renames MetaData to Metadata everywhere |
20 | | - - moves StoryMetadata to Scanners folder |
| 4 | + - [#61](https://github.com/TestStack/TestStack.BDDfy/pull/61) & [#62](https://github.com/TestStack/TestStack.BDDfy/pull/62) - rationalized BDDfy namespaces to require less namespaces for some features and to make features more discoverable. **Breaking Change** |
| 5 | + - Some long namespaces were removed from the framework so the API becomes more discoverable. You just need to delete the now-removed namespaces from your using statements. |
| 6 | + - The `Reporters` namespaces that you would use when configuring BDDfy's reports through the `Configurator` class has been moved around to the root namespace. |
| 7 | + |
| 8 | + - [#63](https://github.com/TestStack/TestStack.BDDfy/pull/63) - renames a number of types to more accurately reflect their role and usage. **Breaking Change** |
| 9 | + - renames ExecutionStep to Step & its StepTitle to Title |
| 10 | + - renames StepExecutionResult to Result |
| 11 | + - renames StepAction in Step to Action |
| 12 | + - moves RunStepWithArgs from root to StepScanners |
| 13 | + - renames MetaData to Metadata everywhere |
| 14 | + - moves StoryMetadata to Scanners folder |
21 | 15 |
|
22 | 16 | - [#67](https://github.com/TestStack/TestStack.BDDfy/pull/67) - makes `StoryMetadata` generic to allow different story narratives |
23 | 17 | - [#71](https://github.com/TestStack/TestStack.BDDfy/pull/71) - adds `ResolveJqueryFromCdn`config point for resolving jquery thru CDN or embedding it |
24 | 18 | - [#72](https://github.com/TestStack/TestStack.BDDfy/pull/72) - minifies bddfy .css and .js files to make HTML report smaller and the source more readable |
25 | | - - [#80](https://github.com/TestStack/TestStack.BDDfy/pull/80) - removes .net 3.5 support |
26 | | - |
27 | | -**Breaking Change** |
28 | | - |
29 | | -BDDfy V4 won't support .Net 3.5. So if you want to feel all the love that's coming to V4 you should upgrade to .Net 4+. |
| 19 | + - [#80](https://github.com/TestStack/TestStack.BDDfy/pull/80) - removes .net 3.5 support. **Breaking Change** |
| 20 | + - BDDfy V4 won't support .Net 3.5. So if you want to feel all the love that's coming to V4 you should upgrade to .Net 4+. |
30 | 21 |
|
31 | 22 | ####New Features |
32 | 23 | - [#81](https://github.com/TestStack/TestStack.BDDfy/pull/81) - adds ability to do inline assertions and title only steps using the fluent API |
|
0 commit comments