[MAGNOLIA-5162] Tests don't necessarily cleanup everything in SystemProperty Created: 08/Jul/13 Updated: 09/Jul/13 Resolved: 08/Jul/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | testing |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.1 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Sub-Tasks: |
|
|||||||||||||||
| 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)
|
|||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
All our tests use info.magnolia.cms.core.SystemProperty.clear() (which is still supported mostly for backwards compatilibilty). Unfortunately, this method doesn't clear info.magnolia.cms.core.SystemProperty#magnoliaConfigurationProperties, which produces some odd side-effects sometimes (typically when a module defines <properties> it its module descriptor for what should really be <components>) |