Mocha TAP reporter, with added capability of storing results in a file
Consumes TAP file and sends an email in case of failed tests
Run multiple testems, output to a single tap file
Utility loading and managing tap configuration
A Test-Anything-Protocol library for JavaScript
minimal implementation of a PassThrough stream
a built-in tap extension that adds typescript support
parse the test anything protocol
Google OAuth2 using Google Identity Services for React 🚀
Tap plugin to provide t.testdir() and t.fixture()
TypeScript definitions for google-one-tap
Zero-dependency reactive state management inspired by React hooks
Silly small, silly easy junit output formatter for tap.
Format a TAP stream using Mocha's set of reporters
Yaml handling for TAP parsers and generators
a built-in tap extension for t.worker()
Easiest way to tap into a pipeline
Google One Tap authentication strategy for Passport.
a built-in tap extension for t.spawn()
pluggable core of node-tap
Pretty test output reporters for tap
Stream TAP test data as a serialized node:test stream
TAP to xUnit XML converter.
a built-in tap extension for t.after() and t.teardown()
Like taps but for files.
Aubio is a tool designed for the extraction of annotations from audio signals. Its features include segmenting a sound file before each of its attacks, performing pitch detection, tapping the beat and producing midi streams from live audio.
A TAP test report defines several properties for each tests. The objective of the gem is to provide all the specified properties after parsing the report either from the file or text.
bpm-finder-cli is a small Ruby command-line tool for converting BPM values into practical delay times, converting milliseconds back into tempo, estimating tempo from tap intervals, and analyzing local WAV audio files for BPM. It is designed for DJs, producers, and developers who need quick tempo math in scripts or terminals. For a full browser-based BPM workflow, visit https://bpm-finder.net/
The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `<` lower than - `>=` lower than or equal - `><` included in list, items should be separated by `|` - `!><` not included in list, items should be separated by `|` - `~` pattern matching, may include `%` (any characters) and `_` (one character) - `!~` pattern not matching, may include `%` (any characters) and `_` (one character)
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.