This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 172682 - Create more test cases for the validation plug-in
Summary: Create more test cases for the validation plug-in
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P2 enhancement (vote)
Target Milestone: ---   Edit
Assignee: David Whiteman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-02 11:40 EST by amehrega CLA
Modified: 2012-01-03 13:47 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description amehrega CLA 2007-02-02 11:40:12 EST
We need to create more test cases for the validation plug-in.  We specifically need test cases that will handle import and include statements in schema files.
Comment 1 David Whiteman CLA 2007-03-14 15:58:40 EDT
We also need more/better tests for validating individual SML documents.  In fixing bug 177269, I realized that we must not be currently testing these at all, since a change made to support better marker output in the last month was making an assumption that only is true in the case of validating SML-IF documents.
Comment 2 David Whiteman CLA 2007-03-27 11:30:25 EDT
We need new tests for lots of useful variations on rule bindings, including having a ruleAlias but no documentAlias, using baseURI prefixes, "wildcard" lookup with URIs, multiple rules bound to the same doc alias, etc.
Comment 3 David Whiteman CLA 2007-04-18 16:41:32 EDT
Valentina, is your attempt to check in the interop samples part of this bug report?  Or should that be a separate one?
Comment 4 Valentina Popescu CLA 2007-04-18 23:27:00 EDT
I plan to use 181045 to check in the SMLIF usecases
Comment 5 Valentina Popescu CLA 2007-11-29 13:52:11 EST
moving target to i8
Comment 6 David Whiteman CLA 2007-12-07 10:06:46 EST
The process already dictates that testcases should be created.  Also, this is an ongoing task that cannot be closed.  However, perhaps this should be broken into granular defects to address specific testcases to be created, so that the progress can be tracked.
Comment 7 amehrega CLA 2008-01-02 13:37:26 EST
closing