[MAGNOLIA-4519] Make resolving path in MockNode easier to read and do not allow node to be its own parent Created: 27/Aug/12 Updated: 25/Oct/13 Resolved: 18/Sep/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | testing |
| Affects Version/s: | 4.5 |
| Fix Version/s: | 4.5.5 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Jan Haderka |
| Resolution: | Fixed | 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Comments |
| Comment by Daniel Lipp [ 17/Sep/12 ] |
|
Changes in path resolving should be covered via unit-test(s) in order to make it obvious what bug was solved and to make sure no new one was introduced. |
| Comment by Jan Haderka [ 18/Sep/12 ] |
|
Actually MockNodeTest has already 3 tests for different path that covers method pretty well ... and tests are still passing even after my changes. |