AWS credential provider that sources credentials from a Node.JS environment.
AWS credential provider for containers and HTTP sources
AWS credential provider that sources credential_process from ~/.aws/credentials and ~/.aws/config
Babel helper to create your own polyfill provider
AWS credential provider that sources credentials from ~/.aws/credentials and ~/.aws/config
AWS credential provider that sources credentials from the EC2 instance metadata service and ECS container metadata service
AWS credential provider that calls STS assumeRole for temporary AWS credentials
AWS credential provider that exchanges a resolved SSO login token file for temporary AWS credentials
GrowthBook provider for the Flags SDK
AWS credential provider that sources credentials from known environment variables
Utility to wait for a TCP port to open.
A collection of token providers
No description provided.
Simple and complete DOM testing utilities that encourage good testing practices.
No description provided.
Simple and complete React DOM testing utilities that encourage good testing practices.
Runtime agnostic JS utils
[](https://www.npmjs.com/package/@aws-sdk/credential-provider-cognito-identity) [ allows the use of a wide variety of AI models and providers.
Custom jest matchers to test the state of the DOM
Alephium Provider for WalletConnect Protocol
The **[OpenAI provider](https://ai-sdk.dev/providers/ai-sdk-providers/openai)** for the [AI SDK](https://ai-sdk.dev/docs) contains language model support for the OpenAI chat and completion APIs and embedding model support for the OpenAI embeddings API.
Fire events the same way the user does
This framework uses Ruby, Rake and a local instance of the SFCB CIMOM to run tests against CIM providers
Shared classes and tests for fog providers and services.
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.
This gem facilitates modeling a test suite that is written in Gherkin (e.g. Cucumber, SpecFlow, Lettuce, etc.). It does this by providing an abstraction layer on top of the Abstract Syntax Tree that the 'cucumber-gherkin' gem generates when parsing features, as well as providing models for feature files and directories in order to be able to have a fully traversable model tree of a test suite's structure. These models can then be analyzed or manipulated more easily than the underlying AST layer.
Library which provides helpers for easier Karafka consumers tests
Enables consumer driven contract testing, providing a mock service and DSL for the consumer project, and interaction playback and verification for the service provider project.
A helper for testing poise-ruby providers.
A helper for testing poise-service providers.
A gem providing "time travel" and "time freezing" capabilities, making it dead simple to test time-dependent code. It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call.
Provides a splitting framework similar to AB testing
CQL is a domain specific language used for querying a Cucumber (or other Gherkin based) test suite. The goal of CQL is to increase the ease with which useful information can be extracted from a modeled test suite and turned into summarized data or reports.
RSpec matcher for testing ActionMailer
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.