Home Explore Project
Register Sign In
linux
/
acme-tiny
3
1
Fork 0
Files Issues 1 Pull Requests 0 Wiki
Tree: ad7802f1c4
Branches Tags
acme-tiny
/
tests
Daniel Roesler 31ff3267b4 Merge remote-tracking branch 'origin/master' 6 years ago
..
README.md 31ff3267b4 Merge remote-tracking branch 'origin/master' 6 years ago
__init__.py 9bc3865d8c Add setup.py 9 years ago
monkey.py 31ff3267b4 Merge remote-tracking branch 'origin/master' 6 years ago
requirements.txt e6cad5f0f6 added argparse to requirements for python 2.6 and removed fuse from coverage 9 years ago
server.py daba51d37e fixed key in test suite server that I had already apparently fixed in travis-ci.gethttpsforfree.com 8 years ago
test_install.py 9bc3865d8c Add setup.py 9 years ago
test_module.py 31ff3267b4 Merge remote-tracking branch 'origin/master' 6 years ago

README.md

How to test acme-tiny

Testing acme-tiny requires a bit of setup since it interacts with other servers (Let's Encrypt's staging server) to test issuing fake certificates. This readme explains how to setup and test acme-tiny yourself.

Setup instructions

  1. Make a test subdomain for a server you control. Set it as an environmental variable on your local test setup.
    • On your local: export TRAVIS_DOMAIN=travis-ci.gethttpsforfree.com
    • Configure the webserver on $TRAVIS_DOMAIN for redirection of http://$TRAVIS_DOMAIN/.well-known/acme-challenge/ to http://localhost:8888/
  2. Generate a shared secret between your local test setup and your server.
    • openssl rand -base64 32
    • On your local: export TRAVIS_SESSION="<random_string_here>"
  3. Copy and run the test suite mini-server on your server:
    • scp server.py ubuntu@travis-ci.gethttpsforfree.com
    • ssh ubuntu@travis-ci.gethttpsforfree.com
    • export TRAVIS_SESSION="<random_string_here>"
    • sudo server.py
  4. Install the test requirements on your local (FUSE and optionally coveralls).
    • sudo apt-get install fuse
    • virtualenv /tmp/venv
    • source /tmp/venv/bin/activate
    • pip install -r requirements.txt
  5. Run the test suit on your local.
    • cd /path/to/acme-tiny
    • coverage run --source ./ --omit ./tests/server.py,./setup.py -m unittest tests

Why use FUSE?

Acme-tiny writes the challenge files for certificate issuance. In order to do full integration tests, we actually need to serve correct challenge files to the Let's Encrypt staging server on a real domain that they can verify. However, Travis-CI doesn't have domains associated with their test VMs, so we need to send the files to the remote server that does have a real domain.

The test suite uses FUSE to do this. It creates a FUSE folder that simulates being a real folder to acme-tiny. When acme-tiny writes the challenge files in the mock folder, FUSE POSTs those files to the real server (which is running the included server.py), and the server starts serving them. That way, both acme-tiny and Let's Encrypt staging can verify and issue the test certificate. This technique allows for high test coverage on automated test runners (e.g. Travis-CI).