Remove travisCI integration.

dpanta94 · Mar 2, 2021 · 0a2db6f · 0a2db6f
1 parent 5c3ea24
commit 0a2db6f
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 154 deletions.
diff --git a/.travis.yml b/.travis.yml
diff --git a/package.json b/package.json
@@ -34,7 +34,6 @@
     "lint": "eslint --quiet --parser=babel-eslint 'src/modules/**/*.js'",
     "lint:fix": "npm run lint -- --fix",
     "test": "TZ=UTC jest --config jest.config.json",
-    "test:travis": "npm run test -- --maxWorkers=4",
     "zip": "node node_modules/product-taskmaster/util/zip.js",
     "glotpress": "gulp glotpress"
   },

diff --git a/tests.md b/tests.md
@@ -21,7 +21,6 @@ params:
 ```
 
 Codeception will process configuration files in a cascading way, think of CSS, so the `codeception.dist.yml` file will be read first and whatever you set in `codeception.yml` will be applied on top of it.
-The only override we do here is telling Codeception that it should read the modules settings not from the `.env` file, that is configured to run the tests on Travis CI, but to read them from the `.env.testing.local` file.
 Now create, again in the plugin root folder, a `.env.testing.local` file copying the `.env.` file and changing any value in it to match your local installation, e.g.:
 
 ```
-Original file line number
+Diff line change
@@ Expand Up / @@ -21,7 +21,6 @@ params: @@
     ```
     Codeception will process configuration files in a cascading way, think of CSS, so the `codeception.dist.yml` file will be read first and whatever you set in `codeception.yml` will be applied on top of it.
-    The only override we do here is telling Codeception that it should read the modules settings not from the `.env` file, that is configured to run the tests on Travis CI, but to read them from the `.env.testing.local` file.
     Now create, again in the plugin root folder, a `.env.testing.local` file copying the `.env.` file and changing any value in it to match your local installation, e.g.:
     ```
@@ Expand Down @@