…zing events as Cucumber Messages.

…ecutionEvents to one or more Message Sinks. Default implementation of one Sink that serializes Messages to an ndjson file per feature.

Not finished: hooking up the TestThreadExecution event handlers.

…mber Messages Publisher and Broker to the initialization sequence provided by the Plugin architecture.

…est project. The File Sink is hooked in as a nuget package.

Next: exploratory debugging to confirm the event listeners are wired up correctly at Feature start time.

Need to figure out why trace logging also not working.

…check of whether it had been initialized (temp).

(Temp) - added Debugger.Launch to FileSinkPlugin to force launch of debugger.

…Publisher from the FileSinkPlugIn completely.

…the use of a BlockingCollection. Eliminated base class for Sinks. Eliminated use of Async for MessageSinks. Sinks have to ensure their own thread-safety and non-blocking behavior. May want to revisit that.

…ke Messages (meta, Source, GherkinDocument, and Pickles).

… information into Messages. First example is transforming StepBinding classes into messages of type StepDefinition.

…Generator.

…pport for CucumberMessages for that feature.

…e, then all are published.

…ioState emit sequences of Envelopes for consumption by the Publisher.

…fter scenario completion so that we have full binding Match info available to create the TestCase message.

… simple scenarios.

minimal and pending scenarios added.

… which I don't think apply to the .NET implementation.

Need to add support for images and documents as embedded resources to be added to generated test projects before attachments and hooks can be implemented and tested.
Not yet added infrastructure to compare output ndjon with expected.

…ly handle binary files.

Fails on undefined steps (but not specific to Hooks).
Made change to TestExecutionEngine to add Feature, Scenario, and Step context to the HookBinding events.

…n how they are rendered as TestStep messages.

…it centrally available.

NdJson files in CCK tests were moved out of assembly resource to be plain project content files.

Clean up of source files.

… logic.

… an 'Attachment'.

…ormations.

…ows an exception.

…rForRegularExpressionMatch to false (as these aren't used by Reqnroll).

Needs CI and Git info.
Needs to be refactored.

Refactored OS and CI information gathering out of AnalyticsEventProvider to EnvironmentWrapper.

Hooks partially work.

…ed event.

…nts (headers, rows, cells).

…s are properly parsed as DataTables by the Gherkin pickler.

…and ID.

Validates that top-level Messages match by Type and Count.

Introduced visitor pattern over the Messages types.

…or for all element types.

Source comparison complete.
Feature top-level properties comparison complete. (Feature Children next)

Fixed namespace mispelling in FileSinkPlugin (to match changes made in previous commit).
Temp fix: updated plug-in version reference to 2.2.0-local; need a way to fetch this from assembly.

Temp patch to Cucumber.Messages - with local build. Will need to revert to global nuget package when PR accepted by them.

Separate treatment of how hook-related TestStepFinished messages are handled.

FluentAssertion structural comparisons working for Cdata, hooks, minimal, parameter-types, pending, stack-traces, undefined, and unknown-parameter-type.
The remaining won't work until handling of DataTables is fixed.
Next: ID walking to test referential integrity.

…st step results statuses were mapped.

…le elements (headers, rows, cells)."

This reverts commit d9ada24.

…ST to patch in missing Location elements before the AST is transformed to the Cucumber GherkinDocument.

This duplicates the GherkinDocumentVisitor and ScenarioTransformation classes from the External Plugin (pending further refactoring).

Fixed: copy/paste error of using statement in Location Element transformer

… carry along the candidate BindingMatches that cause the ambiguity. These are used in the Step tracker and message factory to populate the array of StepDef Ids that cause the ambiguity.

… DocString from being rendered as StepMatchArguments. This allows for the DataTables CCK scenario to pass.

…ded to each test method at runtime (as a parameter for row tests, hard-coded by code-gen for regular tests). PickleStepIds are retrieved at run-time (given the PickleId and sequence of steps taken). The PickleID is stored in ScenarioInfo and the pickleStepId is provided to the Given/When/Then. These are wired into the relevant ExecutionEvents.

Minor refactoring to UnitTestMethodGenerator and ScenarioPartHelper - moved pickle generation to SPH.
Add new non-CCK scenario for Backgrounds

…e storage location of output and a flag to enable or disable execution.

…t is Enabled.

Fixed regressions in RuntimeTests.AnalyticsProviderTests

Fixed a defect that threw an exception when Source document is not available; not a critical error, so changed it to allow it to proceed with Pickle creation.
Revised tests to delete previous run .ndjson files.

…to Messages

…ements when testing generation.

Fixed MissingLocation patcher to include Feature and Scenario locations.
Enhanced Publisher to be more careful of handling of Feature-level enablement.

Added Location fixup to Tags, Features and Scenario elements to better support testability when tests set them as null as a convenience when setting up test data.
Added smoke test to include more than one feature per test.

…eadDependencies.

Check for null Feature Context on hooks that execute before a feature is started.

…count for step-less Scenarios.

…eded.

…o the TestExecutionEngine ExecuteStepAsync. it also calls NextStep on the pickleStepSequence.

In order to avoid assembly version conflicts, adding explicit assembly dependencies to the MSBuild.Generation nuspec.

…s. Will allow code gen and execution to continue without support for Messages.

…zing events as Cucumber Messages.

…ecutionEvents to one or more Message Sinks. Default implementation of one Sink that serializes Messages to an ndjson file per feature.

Not finished: hooking up the TestThreadExecution event handlers.

…mber Messages Publisher and Broker to the initialization sequence provided by the Plugin architecture.

…est project. The File Sink is hooked in as a nuget package.

Next: exploratory debugging to confirm the event listeners are wired up correctly at Feature start time.

Need to figure out why trace logging also not working.

…check of whether it had been initialized (temp).

(Temp) - added Debugger.Launch to FileSinkPlugin to force launch of debugger.

…Publisher from the FileSinkPlugIn completely.

…the use of a BlockingCollection. Eliminated base class for Sinks. Eliminated use of Async for MessageSinks. Sinks have to ensure their own thread-safety and non-blocking behavior. May want to revisit that.

…ke Messages (meta, Source, GherkinDocument, and Pickles).

… information into Messages. First example is transforming StepBinding classes into messages of type StepDefinition.

…Generator.

…pport for CucumberMessages for that feature.

…e, then all are published.