*** Transient Document ***
Please note that this document is transient. It will likely be removed once the first version of the user guide is complete.
*** Transient Document ***
- Mission statement
- Architecture overview
- Test framework (TestNG/JUnit)
- Arquillian test runner (correct term?)
- ShrinkWrap
- Target container
- Integration testing in Java EE
- What testing needs Arquillian seeks to cover
- Testing the magic (i.e., declarative services)
- Controlling the test classpath
- Test micro-deployments
- Accessing the components under test
- To get component w/ services, you can't use the new operator, you need to perform a lookup)
- Getting started
- Building Arquillian (temporary)
- Adding Arquiilian to your Maven 2 project
- Defining an Arquillian-managed test case: JUnit/Test NG
- Assembling the test archive with ShrinkWrap
- Selecting the target container deployer
- Executing the test case from Maven 2
- Executing the test case from an IDE plugin
- Debugging the test case
- A note about assertions
- Enabling the use of the assert keyword
- Injection into the test case
- What can be injected
- Activating CDI in your test archive
- Active CDI scopes during test method
- Test execution process
- Hooking into the test runner
- Deployment
- RPC (or local) test execution
- Returning results
- Debugging tests
- Remote container
- Standalone container
- Target environments
- Testing scenarios
- Activating CDI in your test archive
- Setting up a persistence unit in a test case
- Controlling transactions in a test
- Seperating integration tests from standalone tests
- Extending Arquillian
- Containers SPI
- Defining a new container
- ShrinkWrap primer
- Exporting a test archive for inspection
Comments