Solution for easy integration/end-to-end test with React
A Babel preset that enables parsing of proposals supported by the current Node.js version.
All change-case methods bundled in a single module
HTML5 2d canvas library.
Convert between various world calendars
A ridiculously light-weight argument validator (now browser friendly)
Typings for the swc project.
Cross Platform Smart Fetch Ponyfill
A Test-Anything-Protocol library for JavaScript
SerialPort Hardware bindings for node serialport written in c++
Starts server, waits for URL, then runs test command; when the tests end, shuts down server
Simple, transparent parser combinators toolkit that supports any tokens
concurrent or serial run npm scripts, javascript tasks, and more
fs read and write streams based on minipass
An evented streaming XML parser in JavaScript
Variant of merge that's useful for webpack configuration
fs read and write streams based on minipass
prelude.ls is a functionally oriented utility library. It is powerful and flexible. Almost all of its functions are curried. It is written in, and is the recommended base library for, LiveScript.
TON transaction emulator
Collects all values from an async iterator, sorts them using the passed function and yields them
micromark utility to resolve subtokens
Merges multiple JUnit XML reports into one.
Recursively resolve JSON pointers and remote authorities.
Collects all values from an (async) iterable and returns them as an array
#set(), speed-up your specs
Custom formatter for xcpretty that saves on a JSON file all the errors, warnings and test failures, so you can process them easily later.
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
Knapsack Pro wraps your current test runner(s) and works with your existing CI infrastructure to parallelize tests optimally. It dynamically splits your tests based on up-to-date test execution data. It's designed from the ground up for CI and supports all of them.
One test that dominates them all
Makes some failing tests for you
Maily is a Rails Engine to manage, test and navigate through all your email templates of your app, being able to preview them directly in your browser.
Control your tests, run them parallel. Check statuses of your revisions online. Share results to all team members.
A test helper that removes `ActiveSupport::Deprecation` noise from being interlaced in your test output. Instead this gem collects any and all deprecation warnings that occur during your tests, and succinctly reports them at the end of the test run.
With this library you can catch all outgoing e-mails and redirect them to a specific address. This is very useful for testing purpose, for example on your staging/testing server.
A Hyperloop application consists of isomorphic React Components, Active Record Models, Stores, Operations and Policiespec. Test them all from Rspec, regardless if the code runs on the client or server.
It launches and interacts with a set of services from a single terminal window. * Colorizes output for each process to help distinguish them. * Useful for integration-test applications where you need to start up several processes and test them all. * Built because servolux wasn't working very well for me. * Can detect exactly when a service is successfully launched by watching the output of the process.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.