Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324037 - Improve IUBundleContainerTests and check for cases where profile is stale
Summary: Improve IUBundleContainerTests and check for cases where profile is stale
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.7 M2   Edit
Assignee: Curtis Windatt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 276326
Blocks:
  Show dependency tree
 
Reported: 2010-08-30 17:34 EDT by Curtis Windatt CLA
Modified: 2010-09-01 11:56 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Windatt CLA 2010-08-30 17:34:20 EDT
Follow up to bug 276326

1) We should add a couple new test cases to check that the profile resolution gets used.

2) The tests should delete the profile in a try/finally otherwise one failure can lead to others (the later tests look up information in the profile)

3) While the tests pass and my manual testing passed, there still may be ways to get a stale profile.  One possibility would be when switching from slicing to planning, while the planner would actually fail, we never get to that point because the profile contains the previously sliced IUs.
Comment 1 Curtis Windatt CLA 2010-08-31 17:21:45 EDT
1) Still working on this, I have a test that will modify the profile during the test so the if the resolveWithProfile is running correctly it will get different results.

2) Fixed in HEAD.

3) Changing slicing vs planning forces the profile to be recreated because the properties are immutable.  I think we are ok here.
Comment 2 Curtis Windatt CLA 2010-09-01 11:56:32 EDT
Fixed in HEAD, see IUBundleContainerTests.  I also had to add some new dependencies to the test bundle to modify the profile during the test.