From a91b6bf3bd216c13f0dafdbbf9ef33f15dd103bf Mon Sep 17 00:00:00 2001 From: Alex Crichton Date: Tue, 22 Sep 2015 11:29:47 -0700 Subject: Enable testing on Windows via AppVeyor This abolishes the test.sh script which spawns a bunch of `openssl` instances to instead run/manage the binary in-process (providing more isolation to boot). The tests have been updated accordingly and the `connected_socket` dependency was also dropped in favor of `net2` as it the former doesn't work on Windows. --- README.md | 14 -------------- 1 file changed, 14 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 06b9b7f8..82dd2e4f 100644 --- a/README.md +++ b/README.md @@ -64,18 +64,4 @@ The build script can be configured via environment variables: If either `OPENSSL_LIB_DIR` or `OPENSSL_INCLUDE_DIR` are specified, then the build script will skip the pkg-config step. -## Testing -Several tests expect a local test server to be running to bounce requests off -of. It's easy to do this. Open a separate terminal window and `cd` to the -rust-openssl directory. Then run one of the following command: - -```bash -./openssl/test/test.sh -``` - -This will boot a bunch of `openssl s_server` processes that the tests connect -to. Then in the original terminal, run `cargo test`. If everything is set up -correctly, all tests should pass. You can stop the servers with `killall -openssl`. - [1]: http://slproweb.com/products/Win32OpenSSL.html -- cgit v1.2.3