kinto-settings integration tests
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
config-tests
.dockerignore
.gitignore Do not need to use python-dotenv because pipenv will automatically lo… May 9, 2018
.travis.yml Remove extraneous pipenv install of flake8 Feb 28, 2018
Dockerfile Revert "Remove --skip-lock, since we've moved to Dependabot, from pyu… Oct 18, 2018
Jenkinsfile Bug 1476402; fix cron-jobs and pollSCM branch-running logic Jul 19, 2018
LICENSE chore: initial checkin Jan 25, 2017
Pipfile Bump kinto-http from 10.1.0 to 10.1.1 Nov 14, 2018
Pipfile.lock
README.md Fixed typo Sep 20, 2018
conftest.py Added back in test for verfifying email notifications happen when add… Jun 7, 2018
manifest.ini Update kinto writer host name for -stage Aug 10, 2018
pipenv.txt Bump pipenv from 2018.7.1 to 2018.10.13 Oct 16, 2018
setup.cfg feat: add @chartjes config-test Jan 25, 2017
testrail.cfg Added in place holders for username and password Mar 26, 2018

README.md

License travis Dependabot

Summary

Tests for the Kinto server fall into 3 categories:

  1. unit tests - located here: https://github.com/Kinto/kinto/tree/master/tests
  2. loadtests - located here: https://github.com/Kinto/kinto-loadtests
  3. configuration check tests - located in this repo

This repo is a clearinghouse for all automated tests that don't need to reside in their own repository. They would include a variety of test types that usually fall in the middle of the test pyramid: API tests, config and URL checks, deployment tests, end-2-end tests, security tests, etc.

Preparing the tests

To run the tests, you need to have the following installed:

  • Python 3.6 or greater
  • Pipenv

Running the tests

You can run these tests using the following commands from inside the root directory for the project:

$ pipenv install
$ pipenv run pytest -m TEST_TYPE --env TEST_ENV
  • TEST_TYPE is dist for kinto-dist deployments, settings for kinto-settings deployments and webextensions for kintowe deployments
  • TEST_ENV is one of the environments listed in the manifest.ini file.

Running the tests using Docker

With Docker installed, running the tests is as simple as first building:

$ docker build -t kinto-tests .

Then, you can run the tests like so (substituting your TEST_TYPE and TEST_ENV):

$ docker run -it kinto-tests pytest -m settings --env=stage