LightBDD changelog

Changelog History

• v3.2.0 Changes

  May 23, 2020

  📦 #206 Added explicit netstandard2.0 support for all LightBDD packages to simplify dependency resolution graph
  ⚡️ #210 Updated Fixie version to 2.2.1
  ⚡️ #210 Updated MSTest.TestFramework version to 2.1.1
  ⚡️ #210 Updated NUnit version to 3.12.0
  ⚡️ #210 Updated xunit version to 2.4.1

• v3.1.1 Changes

  October 31, 2019

  📜 #181 Improved compact step parsing and rendering
  📜 #182 Made step parsing issues easily discoverable
  🛠 #185 Fixed: Using skip feature with XUnit InlineData attribute throws InvalidOperationException
  🔧 #187 Improved disposal behavior of pre-configured DI containers
  #199 Improved Html/Xml/Text reports to present scenarios orderly manner
  📦 #202 Migrated symbol packages to snupkg in order to remove https://nuget.smbsrc.net dependency

• v3.1.0 Changes

  August 19, 2019

  🚀 This release includes:
  #191 (Core)(Change) Expanded IScenarioInfo, IStepInfo with Parent property
  #191 (Core)(Change) Expanded IFeatureInfo, IScenarioInfo, IStepInfo with RuntimeId property
  ⚡️ #191 (Framework)(Change) Updated XmlReportFormatter to include RuntimeId

• v3.0.1 Changes

  January 16, 2019

  🚀 This release include:
  #177 Scenarios built fluently are not executed properly

• v3.0.0 Changes

  January 13, 2019

  • 🚚 #152 Removed obsolete code
  • #152 Unified scenario extensions
    • Unified scenario extension namespaces to LightBDD.Framework.Scenarios
    • Removed RunScenarioActionsAsync() method in favor of Runner.AddSteps(/*async void*/).RunAsync()
    • Removed Runner.NewScenario() in favor of Runner being fluent by default
  • 🔧 #152 Unified configuration namespaces to either LightBDD.Core.Configuration or LightBDD.Framework.Configuration
  • #152 Reworked framework-core abstractions
  • #157 Signed all assemblies except LightBDD.Fixie2
  • ⚡️ #163 Updated DefaultExceptionFormatter to exclude "End of stack trace" lines
  • ⚡️ #165 Updated basic syntax compiler to not accept compiler generated methods
  • 🚚 #170 Removed LightBDD.NUnit2
  • #174 Allowed IgnoreScenarioAttribute on class level to ignore all scenarios in given feature.

  More on What Is New wiki page

• v2.5.0 Changes

  December 02, 2018

  #60 Implemented Project Templates in VSIX extension
  #61 Implemented snippets for scenario and composite steps in VSIX extension
  #148 Expect.To.BeAnyTrue() with no sub-expectations should fail
  ⚡️ #153 Updated dotnet test examples for xunit2 to reflect the newest framework changes
  #156 Implemented compact step syntax allowing inline step definitions
  ⚡️ #160 Updated Fixie dependency to v2.0.2 to detect tests in VS 15.8 and higher

• v2.4.3 Changes

  September 12, 2018

  #145 NULL value not assignable to Nullable<bool> parameter

• v2.4.2 Changes

  August 19, 2018

  #127 Features gets reported multiple times (LightBDD.XUnit2)
  ✅ #128 Implement proper test progress capture in parallel LightBDD.MsTest2 scenarios
  #134 Capability of protecting shared state from being used without former initialization
  #135 Integrate with sourcelink
  🐧 #137 Unable to specify absolute path to report location on Linux

• v2.4.1 Changes

  July 16, 2018

  #122 Provided integration with DI containers implementing Microsoft DI abstractions
  #123 Improved experience with running parameterized scenarios in LightBDD.XUnit2

• v2.4.0 Changes

  July 11, 2018

  #38 (all)(New) Added ability to specify verifiable parameters
  #38 (all)(New) Added Expect.To.* expectation expressions
  👍 #59 (Core)(New) Added support for DI container
  0️⃣ #59 (Framework)(New) Implemented default DI container
  #59 (Autofac)(New) Added LightBDD.Autofac integration for Autofac DI container
  #67 (Fixie)(New) Added LightBdd.Fixie2 integration project with https://github.com/fixie/fixie
  #70 (all)(New) Added InlineTable, VerifiableDataTable, TableValidator classes to represent tabular step method parameters and Table class to create them
  ✅ #117 (XUnit2)(New) Added experimental ClassCollectionBehavior attribute allowing inter-class test parallelization
  #120 (Framework)(Fix) StepExecution.Current.Comment() does not work after leaving sub-step in composite step