Bug 509281 - [validation] Provide comprehensive QVTd WFRs
Summary: [validation] Provide comprehensive QVTd WFRs
Status: NEW
Alias: None
Product: QVTd
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on: 464693 500254 510348 512738 525710 540746 550155 557995 560427 412341
Blocks:
  Show dependency tree
 
Reported: 2016-12-15 07:29 EST by Ed Willink CLA
Modified: 2020-02-25 03:08 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2016-12-15 07:29:26 EST 
Following the addition of basic validation support via Bug 412341, This planning bug aggregates any further validation issues.
Comment 1 Ed Willink CLA 2017-04-14 04:02:59 EDT 
Big 515237 identifies that deep overlapping enforcement patterns may be ambiguous as to who realizes what. WFR should diagnose this.
Comment 2 Ed Willink CLA 2017-10-04 09:57:30 EDT 
Bug 512738 identifies that RelationCallExp as if then/else is suspect. WFR needed.
Comment 3 Ed Willink CLA 2017-10-07 05:02:17 EDT 
Bug 525710 provides an example of the need to diagnose multi-assignment hazards.
Comment 4 Ed Willink CLA 2018-11-04 04:15:51 EST 
Bug 540746 identifies a need for proactive WFRs to avoid obscure QVTs2QVTi failures.
Comment 5 Ed Willink CLA 2019-08-16 10:07:55 EDT 
Bug 550155 identifies the need for default_values WFRs.
Comment 6 Ed Willink CLA 2019-12-07 15:20:04 EST 
Bug 557995 calls for RelationCallExp argument checking.
Comment 7 Ed Willink CLA 2020-02-25 03:08:25 EST 
Bug 560427 identifies a case in which where calls were impractical iteration-wise. WFR or helper needed.