With Arquillian, you no longer have to worry about setting up the execution environment because that is all handled for you. The test will either be running in a container or a local CDI environment
Group items tagged
WYTIWYR : What You Test Is What You Run « Antonio's Blog - 0 views
-
" Don't mock types you don't own TDD: Only mock types you own Test Smell: Everything is mocked Testing Anti-Patterns: How to Fail With 100% Test Coverage TDD: Only mock types you own Test Smell: Everything is mocked Arquillian"
Test enrichers - Arquillian - Project Documentation Editor - 0 views
-
With Arquillian, you no longer have to worry about setting up the execution environment because that is all handled for you. The test will either be running in a container or a local CDI environment
Containers - Arquillian - Project Documentation Editor - 0 views
-
Arquillian recognizes three container interaction styles: A remote container resides in a separate JVM from the test runner. Arquillian binds to the container to deploy the test archive and invokes tests via a remote protocol (e.g., Servlet, JMX). A managed container is similar to a remote container, except its lifecycle (startup/shutdown) is also managed by Arquillian. An embedded container resides in the same JVM and is mostly likely managed by Arquillian. Tests are executed via a local protocol for containers without a web component and via a remote protocol for containers with a web component. No need to fiddle with those Maven plugins!
-
Arquillian can control a variety of containers out of the box
How it works - Arquillian - Project Documentation Editor - 0 views
-
How it works
-
write a basic test case and annotate it with declarative behavior that says, "@RunWith Arquillian."
-
tells Arquillian to take over execution of the test when it's launched
- ...1 more annotation...
1 - 6 of 6
Showing 20▼ items per page