An Assertion library for Should.js defining a descriptive object comparator indicating how two objects differ (i.e. which properties have been modified / deleted / added)
Accessibility (a11y) utilities for WordPress.
Form field description component for the Municipality of Utrecht based on the NL Design System architecture
A type-safe fluent assertion library
Assertive is a terse yet expressive assertion library
> A custom element for making announcements with live regions
Typings for the swc project.
lezer-based C++ grammar
minimalistic-assert ===
Node's event emitter for all engines.
Embedded JavaScript templates
The Material Components Web banner component.
Nice text table for the CLI
Code to parse and use Expo and Expo Updates manifests.
Utilities for reading JSONObjects (Android) and NSDictionaries (iOS).
minimal implementation of a PassThrough stream
A cross-platform React status indicator that pairs a coloured dot with an optional inline label.
A module for editing content inline using an accessible contenteditable implementation
two functions: One that returns true, one that returns false
walk paths fast and efficiently
Lexes CommonJS modules, returning their named exports metadata
A library to generate a fingerprint from a React Native project
Lexes ES modules returning their import/export metadata
TypeScript definitions for toastify-js
Shoulda macros for making very basic assertions about JSON responses
BRASS stands for Bare-Metal Ruby Assertion System Standard. It is a very basic foundational assertions framework for other assertion and test frameworks to make use so they can all work together harmoniously.
A method for very basic nested type assertions
minitest provides a complete suite of testing facilities supporting TDD, BDD, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. == Features/Problems: * minitest/autorun - the easy and explicit way to run all your tests. * minitest/test - a very fast, simple, and clean test system. * minitest/spec - a very fast, simple, and clean spec system. * minitest/benchmark - an awesome way to assert your algorithm's performance. * minitest/pride - show your pride in testing! * minitest/test_task - a full-featured and clean rake task generator. * Incredibly small and fast runner, but no bells and whistles. * Written by squishy human beings. Software can never be perfect. We will all eventually die.
Custom assertions functions. This is the beginning of a small lightweight BDD project. Currently, this is just a very simple code sample that only displays a custom message in green or in red depending on the value of a predicate.
A library of cucumber step definitions, which allow you to use a human to assert conditions during acceptance tests. Some requirements are simple for a human to confirm, but are very difficult to assert using automation. Farmer allows us to include human confirmation into our normal testing flow. For example, we needed to verify that certain portions of an image were 'blacked out'.
minitest-macruby provides extensions to minitest for macruby UI testing. It provides a framework to test GUI apps in a live instance. Documentation and examples are light at the moment as I've just thrown this together. Suggestions for extensions are very welcome! Currently it provides the following methods in minitest's assertions: * self.run_macruby_tests * find_ui_menu(*path) * find_ui_menu_items menu * assert_ui_menu menu, *items * find_ui_menu_item(*path) * assert_ui_action obj, target, action, key = nil * assert_ui_binding item, binding_name, target, path
With the happy proliferation of TDD, test suites are getting massive, and developer efficiency is dwindling as we wait for our tests to pass. There is a big tradeoff between making unit test more integrationish (and therefore more reliable) vs. making them very mocky, unity and fast. Mockumentary is a library for the later. It inspects the ActiveRecord universe and makes a series of AR mockeries that approximate model without hitting the database, or making any assertions. The assertions, they are still part of the developers job. Mocumentary has two types of AR mockeries: One is used within the Rails universe. It uses introspection to derive association and field information. The second is a static copy built from the first. This static version can be used outside the Rails test universe in a suite faster than the speed of Rails environment load time. Mocking isn't for everyone, so test-drive responsibly.