Bug 267084 - [tests] Automate XSL Tools Smoke Tests using SWTBot
Summary: [tests] Automate XSL Tools Smoke Tests using SWTBot
Status: RESOLVED INVALID
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.xsl (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P5 enhancement (vote)
Target Milestone: 3.4   Edit
Assignee: wst.xsl-triaged CLA
QA Contact: David Carver CLA
URL:
Whiteboard:
Keywords: bugday, helpwanted
Depends on:
Blocks:
 
Reported: 2009-03-04 14:24 EST by David Carver CLA
Modified: 2011-06-02 23:20 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 David Carver CLA 2009-03-04 14:24:44 EST
XSL Tools will need to go through UI testing and smoke test verification.  Currently this is a manual process and prone to human error when doing the tests.  From the following blog entry:

http://model-driven-blogging.blogspot.com/2009/03/shuangxi-effect-ui-testing-and.html

It appears that SWTBot could be used to automate the Smoke Testing for XSL Tools, and other WTP projects.   I'll use XSL Tools as a Proof of Concept on this.
Comment 1 David Carver CLA 2009-04-29 19:45:37 EDT
retargetting for 3.2
Comment 2 David Carver CLA 2009-09-02 15:24:33 EDT
Assigning inbox items to triaged since these have all be triaged.
Comment 3 Jesper Moller CLA 2011-06-02 19:04:17 EDT
I'll take a stab at this
Comment 4 Jesper Moller CLA 2011-06-02 19:24:44 EDT
I guess there's a potential license problem using the periodic table and associated XSL from the book (as mentioned on http://wiki.eclipse.org/XSLT_Tools/SmokeScenarios ) 
I'll consider a different instance+schema.

Also, should this go in a separate test plugin, or org.eclipse.wst.xsl.ui.tests?
Comment 5 David Carver CLA 2011-06-02 23:20:39 EDT
(In reply to comment #4)
> I guess there's a potential license problem using the periodic table and
> associated XSL from the book (as mentioned on
> http://wiki.eclipse.org/XSLT_Tools/SmokeScenarios ) 
> I'll consider a different instance+schema.
> 
> Also, should this go in a separate test plugin, or
> org.eclipse.wst.xsl.ui.tests?

I'd just add them to xsl.ui tests, and let them run with every build.  As for the licensing, could always ask IP about it, and email Elliote Harold the original author.  He's on twitter as well. :)