Community
Participate
Working Groups
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.
retargetting for 3.2
Assigning inbox items to triaged since these have all be triaged.
I'll take a stab at this
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?
(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. :)