Arquillian brings the test to the runtime so you don't have to manage the runtime from the test (or the build). Arquillian eliminates this burden by covering all aspects of test execution, which includes:
Managing the lifecycle of the container (or containers)
Bundling the test case, dependent classes and resources into a ShrinkWrap archive (or archives)
Deploying the archive (or archives) to the container (or containers)
Enriching the test case by providing dependency injection and other declarative services
Executing the tests inside (or against) the container
Capturing the results and returning them to the test runner for reporting
Esta idea está muy interesante para hacer tests de clientes que usen mocks de servers cuyo comportamiento se graba de corridas contra servers reales, ¿habrá algo así para java/.net?
"Model your domain in the language and style of Domain Driven Design. Implement it using Scala case classes and companion objects. Pass us your subdomain, and we provide the persistence. Persistence concerns, operations and data are abstracted behind an elegant persistence API. We provide you with fully featured repositories for MongoDB and Cassandra. We provide a suite of integration tests to exercise your repositories against a real database, as well as in-memory repositories for other tests."
Pacto judges the contracts between consumers and providers of RESTful services. It can aid in designing realistic test doubles, by ensuring the double complies with the same contract as the real service. It can also aid with service evolution patterns, like Consumer-Driven Contracts or Documentation-Driven Contracts.
Pacto ensures consumers meet their contractual obligations:
Send the required HTTP request headers
Send an appropriate request body (when required)
Pacto also ensures providers meet their contractual obligations:
Send an appropriate response code
Send the required HTTP response headers
Send an appropriate response body
Pacto can also ensure the provider and consumer collaborate appropriately. It can ensure that for a given scenario:
The consumer calls the expected service(s) with a valid request
The provider sends a valid response
No unexpected services were called
"Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers."