boulder/test/js
Ben Irving 67fd6ef67c Add certificatesPerName rate limit to integration test (#1940)
This PR, covers the code path where the certificatesPerName rate limit is exceeded.

Additionally, a node package (cli) was upgraded as the spinner was preventing the redirection of I/O. See this commit: node-js-libs/cli@ff064fe.

Fixes #1614

https://github.com/letsencrypt/boulder/pull/1940
2016-06-17 16:10:05 -07:00
..
README.md Move boulder to using local signer. 2015-06-05 08:13:39 -07:00
acme-util.js Remove all stray copyright headers and appends the initial line to LICENSE.txt (#1853) 2016-05-31 12:32:04 -07:00
acme.js Add trailing commas. 2015-08-28 10:45:39 -07:00
crypto-util.js Remove all stray copyright headers and appends the initial line to LICENSE.txt (#1853) 2016-05-31 12:32:04 -07:00
package.json Add certificatesPerName rate limit to integration test (#1940) 2016-06-17 16:10:05 -07:00
revoke.js Remove all stray copyright headers and appends the initial line to LICENSE.txt (#1853) 2016-05-31 12:32:04 -07:00
test.js Remove the agreement flag from test.js. (#1885) 2016-06-06 13:19:57 -07:00

README.md

A JS tester for boulder

The node.js scripts in this directory provide a simple end-to-end test of Boulder. (Using some pieces from node-acme) To run:

Run boulder in default test mode:

cd ../../
./start.py

To run cfssl with a Yubikey, edit test/boulder-pkcs11-example-config.json to

add your PKCS#11 PIN (and module name, token name, and label). Then run:

cd ../../
BOULDER_CONFIG=test/boulder-pkcs11-example-config.json ./start.py

Client side

npm install
node test.js