Removed end-to-end tests (#226)

Author: Josh Goldberg

.circleci/config.yml

@@ -79,7 +79,7 @@ jobs:
 
             - run: npm run prettier
 
-    test-end-to-end:
+    test:
         docker:
             - image: circleci/node:latest
 
@@ -91,21 +91,7 @@ jobs:
             - attach_workspace:
                   at: "."
 
-            - run: npm run test:end-to-end
-
-    test-unit:
-        docker:
-            - image: circleci/node:latest
-
-        working_directory: ~/repo
-
-        steps:
-            - checkout
-
-            - attach_workspace:
-                  at: "."
-
-            - run: npm run test:unit -- --coverage
+            - run: npm run test -- --coverage
 
     tsc:
         docker:
@@ -143,11 +129,7 @@ workflows:
             - prettier:
                   requires:
                       - build
-            - test-end-to-end:
-                  requires:
-                      - build
-                      - tsc
-            - test-unit:
+            - test:
                   requires:
                       - build
             - tsc:

docs/Development.md

@@ -17,10 +17,10 @@ cd tslint-to-eslint-config
 npm i
 ```
 
-Compile with `npm run tsc` and run tests with `npm run test:unit`.
+Compile with `npm run tsc` and run tests with `npm run test`.
 
 ## Further Reading
 
 -   [Architecture](./Architecture.md): How the general app structure operates
 -   [Dependencies](./Dependencies.md): How functions pass and receive static dependencies
--   [Testing](./Testing.md): Unit and end-to-end tests
+-   [Testing](./Testing.md): Unit tests

docs/Testing.md

@@ -1,9 +1,7 @@
 # Testing
 
-## Unit Tests
-
 ```
-npm run test:unit
+npm run test
 ```
 
 Each `src/**/*.ts` source file should have an equivalent `*.test.ts` next to it.
@@ -21,26 +19,3 @@ Tests should include comments above each section of the "AAA" testing format:
 
 See [Dependencies](./Dependencies.md) for how static dependencies are stubbed out in functions.
 That system is how functions can receive stubs and spies during unit tests.
-
-## End-to-End Tests
-
-```shell
-npm run test:end-to-end
-```
-
-End-to-end tests that execute the `bin/tslint-to-eslint` command and validate outputs are generated from the directories in `test/tests/`.
-Each directory there contains:
-
--   `test.ts`: Test file that runs `createTests(__dirname);` to set up tests in that directory
--   `.eslintrc.json`: `.gitignore`d output from the most recent test run
--   `expected.json`: Expected output ESLint configuration
--   `stderr.txt`: Expected output written to the process `stderr`
--   `stdout.txt`: Expected output written to the process `stdout`
--   `tslint.json`: Original TSLint configuration file to convert
-
-Within each directory, a test suite will execute `bin/tslint-to-eslint` and validate the outputs match what's on disk.
-
-Use `npm run test:end-to-end:accept` to overwrite the expected contents of files with what is actually written.
-These behave similarly to updating snapshots in snapshot testing.
-
-> Note: these end-to-end tests use the compiled result of `npm run tsc`, so if you update source code, re-run `npm run tsc` before `npm run test:end-to-end`.

package.json

@@ -60,9 +60,7 @@
         "eslint": "eslint \"./src/*.ts\" \"./src/**/*.ts\" --report-unused-disable-directives",
         "prettier": "prettier \"./src/*.{js,json,ts,xml,yaml}\" \"./src/**/*.{js,json,ts,xml,yaml}\" --ignore-path .prettierignore",
         "prettier:write": "npm run prettier -- --write",
-        "test:unit": "jest",
-        "test:end-to-end": "jest --config=test/jest.config.js --runInBand",
-        "test:end-to-end:accept": "jest --config=test/jest.config.js --globals=\"{\\\"acceptTestChanges\\\": true }\"  --runInBand",
+        "test": "jest",
         "tsc": "tsc"
     },
     "version": "0.2.7"