| Summary: | [impact] Impact analyzer doesn't handle derived properties | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] OCL | Reporter: | Axel Uhl <eclipse> | ||||
| Component: | Core | Assignee: | OCL Inbox <mdt-ocl-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | ed | ||||
| Version: | 3.1.0 | ||||||
| Target Milestone: | 3.1.0 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Axel Uhl
Created attachment 196731 [details]
Patch handling derived properties, including tests
This patch contains an implementation for the TracebackStep (default) approach which can handle derived properties. It extends the o.e.o.examples.impactanalyzer.testmodel.company model by some derived properties which are then used by a few new tests. Note that at least for one test there is a check for the current IA implementation strategy, ensuring the test is only applied for the TracebackStep strategy.
I ran the default and IA tests with this patch with no errors.
Tests run. Changes small and confined to examples.impact.... +1. Committed to CVS for RC3 Closing |