Displaying 1 to 20 from 64 results

ava - Futuristic JavaScript test runner

Even though JavaScript is single-threaded, IO in Node.js can happen in parallel due to its async nature. AVA takes advantage of this and runs your tests concurrently, which is especially beneficial for IO heavy tests. In addition, test files are run in parallel as separate processes, giving you even better performance and an isolated environment for each test file. Switching from Mocha to AVA in Pageres brought the test time down from 31 to 11 seconds. Having tests run concurrently forces you to write atomic tests, meaning tests don't depend on global state or the state of other tests, which is a great thing!

angular-starter - :tada: An Angular Starter kit featuring Angular (Router, Http, Forms, Services, Tests, E2E, Dev/Prod, HMR, Async/Lazy Routes, AoT via ngc), Karma, Protractor, Jasmine, Istanbul, TypeScript, TsLint, Codelyzer, Hot Module Replacement, @types, and Webpack by @TipeIO

An Angular starter kit featuring Angular 5, Ahead of Time Compile, Router, Forms, Http, Services, Tests, E2E), Karma, Protractor, Jasmine, Istanbul, TypeScript, @types, TsLint, Codelyzer, Hot Module Replacement, and Webpack by AngularClass.This seed repo serves as an Angular starter for anyone looking to get up and running with Angular and TypeScript fast. Using a Webpack 3 for building our files and assisting with boilerplate. We're also using Protractor for our end-to-end story and Karma for our unit tests.

karmatic - 🦑 Easy automatic (headless) browser testing. Powered by Karma, Webpack & Jasmine.

A simplified zero-configuration wrapper around Karma, Webpack, Jasmine & Puppeteer. Karma, Webpack and Jasmine are all great. They're all also quite powerful and each highly configurable. When creating and maintaining small modules, duplication of these configurations and dependencies is cumbersome.

frisby - Frisby is a REST API testing framework built on node

Frisby.js an API testing tool built on top of Jasmine that makes testing API endpoints easy, fast and fun. The minimum setup to run a single test expectation.

Jasmine-Matchers - A huge library of test matchers for Jasmine and Jest.

A huge library of test matchers for a range of common use-cases, compatible with all versions of Jasmine and Jest. Custom Matchers make tests easier to read and produce relevant and useful messages when they fail.

guard-jasmine - The Swiss Army knife for automated Jasmine specs in your console.

Guard::Jasmine automatically tests your Jasmine specs when files are modified. Tested on MRI Ruby 1.9.3, 2.0.0, 2.0.1 and the latest versions of JRuby and Rubinius.

yeti - Yeti automates browser testing.

Yeti automates tests written for various test frameworks. Yeti scales from your dev box (where it works by itself) to your CI system (where it launches browsers with Selenium) without changing your existing tests. You can use any of these test frameworks with Yeti.

grunt-contrib-jasmine - Run jasmine specs headlessly through PhantomJS.

Run this task with the grunt jasmine command. Automatically builds and maintains your spec runner and runs your tests headlessly through PhantomJS.

Ext Spec

Ext Spec makes unit testing Ext JS apps easy. Pick a test framework, plug in Ext Spec and start unit testing your classes - no other dependencies required*.

generator-ng-poly - Yeoman generator for modular AngularJS apps with Gulp and optional Polymer support

Inspired by John Papa's Angular Style Guide and Todd Motto's AngularJS styleguide.This generator focuses on organizing Angular components by feature (home, about, video player, etc.) instead of by type (controller, service, directive, etc.) to encourage the development of self-contained, reusable components.

jasmine-async-sugar - Simple drop-in syntax sugar for Jasmine 2

Simple drop-in syntax sugar for Jasmine 2.X test framework to enhance testing of async (promise) functionality in Angular 1.X applications.Library adds extra global methods which handle async tests implicitly without need to call $rootScope.$digest();, $timeout.flush();,$httpBackend.flush();, or done(); manually. Only thing you need to do is to return the promise in your test function. This approach was inspired by Mocha test framework which waits for resolution of returned promises by default before progressing to next test block.