Giter VIP home page Giter VIP logo

komondor-test's Introduction

komondor-test

NPM version NPM downloads Build status Codecov Coverage Status

Greenkeeper Semantic Release

Visual Studio Code Wallaby.js

Test library for writing plugins for komondor.

API

k.live(), k.save(), k.simulate(), k.trio() has the same signature. This allows you to easily switch between them to debug specific issue. e.g.

import k from 'komondor-test'

// starts with
k.live('...', (title, spec) => {
  test.only(title, async () => {
    // test away
  })
})

// change 4 characters 'Live' to 'Save' for saving the result
k.save('...', ...)

// change `Save` to `Simulate` to valid it works in simulate mode
k.simulate('...', ...)

// change to `Trio` to run all three
k.trio('...', ...)

testTrio([customDescription], specName, handler)

Also exposed as k.trio(). Use testTrio() to run all three tests (live, save, and simulate)

import { testTrio } from 'komondor-test'

testTrio('node/childProcess/success', (title, spec) => {
  // `test()` is your test runner: jest, ava, mocha, etc.
  test(title, async () => {
    const s = await spec(childProcess)
    ...
  })
})

testLive([customDescription], specName, handler)

Also exposed as k.live(). Use testLive() to run spec in live mode.

import { testLive } from 'komondor-test'

testLive('node/childProcess/success', (title, spec) => {
  // `test()` is your test runner: jest, ava, mocha, etc.
  test(title, async () => {
    const s = await spec(childProcess)
    ...
  })
})

testSave([customDescription], specName, handler)

Also exposed as k.save(). Use testSave() to run spec in save mode

import { testSave } from 'komondor-test'

testSave('node/childProcess/success', (title, spec) => {
  // `test()` is your test runner: jest, ava, mocha, etc.
  test(title, async () => {
    const s = await spec(childProcess)
    ...
  })
})

testSimulate([customDescription], specName, handler)

Also exposed as k.simulate(). Use testSimulate() to run spec in simulate mode.

import { testSimulate } from 'komondor-test'

testSimulate('node/childProcess/success', (title, spec) => {
  // `test()` is your test runner: jest, ava, mocha, etc.
  test(title, async () => {
    const s = await spec(childProcess)
    ...
  })
})

Contribute

# right after fork
npm install

# begin making changes
git checkout -b <branch>
npm run watch

# edit `webpack.config.dev.js` to exclude dependencies for the global build.

# after making change(s)
git commit -m "<commit message>"
git push

# create PR

Npm Commands

There are a few useful commands you can use during development.

# Run tests (and lint) automatically whenever you save a file.
npm run watch

# Run tests with coverage stats (but won't fail you if coverage does not meet criteria)
npm run test

# Manually verify the project.
# This will be ran during 'npm preversion' so you normally don't need to run this yourself.
npm run verify

# Build the project.
# You normally don't need to do this.
npm run build

# Run tslint
# You normally don't need to do this as `npm run watch` and `npm version` will automatically run lint for you.
npm run lint

Generated by [email protected]

komondor-test's People

Contributors

unional avatar greenkeeper[bot] avatar

Watchers

James Cloos avatar  avatar  avatar

komondor-test's Issues

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of rimraf is breaking the build 🚨

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/rimraf-2.6.3 at 100.0% (Details).

Commits

The new version differs by 6 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of assertron is breaking the build 🚨

The devDependency assertron was updated from 5.2.0 to 5.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

assertron is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v5.2.1

5.2.1 (2018-10-25)

Bug Fixes

  • deepEqual support of string array (6ceae6f)
Commits

The new version differs by 1 commits.

  • 6ceae6f fix: deepEqual support of string array

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of dependency-check is breaking the build 🚨

The devDependency dependency-check was updated from 3.2.1 to 3.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

dependency-check is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 4 commits.

  • 32c1b74 3.3.0
  • e3ff1df update travis setup with new node versions
  • 3f302e0 Clarifies that --ignore-module works for unused and missing
  • 5aff1bc Silently pass on unsupported versions of Node.js

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of komondor is breaking the build 🚨

The devDependency komondor was updated from 6.11.3 to 6.11.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

komondor is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v6.11.4

6.11.4 (2019-06-18)

Bug Fixes

Commits

The new version differs by 12 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-harmony is breaking the build 🚨

The devDependency eslint-plugin-harmony was updated from 1.1.0 to 1.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-harmony is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/eslint-plugin-harmony-1.1.1 at 100.0% (Details).

Commits

The new version differs by 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

support other test-runners

Right now it only supports test runner exposing a global test() and test.only().
i.e. jest.

Should be test-runner agnostic.

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.10.5 to 15.10.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v15.10.6

15.10.6 (2018-10-27)

Bug Fixes

  • remove dependency to git-url-parse (a99355e)
Commits

The new version differs by 2 commits.

  • a99355e fix: remove dependency to git-url-parse
  • cc06d89 test: fix errors ordering in assertions

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.