JSPM

coffeelint-no-focused-jasmine-specs

0.1.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 226
  • Score
    100M100P100Q94647F
  • License MIT

CoffeeLint rule to ensure that all your jasmine specs run

Package Exports

  • coffeelint-no-focused-jasmine-specs

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (coffeelint-no-focused-jasmine-specs) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

coffeelint-no-focused-jasmine-specs

Circle CI

Deadlines are looming and you're focusing on getting those last few specs green..

CLEAR TEST RUN. You're done! git add . && git commit -m 'All Done! ⚡'

A few days later someone asks, 'When you run the specs, do only 10 run?' and a knot develops in your throat. You check the project, only to have your worst fears confirmed: You commited an fdescribe block! You remove it to uncover 30 spec failures.

That would never happen to you right? Of course not, this isn't your first rodeo. You're using coffeelint-no-focused-jasmine-specs.

Installation

  1. Setup CoffeeLint in your project and verify that it works
  2. Add this module as a devDependency: npm install -D coffeelint-no-focused-jasmine-specs
  3. Update your coffeelint.json configuration file as described below.
  4. Modify coffeelint to use this custom rule. For example, If you run coffeelint from the command line you might do this coffeelint --rules node_modules/coffeelint-no-focused-jasmine-specs

Configuration

Add the following snippet to your coffeelint.json config:

{
  "no_focused_jasmine_specs": {
    "module": "coffeelint-no-focused-jasmine-specs",
    "level": "warn"
  }
}