Details
-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.0.0.Alpha5
-
Component/s: Test Harness Integration
-
Labels:None
Description
For container / deployer / framework dev it is useful to be able to Assert on Deployment related issues.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Since Deployments happen in @BeforeClass we don't have any instance to test against. We need to override the testframeworks method lookup to support 'static' test methods or just call them our selves. (The TestFrameworks probably need at least one method marked with @Test to run at all)
Show
Aslak Knutsen
added a comment - Since Deployments happen in @BeforeClass we don't have any instance to test against. We need to override the testframeworks method lookup to support 'static' test methods or just call them our selves. (The TestFrameworks probably need at least one method marked with @Test to run at all)
Aslak Knutsen
added a comment - Since Deployments happen in @BeforeClass we don't have any instance to test against. We need to override the testframeworks method lookup to support 'static' test methods or just call them our selves. (The TestFrameworks probably need at least one method marked with @Test to run at all)
Show
Aslak Knutsen
added a comment - https://github.com/aslakknutsen/arquillian/tree/the_bigger_picture
Aslak Knutsen
added a comment - https://github.com/aslakknutsen/arquillian/tree/the_bigger_picture Faulty impl, does not assert if exception is not thrown
Show
Aslak Knutsen
added a comment - Faulty impl, does not assert if exception is not thrown
Aslak Knutsen
added a comment - Faulty impl, does not assert if exception is not thrown pushed upstream master.
Show
Aslak Knutsen
added a comment - pushed upstream master.
Aslak Knutsen
added a comment - pushed upstream master. 
The example show two different approches.
1. Inject the deployment exception and let the user do normal Assertions on it
2. Use the ExpectedException feature of the TestFramework