Re: [Framework-Team] Plone 4.1 Framework Team M eeting Minutes– 17 August, 2010

2010-08-19 Thread Eric Steele
On Aug 19, 2010, at 10:24 AM, Godefroid Chapelle wrote:
 
 Reason why I insist on automated tests. Functional tests run too slowly 
 to rely on developers running them regularly. We need to delegate to 
 Hudson or buildbot.

I agree completely. 

I very nearly* have a Hudson/Selenium Grid/plone.app.testing pile running 
Selenium tests automatically across multiple browsers and machines. If I can 
convince the kid to give me a few free hours to work today, I'll wrap it up and 
write up what I have.

* For some definition of nearly

Eric
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: [Framework-Team] Plone 4.1 Framework Team M eeting Minutes– 17 August, 2010

2010-08-19 Thread Eric Steele
On Aug 19, 2010, at 12:32 PM, Godefroid Chapelle wrote:
 Le 19/08/10 18:14, Eric Steele a écrit :
 On Aug 19, 2010, at 10:24 AM, Godefroid Chapelle wrote:
 
 Reason why I insist on automated tests. Functional tests run too slowly
 to rely on developers running them regularly. We need to delegate to
 Hudson or buildbot.
 
 I agree completely.
 
 I very nearly* have a Hudson/Selenium Grid/plone.app.testing pile running 
 Selenium tests automatically across multiple browsers and machines. If I can 
 convince the kid to give me a few free hours to work today, I'll wrap it up 
 and write up what I have.
 
 Have you written a new layer ? Have you looked at gocept.selenium ?
 
 * For some definition of nearly
 
 Eric

I wrote a new layer, mainly because I wanted to figure out how it all worked. 
I've put up a quick screencast of the whole thing in action, if anyone's 
interested. http://blip.tv/file/4023258

Basically Hudson controls a Selenium Grid which doles out requests to the 
requested browsers based on RC instance availability. The testcase layer 
accepts environment variables for ZServer host/port and Selenium 
host/port/browser. I've created one job per browser (Firefox and Safari in the 
screencast), passing in a new port and browser string environment var in each. 
Selenium Grid will pass the request along to the first available RC instance 
with that browser identifier and that'll hit the one-off ZServer created by the 
testcase.

We should be able to kick off each of these jobs after the Plone 4 build runs 
and AFAIK they'll run simultaneously without issue.

The one thing I'm missing at the moment is preventing them from running during 
normal test runs, but David's shown me a way forward on that.

Eric
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: [Framework-Team] Plone 4.1 Framework Team M eeting Minutes– 17 August, 2010

2010-08-18 Thread Dorneles Treméa
Hello,

 • 10888 (Make KSS optional)
 • Quick consensus
 • Selenium testing
 • KSS does this. Plone doesn't. Do we require plip
 to add this for rewritten work?
 
 
 Short: This plip is a chance for the FWT to give a strong push in the 
 right direction by REQUIRING AUTOMATED tests for JS code.
 
 Longer:
 
 Plone runs more and more js code (iow in the browser), too much being 
 untested (AFAIK).
 
 It is time to require automated tests for new JS code added to Plone 
 core; both js unit and functional (selenium or windmill) tests.
 
 It would be an opportunity for the community to experiment and decide on 
 best practices in this context.
 
 We need these experience and tests as we plan to integrate more complex 
 code (iow code easier to break) like the foreseen Deco editor.
 
 I'd be happy to participate to a sprint focused on setting up those 
 practices and building a set of tests for existing JS code.
 
 However, I am not proposing to pull the community : I tried at various 
 sprints and miserably failed.
 
 
 Godefroid, I am definitely interested to learn from your experience in
 this area. Regarding functional testing of Javascript, would you
 recommend looking at KSS to see how it is done there, or are there newer
 best practices that have emerged since those tests were written?

from his recent work on Canonical, I'm sure Sidnei has some great
insights to share here, don't you Sidnei? :-)

--
Dorneles Treméa
Enfold Systems
http://www.enfoldsystems.com
Fax +1 832 201 8856
Office +1 713 942 2377 Ext 211
Skype dtremea

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team