文件列表:

.whitesource (213, 2020-09-25)
LICENSE (1071, 2020-09-25)
azure-pipelines.yml (462, 2020-09-25)
go.mod (108, 2020-09-25)
go.sum (350, 2020-09-25)
harness_test.go (6272, 2020-09-25)

[](https://gitpod.io/#https://github.com/monch1962/async-pact-spike) [](https://dev.azure.com/monch1962/monch1962/_build/latest?definitionId=13&branchName=master) [](https://sonarcloud.io/dashboard?id=monch1962_async-pact-spike) # async-pact-spike Spike to play with Pact testing on RabbitMQ Intention is to use this code as a template with Pactical (https://github.com/monch1962/pactical). Pactical can populate code tempates from Pacts (https://pact.io), generating executable code. This template file should be able to turn a set of Pacts into a set of executable test cases for async testing against AMQP servers. As Go code generates standalone executables, the set of Pacts can generate a standalone EXE file which, when run, will test all of the interfaces defined within the set of Pacts. This EXE file can then be driven by CI. ## Environment variables There are several environment variables that can be configured for this tool, some of which are optional: - `PROTOCOL` (required, can only be `amqp` or `amqps`) - `PUBLISH_AMQP_SERVER` (default: `localhost`) - `PUBLISH_AMQP_SERVER_TCP` (default: `5672` if PROTOCOL is `amqp`, or `5671` if PROTOCOL is `amqps`) - `PUBLISH_USERNAME` (default: `guest`) - `PUBLISH_PASSWORD` (default: `guest`) - `PUBLISH_Q` (required) - `SUBSCRIBE_AMQP_SERVER` (default: same as `PUBLISH_AMQP_SERVER`) - `SUBSCRIBE_AMQP_SERVER_TCP` (default: same as `SUBSCRIBE_AMQP_SERVER_TCP`) - `SUBSCRIBE_USERNAME` (default: same as `PUBLISH_USERNAME`) - `SUBSCRIBE_PASSWORD` (default: same as `PUBLISH_PASSWORD`) - `SUBSCRIBE_Q` (required) ## To run To run tests against a AMQP server on localhost in default config: `$ PUBLISH_Q=abc SUBSCRIBE_Q=def go test` or to specify AMQP server details, use something like: `$ PUBLISH_AMQP_SERVER=peacock.rmq.cloudamqp.com PUBLISH_USERNAME=edtdqjib PUBLISH_PASSWORD=ucsUTMSeTR9lQEo0cRJwCgPicoroEPwa PUBLISH_Q=abc123 PUBLISH_URI_SUFFIX=edtdqjib PUBLISH_AMQP_SERVER_TCP=5671 PROTOCOL=amqps SUBSCRIBE_Q=abc123 TIMEOUT=10000 go test` ## To output JUnit format `$ go get -u github.com/jstemmer/go-junit-report` `$ PUBLISH_AMQP_SERVER=peacock.rmq.cloudamqp.com PUBLISH_USERNAME=edtdqjib PUBLISH_PASSWORD=ucsUTMSeTR9lQEo0cRJwCgPicoroEPwa PUBLISH_Q=abc123 PUBLISH_URI_SUFFIX=edtdqjib PUBLISH_AMQP_SERVER_TCP=5671 PROTOCOL=amqps SUBSCRIBE_Q=abc123 TIMEOUT=10000 go test -v 2>&1 | go-junit-report` ## To compile tests into a standalone executable file `$ go test -c -o tests` will compile all the tests into a standalone EXE called `tests`, which can be moved and executed on other hardware `$ PUBLISH_AMQP_SERVER=peacock.rmq.cloudamqp.com PUBLISH_USERNAME=edtdqjib PUBLISH_PASSWORD=ucsUTMSeTR9lQEo0cRJwCgPicoroEPwa PUBLISH_Q=abc123 PUBLISH_URI_SUFFIX=edtdqjib PUBLISH_AMQP_SERVER_TCP=5671 PROTOCOL=amqps SUBSCRIBE_Q=abc123 TIMEOUT=10000 ./tests -test.v` will run the tests in verbose mode, and `$ PUBLISH_AMQP_SERVER=peacock.rmq.cloudamqp.com PUBLISH_USERNAME=edtdqjib PUBLISH_PASSWORD=ucsUTMSeTR9lQEo0cRJwCgPicoroEPwa PUBLISH_Q=abc123 PUBLISH_URI_SUFFIX=edtdqjib PUBLISH_AMQP_SERVER_TCP=5671 PROTOCOL=amqps SUBSCRIBE_Q=abc123 TIMEOUT=10000 ./tests` will run them without verbose mode. Finally, to generate Junit reports from a compiled test file, `$ PUBLISH_AMQP_SERVER=peacock.rmq.cloudamqp.com PUBLISH_USERNAME=edtdqjib PUBLISH_PASSWORD=ucsUTMSeTR9lQEo0cRJwCgPicoroEPwa PUBLISH_Q=abc123 PUBLISH_URI_SUFFIX=edtdqjib PUBLISH_AMQP_SERVER_TCP=5671 PROTOCOL=amqps SUBSCRIBE_Q=abc123 TIMEOUT=10000 ./tests -test.v | go-junit-report` ## TODO - support all the features of Pact (e.g. at present it only supports checking against hardcoded responses; should be able to do regex or pattern matching as supported by Pact) - investigate FaaS options for deployment - implement concurrent test execution (this is somewhat tricky for async, where responses can arrive out of sequence. One option would be to single-thread only requests that write to the same output queue, which would avoid the out-of-sequence response problem. Need to think this through further...)

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：