A Vue.js project
Protractor Tester Utils will provide handy utils for make your test better and easy
JSON.parse with context information on error
JSON.parse with context information on error
The most comprehensive authentication framework for TypeScript.
Better Queue for NodeJS
A better opn. Reuse the same tab on Chrome for 👨💻.
Reshape into a better npm audit for the community and encourage more people to include security audit into their process.
Better assertions for node, reporting the expr, filename, lineno etc
Human-friendly JSON Schema validation for APIs
The fastest and simplest library for SQLite in Node.js.
The most comprehensive authentication framework for TypeScript.
Advanced fetch wrapper for typescript with zod schema validations, pre-defined routes, hooks, plugins and more. Works on the browser, node (version 18+), workers, deno and bun.
A better path.resolve() that normalizes paths on Windows
Better `os.arch()` for node and the browser -- detect OS architecture
Telemetry package for Better Auth
Prisma adapter for Better Auth
Kysely adapter for Better Auth
Memory adapter for Better Auth
Drizzle adapter for Better Auth
Mongo adapter for Better Auth
auto-wraps tailwind classes after a certain print width or class count into multiple lines to improve readability.
TypeScript definitions for better-sqlite3
All the development dependencies you need.
Result-returning tests with `?`: composable matchers, rich failure output, no `.unwrap()`.
Optional pretty test runner (`cargo-test-better`) for the test-better testing library.
Procedural macros for the test-better testing library.
Snapshot testing for the test-better testing library.
Property-testing bridge for the test-better testing library.
Core error and result types (`TestError`, `TestResult`) for the test-better testing library.
Matcher trait, standard matchers, and the `check!` macro for the test-better testing library.
Async and timing test helpers (runtime-gated) for the test-better testing library.
= rspec-multi-matchers == Summary * test collection using each or other enumerable methods * makes testing more natural and have a friendlier failure message == HomePage * http://github.com/gregwebs/rspec-multi-matchers == DESCRIPTION: require 'rubygems' require 'spec' require 'rspec_multi_matchers' describe 'array of ones' do it 'should be all ones' do [1,2,3].should each { |n| n.should == 1 } end # this is a new shortcut for a smaller use case it 'should be all ones' do [1,1,1].should each be_eql(1) end end =begin output 'array of ones should fail on 2' FAILED line: 14 item 1: 2 expected: 1, got: 2 (using ==) =end As expected, the output shows expected and got fields line is the line number of the expectiation inside the block the item line gives the index of the item being yielded to the block, and the item itself === Warning Note the use of brackets '{ ... }' instead of 'do ... end' this is necessary because 'do .. end' does not bind strongly enough == RELATED ARTICLES: * http://blog.thoughtfolder.com/2008-11-05-rspec-should-each-matcher.html == INSTALL: * gem install rspec_multi_matchers == LICENSE: (The MIT License) Copyright (c) 2010 Greg Weber Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Better integration tests for apps that use Twilio
Better integration tests for apps that use Twilio
Better syntax for testing whether an object is in a list
Makes fundamental changes to Capybara's threading architecture so you can write stable tests with a shared database connection.
Better integration tests for apps that use Twilio. This is an alternate version of the original JMongol version.
This gem is here to help DRYing your tests cases by giving a better "shared_examples".
A detailed errors while in progress reporter for Minitest
Make your tests more readable
Harness is a feature management platform that helps teams to build better software and to test features quicker.
Better file management with adapters for testing and production
Better way to build Capybara tests
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.