Set up lint and test (#1)

* Set up lint and test

* Add travis setup

* Add lint-staged

* Remove babel

* Format markdown files witg prettier

* Run tests in node environment

* Update lockfile

* Remove more flow, and force strict mode

* Support node 4

Author: SimenB

.eslintrc.js

@@ -0,0 +1,16 @@
+'use strict';
+
+module.exports = {
+  extends: ['eslint:recommended', 'prettier'],
+  plugins: ['prettier'],
+  parserOptions: {
+    ecmaVersion: 2017,
+  },
+  env: {
+    node: true,
+  },
+  rules: {
+    strict: 'error',
+    'prettier/prettier': 'error',
+  },
+};

.gitignore

@@ -0,0 +1 @@
+node_modules/

.npmignore

@@ -1,3 +1 @@
-**/__mocks__/**
 **/__tests__/**
-src

.travis.yml

@@ -0,0 +1,11 @@
+language: node_js
+node_js:
+  - node
+  - 8
+  - 6
+  - 4
+cache:
+  yarn: true
+branches:
+   only:
+   - master

README.md

@@ -1,5 +1,7 @@
 # eslint-plugin-jest
 
+[![Build Status](https://travis-ci.org/jest-community/eslint-plugin-jest.svg?branch=master)](https://travis-ci.org/jest-community/eslint-plugin-jest)
+
 Eslint plugin for Jest
 
 ## Installation
@@ -8,21 +10,20 @@ Eslint plugin for Jest
 $ yarn add --dev eslint eslint-plugin-jest
 ```
 
-**Note:** If you installed ESLint globally then you must also install `eslint-plugin-jest` globally.
+**Note:** If you installed ESLint globally then you must also install
+`eslint-plugin-jest` globally.
 
 ## Usage
 
-Add `jest` to the plugins section of your `.eslintrc` configuration file. You can omit the `eslint-plugin-` prefix:
+Add `jest` to the plugins section of your `.eslintrc` configuration file. You
+can omit the `eslint-plugin-` prefix:
 
 ```json
 {
-  "plugins": [
-    "jest"
-  ]
+  "plugins": ["jest"]
 }
 ```
 
-
 Then configure the rules you want to use under the rules section.
 
 ```json
@@ -48,33 +49,41 @@ You can also whitelist the environment variables provided by Jest by doing:
 
 ## Supported Rules
 
-- [no-disabled-tests](/packages/eslint-plugin-jest/docs/rules/no-disabled-tests.md) - disallow disabled tests.
-- [no-focused-tests](/packages/eslint-plugin-jest/docs/rules/no-focused-tests.md) - disallow focused tests.
-- [no-identical-title](/packages/eslint-plugin-jest/docs/rules/no-identical-title.md) - disallow identical titles.
-- [valid-expect](/packages/eslint-plugin-jest/docs/rules/valid-expect.md) - ensure expect is called correctly.
+* [no-disabled-tests](/packages/eslint-plugin-jest/docs/rules/no-disabled-tests.md) -
+  disallow disabled tests.
+* [no-focused-tests](/packages/eslint-plugin-jest/docs/rules/no-focused-tests.md) -
+  disallow focused tests.
+* [no-identical-title](/packages/eslint-plugin-jest/docs/rules/no-identical-title.md) -
+  disallow identical titles.
+* [valid-expect](/packages/eslint-plugin-jest/docs/rules/valid-expect.md) -
+  ensure expect is called correctly.
 
 ## Shareable configurations
 
 ### Recommended
 
-This plugin exports a recommended configuration that enforces good testing practices.
+This plugin exports a recommended configuration that enforces good testing
+practices.
 
-To enable this configuration use the `extends` property in your `.eslintrc` config file:
+To enable this configuration use the `extends` property in your `.eslintrc`
+config file:
 
 ```json
 {
   "extends": ["plugin:jest/recommended"]
 }
 ```
 
-See [ESLint documentation](http://eslint.org/docs/user-guide/configuring#extending-configuration-files) for more information about extending configuration files.
+See [ESLint
+documentation](http://eslint.org/docs/user-guide/configuring#extending-configuration-files)
+for more information about extending configuration files.
 
 The rules enabled in this configuration are:
 
-- [jest/no-disabled-tests](/packages/eslint-plugin-jest/docs/rules/no-disabled-tests.md)
-- [jest/no-focused-tests](/packages/eslint-plugin-jest/docs/rules/no-focused-tests.md)
-- [jest/no-identical-title](/packages/eslint-plugin-jest/docs/rules/no-identical-title.md)
-- [jest/valid-expect](/packages/eslint-plugin-jest/docs/rules/valid-expect.md)
+* [jest/no-disabled-tests](/packages/eslint-plugin-jest/docs/rules/no-disabled-tests.md)
+* [jest/no-focused-tests](/packages/eslint-plugin-jest/docs/rules/no-focused-tests.md)
+* [jest/no-identical-title](/packages/eslint-plugin-jest/docs/rules/no-identical-title.md)
+* [jest/valid-expect](/packages/eslint-plugin-jest/docs/rules/valid-expect.md)
 
 ## Credit
 

docs/rules/no-disabled-tests.md

@@ -10,6 +10,7 @@ This rule raises a warning about disabled tests.
 ## Rule Details
 
 There are a number of ways to disable tests in Jest:
+
 * by appending `.skip` to the test-suite or test-case
 * by prepending the test function name with `x`
 * by declaring a test with a name but no function body
@@ -34,7 +35,7 @@ it('bar');
 test('bar');
 
 it('foo', () => {
-  pending()
+  pending();
 });
 ```
 

docs/rules/no-focused-tests.md

@@ -1,15 +1,19 @@
 # Disallow Focused Tests (no-focused-tests)
 
-Jest has a feature that allows you to focus tests by appending `.only` or prepending `f` to a test-suite or a test-case.
-This feature is really helpful to debug a failing test, so you don’t have to execute all of your tests.
-After you have fixed your test and before committing the changes you have to remove `.only` to ensure all tests are executed on your build system.
+Jest has a feature that allows you to focus tests by appending `.only` or
+prepending `f` to a test-suite or a test-case. This feature is really helpful to
+debug a failing test, so you don’t have to execute all of your tests. After you
+have fixed your test and before committing the changes you have to remove
+`.only` to ensure all tests are executed on your build system.
 
-This rule reminds you to remove `.only` from your tests by raising a warning whenever you are using the exclusivity feature.
+This rule reminds you to remove `.only` from your tests by raising a warning
+whenever you are using the exclusivity feature.
 
 ## Rule Details
 
-This rule looks for every `describe.only`, `it.only`, `test.only`, `fdescribe`, `fit` and `ftest` occurrences within the source code.
-Of course there are some edge-cases which can’t be detected by this rule e.g.:
+This rule looks for every `describe.only`, `it.only`, `test.only`, `fdescribe`,
+`fit` and `ftest` occurrences within the source code. Of course there are some
+edge-cases which can’t be detected by this rule e.g.:
 
 ```js
 const describeOnly = describe.only;

docs/rules/no-identical-title.md

@@ -1,10 +1,15 @@
 # Disallow identical titles (no-identical-title)
 
-Having identical titles for two different tests or test suites may create confusion. For example, when a test with the same title as another test in the same test suite fails, it is harder to know which one failed and thus harder to fix.
+Having identical titles for two different tests or test suites may create
+confusion. For example, when a test with the same title as another test in the
+same test suite fails, it is harder to know which one failed and thus harder to
+fix.
 
 ## Rule Details
 
-This rule looks at the title of every test and test suites. It will report when two test suites or two test cases at the same level of a test suite have the same title.
+This rule looks at the title of every test and test suites. It will report when
+two test suites or two test cases at the same level of a test suite have the
+same title.
 
 The following patterns are considered warnings:
 
@@ -17,7 +22,8 @@ describe('foo', () => {
     // ...
   });
 
-  describe('baz', () => { // Has the same title as a previous test suite
+  describe('baz', () => {
+    // Has the same title as a previous test suite
     // ...
   });
 });
@@ -37,7 +43,8 @@ describe('foo', () => {
     it('should work', () => {});
   });
 
-  describe('baz', () => { // Has the same title as a previous test suite
+  describe('baz', () => {
+    // Has the same title as a previous test suite
     // Has the same name as a test in a sibling test suite, which is fine
     it('should work', () => {});
   });

docs/rules/prefer-to-have-length.md

@@ -1,10 +1,12 @@
-# Suggest using  `toHaveLength()` (prefer-to-have-length)
+# Suggest using `toHaveLength()` (prefer-to-have-length)
 
-In order to have a better failure message, `toHaveLength()` should be used upon asserting expections on object's length property.
+In order to have a better failure message, `toHaveLength()` should be used upon
+asserting expections on object's length property.
 
 ## Rule details
 
-This rule triggers a warning if `toBe()` is used to assert object's length property.
+This rule triggers a warning if `toBe()` is used to assert object's length
+property.
 
 ```js
 expect(files.length).toBe(1);

docs/rules/valid-expect.md

@@ -1,11 +1,13 @@
 # Enforce valid `expect()` usage (valid-expect)
 
-Ensure `expect()` is called with a single argument and there is an actual expectation made.
+Ensure `expect()` is called with a single argument and there is an actual
+expectation made.
 
 ## Rule details
 
-This rule triggers a warning if `expect()` is called with more than one argument or without arguments. 
-It would also issue a warning if there is nothing called on `expect()`, e.g.:
+This rule triggers a warning if `expect()` is called with more than one argument
+or without arguments. It would also issue a warning if there is nothing called
+on `expect()`, e.g.:
 
 ```js
 expect();