Please enable JavaScript.

Coggle requires JavaScript to display documents.

BDD (Problems (Tools (Poor IDE support, Hard to mainain, Hard to debug),…

- - - - javascript
      - C#
      - php
      - Sample https://livestats-reports.s3.eu-west-2.amazonaws.com/basketball/allure/index.html#behaviors
      - Documentation:https://docs.qameta.io/allure/
    - - Demo: https://web.demo.reportportal.io/ui/
      - Documentation: https://reportportal.io/docs/Log-Data-in
      - Reports straigt to the site as test progresses
      - Ability to upload results via API/UI
    - - Currently not enabled (issue filed)
      - Ability to view html artifacts by hosting it on separate web server
      - Admin setup: https://docs.gitlab.com/ee/administration/pages/
      - Feature overview: https://about.gitlab.com/2017/10/22/gitlab-10-1-released/#online-view-of-html-artifacts
  - - - SpecFlow
        
        hard to maintain
        
        Other
        
        Ocassional clearing %temp% when can't bing the steps
        
        Cryptic regular expressions
        
        No built-in reporting
        
        Limited control over execution
        
        Allure Reports can be integrated
      - NBehave (dead?)
        
        Does not support .net Core
        
        Has VS plugin (year 2012)
        
        Similarly to SpecFlow uses step definitions
    - - Behavior based
        
        BDDfy
        
        General
        
        Reports
        
        Text
        
        Html
        
        Markdown
        
        No need for a separate test runner
        
        Not supported (last commit 3 years ago)
        
        Details
        
        One Story per Class
        
        Story Object
        
        Story metadata
        
        Scenarios
        
        Title
        
        Steps
        
        6 more items...
        
        Result
        
        Duration
        
        Result
        
        Not Executed
        
        Passed
        
        Not Implemented
        
        Inconclusive
        
        Failed
        
        Category
        
        Test Steps (methods)
        Supported types:
        
        Snake_Case
        
        camelCase
        
        PascalCase
        
        Scanners
        
        Story
        
        Scenario
        
        Step
        
        Processors
        
        Pipeline
        
        Console Reporter (Report): Displays the test result in the console.
        
        Exception Processor (Process Exceptions): Handles exceptions.
        
        Story Cache (Finally): Saves each Story for later processing by the Batch Processors.
        
        Disposer (Finally): Cleans up the Story and its Scenarios.
        
        Test Runner (Execute): Executes the tests.
        
        Processor Types:
        
        Firstly
        
        Execute
        
        Before Report
        
        Report
        
        After Report
        
        Process Exceptions
        
        Finally
        
        Batch processors
        
        Html Reporter
        
        Markdown Reporter
        
        Diagnostics reporter
        
        Fluent API
        (Given/When/Then Keywords)
        
        StoryQ (unmaintained)
        
        LightBDD
        
        Simillar to BBDfy
        
        Details
        
        Lifecycle options
        
        OnConfigure
        
        OnSetUp
        
        OnTearDown
        
        ReportWritersConfiguration() - Allows to configure reports that will be generated after all tests (described in Generating Reports section).
        
        CultureInfoProviderConfiguration() - Allows to configure culture that would be used to render feature/scenario/steps details.
        
        StepTypeConfiguration() - Allows to configure predefined step types and repeated step replacement (described in Scenario Steps Definition section). It allows also to specify a method determining if given lambda parameter name should be used as step type or not.
        
        ExecutionExtensionsConfiguration() - Allows to enable additional LightBDD extensions for scenario and step execution (described in Extending test behavior section).
        
        ExceptionHandlingConfiguration() - Allows to configure what failure scenario/step details are captured.
        
        NameFormatterConfiguration() - Allows to configure feature/scenario/step name formatting.
        
        ValueFormattingConfiguration() - Allows to configure default formatters used to format scenarios/step parameters.
        
        DependencyContainerConfiguration() - Allows to configure DI container used by LightBDD (described in DI Containers section).
        
        FeatureProgressNotifierConfiguration() - Allows to configure feature progress notification (described in Test Progress Notification section).
        
        ScenarioProgressNotifierConfiguration() - Allows to configure scenario progress notification (described in Test Progress Notification section).
        
        snake_case methods used as steps (by default)
        
        Feature
        
        Scenario
        
        Steps
        
        Composite Steps
      - Spec Based
        
        MSpec
        
        Runners
        
        Resharper
        
        mspec.exe
        
        Vstest.console.exe
        
        similar to Arrange-Act-Assert model
        
        Details
        
        Advanced Lifecycle Options
        
        IAssemblyContext
        
        OnAssemblyStart
        
        OnAssemblyComplete
        
        ICleanupAfterEveryContextInAssembly
        
        SetupForEachSpecification
        
        Uses custom delegates instead of attributes on methods
        
        Best Practices: https://github.com/machine/machine.specifications/wiki/Best-Practices
        
        Structure
        
        Subject
        
        Tags
        
        Establish
        
        Cleanup
        
        Because
        
        It
        
        Hard to write workflow scenarios
        
        Can't run tests in parrallel
        
        NSpec
        
        last commit 2 years ago
        
        No html reports
        
        Visual Studio Extension only for VS 2013, 2015
        
        Custom runner
        
        Weird syntax https://github.com/nspec/NSpec/wiki/Execution-Orders
        
        SpecsFor (unmaintained)