[MAGNOLIA-2633] Extract module to support testing (magnolia-testutils) Created: 22/Feb/09 Updated: 02/Dec/13 Resolved: 02/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | testing |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Rob van der Linden Vooren | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
I recently discovered that Magnolia core provides utilities for testing, residing in the "info.magnolia.test.mock" package, in the "test" source tree. One could then define a maven dependency as such (example): <dependency> and have testing tools readily available. What do you guys think? |
| Comments |
| Comment by Magnolia International [ 23/Feb/09 ] |
|
You can already do that, like most of our modules do: <dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-core</artifactId>
<version>4.0-SNAPSHOT</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>
Extracting that out of the source tree would mean splitting core in several artifacts (because those utils use some core code too), which is not something we're ready or willing to do now. |