[MAGNOLIA-3740] Consolidate various testing utilities into a single testing framework Created: 23/Jun/11 Updated: 03/Dec/13 Resolved: 03/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Rob Blake | Assignee: | Philipp Bärfuss |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
| Comments |
| Comment by Magnolia International [ 23/Jun/11 ] |
|
Agreed with the need for consolidation, although your use-case sounds like it's calling for integration tests. We could also think about providing an ITest framework where one could run stuff "in" Magnolia, without necessarily requiring firing up an app server. (after all, we do this in magnolia-tools) |