[MAGNOLIA-4128] Enhance ComponentTestUtils to also support GuiceComponentProvider Created: 17/Jun/11 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.5.x |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Daniel Lipp | Assignee: | Unassigned |
| Resolution: | Won't Do | 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 |
|
Right now ComponentTestUtils hardcoded relies on MockComponentProvider. As soon as you e.g. want to use a GuiceComponentProvider you cannot use it any longer. Proposal how to do that (by tmattsson): @ConfigureComponents @Inject @Test } |
| Comments |
| Comment by Daniel Lipp [ 11/Jul/11 ] |
|
updated description as we gave up Pico in favor of Guice |
| Comment by Tobias Mattsson [ 29/Aug/11 ] |
|
In my opinion ComponentsTestUtil should be removed or at least deprecated. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |