Easy test setup without side effects
Provides "ui" for testing frameworks such as mocha/jasmine which allows to define lazy variables and subjects
Jest plugins to emulate RSpec syntax and structure.
steps ui component for react
Damerau - Levenshtein distance by The Spanish Inquisition + relative distance
steps ui component for react
Adds context as an alternative to describe to jest.
Azure Storage Common Client Library for JavaScript
Core library for shared utility methods
react animation library
TBD
Core logic for the steps widget implemented as a state machine
Provides low-level interfaces and helper methods for tracing in Azure SDK
Adds a Given-When-Then DSL to jasmine as an alternative style for specs
Distributed test runner using Redis as a work queue. Push file paths to a Redis list, then multiple CI runners atomically steal batches and execute them via a configurable command.
Super simple DI for JavaScript, targetted mainly at spec test setup
Rotate an array by a given number of steps
Core library for interacting with XML payloads
Core library for interfacing with AutoRest generated code
Core library for interfacing with Azure Rest Clients
Common internal functionality for all of the Azure Key Vault clients in the Azure SDK for JavaScript
Memoization for Mocha/Jasmine specs (like RSpec's #let)
Requirements:
Get CI environment variables for parallelizing builds
A minimal implementation of integration testing within RSpec. Allows you to build sequential specs, each with a description, but where state is maintained between tests and before/after actions are only triggered at the beginning and end of the entire sequence. Cool things you can do with this: * Build multi-step user stories in plain RSpec syntax. Locate the point of failure quickly, and break up large integrations into sensible steps * Speed up groups of related tests by running your factories only once before the whole group.
Given/When/Then steps for RSpec examples
I don't like Cucumber. I don't need plain text stories. My clients either read code or don't read any test documents, so Cucumber is mostly useless. But often, especially in full integration tests, it would be nice to have steps in a test.
Setup Rspec for Rails environment including all configurations and command line inputs required. Once the setup is ran, user can start run spec files without any further configurations.
RSpec matchers and Cucumber steps for testing JSON content
I don't like Cucumber. I don't need plain text stories. My clients either read code or don't read any test documents, so Cucumber is mostly useless to me. But often, especially in full integration tests, it would be nice to have steps in a test.
Leverages json_spec to test structured protocol buffers with json data modeling
Provides the ability to define steps and run Gherkin files from with RSpec
common_steps. Some common cucumber step definitions, rake tasks, and rspec matchers
RSpec & Cucumber for Data Examination
SMS Spec gives you an RSpec DSL and Cucumber steps to test SMS interactions.
Build and Inspect FIX Messages with RSpec and Cucumber steps