[MAGNOLIA-2467] Some tests are not cleaning up after themselves Created: 05/Nov/08 Updated: 23/Jan/13 Resolved: 05/Nov/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.0 |
| Fix Version/s: | 4.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Yuriy Dmitriev | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
$ uname -a |
||
| Attachments: |
|
| 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: |
| Description |
|
$ svn up step to reproduse: Results : Tests in error: Tests run: 374, Failures: 0, Errors: 1, Skipped: 0 |
| Comments |
| Comment by Yuriy Dmitriev [ 05/Nov/08 ] |
|
Its maven build log. |
| Comment by Magnolia International [ 05/Nov/08 ] |
|
Could reproduce by running the specific test on its own. It was working for us only because the previous test had set the MgnlContext instance - in my case MgnlGroupTest - now fixed. |
| Comment by Magnolia International [ 05/Nov/08 ] |
|
done on trunk - please reopen if you encounter similar issues again. Thanks for the heads up ! |
| Comment by Yuriy Dmitriev [ 05/Nov/08 ] |
|
Thanks )) all work. |
| Comment by Philipp Bracher [ 14/Nov/08 ] |
|
Use MgnlTestCase which removes all the hassle from the developer. |
| Comment by Magnolia International [ 14/Nov/08 ] |
|
Depending on what you're testing, that's not always the case. Sometimes I want to verify the behaviour of a (easymock) mock context, for instance. |