I don't know Silk but I used Selenium for automated end user test for the 
following reasons :

* open source
* multi-plateform
* do not talk at HTTP level : this is bad. Take control of a real browser : 
this is good.
* used by qooxdoo team : will work with future version, will found help here, 
...

=> our qooxdoo apps can be tested on several OS with several browsers.

My 2 cents.


On 6 juil. 2010, at 17:33, Jim Hunter wrote:

> Thanks for the valuable feedback. We do not use the qooxdoo table in this 
> project so I get to miss all the fun there. And we have already augmented our 
> code a lot to try and enable it to work with Silk, but Silk just doesn't do 
> web apps very well. It was designed for html pages only (ones that generate a 
> 'loaded' event). We are having a big meeting tomorrow to discuss how to 
> proceed and you ahve given me more information to make my case.
> 
> Thanks, and I'll take a look at TemCity, we might be able to use it as well.
> Jim
> 
> 
> On Tue, Jul 6, 2010 at 8:16 AM, Jean-Baptiste BRIAUD -- Novlog 
> <[email protected]> wrote:
> Hi Jim,
> 
> Here some elements :
> * building/packaging/deploying our product automatically was quite a big 
> thing to do.
> We had few ant scripts for some steps but it was not 100% automated. Now it 
> is but it was a big investment.
> 
> * We are currently fighting hard with table widget, Olivier could tell more 
> on that.
> 
> * writing test scenario is still too complex due to locator string.
> We had build an API on top of selenium so the test scenario "vocabulary" (the 
> API) to simplify the writing of test scenarios.
> 
> We have now a continuous build and automated test on each svn commit and this 
> is really helpful.
> We are using TeamCity (free from Idea).
> I'm happy with that solution.
> Still need improvement p, error report. We got a green/re light but we are 
> lacking information on why it is red when it is.
> 
> 
> 
> On 6 juil. 2010, at 16:30, Jim Hunter wrote:
> 
> > For those of you that have been using Selenium to test your UI, what have 
> > been your biggest problems using Selenium with qooxdoo? We are about to 
> > embark on adding testing to our plate and we were thinking of using 
> > Selenium but want to make sure it's a road we should take. We plan on using 
> > the test harness that comes with qooxdoo for testing all our non-visual 
> > code but we think we really need to add UI functional testing as well.
> > Thanks,
> > Jim
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- 
> > http://p.sf.net/sfu/sprint-com-first_______________________________________________
> > qooxdoo-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- 
> http://p.sf.net/sfu/sprint-com-first_______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to