Results for wrap-bdd

a behavior driven development framework for test complete projects and any other testing projects

generator to create base structure for end users of wrap-bdd package

BDD Testing with Playwright runner

Wordwrap a string with ANSI escape codes

Wrap words to a specified length.

Helper to wrap functions inside a function call.

A tiny and fast text wrap library which takes ANSI escapes into account.

Wrap words to a specified length.

Wrap those words. Show them at what columns to start and stop.

A library to create, minimize and optimize binary decision diagrams

Serenity/JS reporting module that produces detailed Serenity BDD test reports and living documentation, enhancing transparency and traceability of test results

Wrap all spawned Node.js child processes by adding environs and arguments ahead of the main JavaScript file argument.

PostCSS plugin to replace overflow-wrap with word-wrap or optionally retain both declarations.

Provides "ui" for testing frameworks such as mocha/jasmine which allows to define lazy variables and subjects

A11y tests for chai

A WebdriverIO plugin. Adapter for Mocha testing framework.

assertion library

ESLint plugin with rules to lint BDD specs.

Encode and decode base64 encoded strings

CodeceptJS helper for chai library

Create ansi colors by passing the open and close codes.

An Error subclass that will chain nested Errors and dump nested stacktraces

Encode and decode quoted-printable strings according to rfc2045

CodeceptJS Saucelabs Integration

Problem: While Cucumber is an awesome tool, for some kinds of tests it's default behaviour becomes an obstacle. Testing large batches of input against a slow error prone system is the source of much frustration. Cucumber will skip remaining steps on failure or error. This is especially problematic if the test input is a dynamic collection, *(e.g. results of a database query). This is opposed to a static collection testing which is solved by a Scenario Outline. Solution: We need to step putside Cucumber's default pass/fail/error handling. Capture all failures and errors in collections. Log errors and failures. Generate a pass/fail manifest against the test inputs. Do not use this for normal BDD style testing, Cucumber's default behaviour is perfect for that. Public Interface: This is a works in progress so I expect changes as usage reveals more. In your cucumber env.rb Before do |scenario| setup_unstoppable end After do |scenario| print unstoppable_failures(scenario) print unstoppable_errors(scenario) end In a step definition wrap any operation that you do not wish to stop execution like so unstoppable do expect(thing).to be(exected_thing) end This helper method does the following: runs executes the block catches any exception 2a. adds error to errors collection if an error 2b. adds expectation failure to failures collection if error is an RSpec::Expectations::ExpectationNotMetError logs error/failure