Bug 147131 - [performance testing] XSD validation performance tests are broken
Summary: [performance testing] XSD validation performance tests are broken
Status: CLOSED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.xsd (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.5.1 M151   Edit
Assignee: Valentin Baciu CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2006-06-14 18:11 EDT by Valentin Baciu CLA
Modified: 2006-09-26 10:02 EDT (History)
2 users (show)

See Also:


Attachments
Proposed fix (70.89 KB, patch)
2006-06-15 14:23 EDT, Valentin Baciu CLA
no flags Details | Diff
Corrects build.properties (592 bytes, patch)
2006-07-06 10:57 EDT, Valentin Baciu CLA
no flags Details | Diff
New fixes (5.23 KB, patch)
2006-07-14 15:06 EDT, Valentin Baciu CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Baciu CLA 2006-06-14 18:11:44 EDT
The XSD validator ID has changed with the implementation of
https://bugs.eclipse.org/bugs/show_bug.cgi?id=132230. The XSD validation
performance tests have this ID hardcoded in quite a few places. The validation
framework cannot find the proper validator when looking it up based on the
wrong ID and all XSD validation performance tests fail.
Comment 1 Keith Chong CLA 2006-06-14 18:14:57 EDT
Hi Valentin, this one is yours.
Comment 2 Valentin Baciu CLA 2006-06-15 11:36:58 EDT
In addition to the validator ID it appears that the XSD editor ID has changed as well. Together, these changes pretty much broke every test in this suite.

Keith, can you comment on the editor ID change? Should I modify the test cases to adapt to the new editor ID or will the editor ID be reverted to the previous value to preserve backward compatibility?
Comment 3 Valentin Baciu CLA 2006-06-15 14:23:20 EDT
Created attachment 44564 [details]
Proposed fix

Instead of simply replacing the many occurrences of the editor and validator IDs scattered across the code, I decided to refactor the code by introducing a couple of base classes. This will concentrate the references to these IDs in at most a few places. For the editor ID I've been able to reuse a constant defined in the XSDEditorPlugin. This will ensure that if the editor ID changes the change will be propagated here easily. Could not find a similar constant for the validator. Avoiding these "magic strings" https://bugs.eclipse.org/bugs/show_bug.cgi?id=136781 would go a long way to avoid breakages like this one.

While I was at it, I updated the copyright headers and organized imports. I did a PDE build as well, so the plugin should build nicely.

I was able to run most test (except the OAGIS ones, which I don't really know how to setup).

Jeff, please test and feel free to commit if everything seems fine.
Comment 4 Jeffrey Liu CLA 2006-06-19 09:21:15 EDT
Patch committed
Comment 5 Valentin Baciu CLA 2006-07-06 10:56:03 EDT
The tests still cannot run on the performance machine. The plugin jar file is missing test.xml.
Comment 6 Valentin Baciu CLA 2006-07-06 10:57:33 EDT
Created attachment 45843 [details]
Corrects build.properties
Comment 7 Valentin Baciu CLA 2006-07-06 10:58:21 EDT
Comment on attachment 44564 [details]
Proposed fix

Already applied.
Comment 8 Jeffrey Liu CLA 2006-07-06 15:23:26 EDT
Comment on attachment 45843 [details]
Corrects build.properties

Patch applied.
Comment 9 Jeffrey Liu CLA 2006-07-06 15:23:41 EDT
Comment on attachment 45843 [details]
Corrects build.properties

Patch applied.
Comment 10 Valentin Baciu CLA 2006-07-14 15:06:13 EDT
Created attachment 46311 [details]
New fixes

Corrects the editor ID missed in one file. Corrects the package name for 6 scalability tests in test.xml.
Comment 11 Jeffrey Liu CLA 2006-07-14 15:19:41 EDT
Comment on attachment 46311 [details]
New fixes

Patch applied.
Comment 12 Valentin Baciu CLA 2006-07-31 11:21:21 EDT
All tests are running now.
Comment 13 David Williams CLA 2006-09-07 09:30:35 EDT
performance bugs should use performance keyword (not [performance] in subject). 
Comment 14 Valentin Baciu CLA 2006-09-24 16:10:08 EDT
Verified.
Comment 15 Valentin Baciu CLA 2006-09-26 10:02:48 EDT
Closing.