jjnair / fest

Automatically exported from code.google.com/p/fest
0 stars 0 forks source link

Create DSL for testing GUIs using Groovy #4

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Use Groovy to create a Domain-Specific Language for testing GUIs. The
purpose is to make creation (and maintenance) of tests easier.

Original issue reported on code.google.com by Alex.Rui...@gmail.com on 16 May 2007 at 12:52

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
hi,
why using Groovy for DSL ? What is the support it provides in this sense ?

thanks,
valerio

Original comment by valerio....@gmail.com on 4 Jun 2007 at 11:48

GoogleCodeExporter commented 8 years ago
Hi Valerio,

AFAIK, with Groovy we can create an API (or DSL, Domain Specific Language) that 
is
much shorter, cleaner and easier to read and write. I don't have any experience 
with
Groovy at all, but I've been reading about creating DSLs with Groovy and it 
looks
pretty useful.

The plan is to experiment with Groovy to see if we can accomplish this goal. My 
good
friend Andres Almiray (who has experience with Groovy) offered his help 
regarding
this topic. You can find his blog at http://jroller.com/page/aalmiray

Best regards,
-Alex.

Original comment by Alex.Rui...@gmail.com on 4 Jun 2007 at 11:55

GoogleCodeExporter commented 8 years ago
I'd be glad to help too if you have anything you want me to look at.
Cheers, Paul.

Original comment by robl...@gmail.com on 8 Jun 2007 at 4:10

GoogleCodeExporter commented 8 years ago
I'd be glad to help too if you have anything you want me to look at.
Cheers, Paul.

Original comment by Paul.Kin...@gmail.com on 8 Jun 2007 at 4:17

GoogleCodeExporter commented 8 years ago
Started work last night for Groovy-based DSL

Original comment by Alex.Rui...@gmail.com on 23 Jun 2007 at 5:44

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I included some FEST/Groovy examples in my Agile 2007 Open Source Testing Tools 
talk
yesterday. It was all using Groovy, it went like:
(1) Create a web service
(2) Test web service using Groovy
(3) Create SwingBuilder GUI for web service
(4) Test using FEST
(5) Create Web form Groovlet for web service
(6) Test using Groovyized Canoo WebTest

Original comment by Paul.Kin...@gmail.com on 16 Aug 2007 at 5:42

GoogleCodeExporter commented 8 years ago
Thanks guys for offering help. I truly appreciate it :)

I'm sorry for the late reply (I hope you can see this message). Google Code 
never
notified me about new comments on this issue :(

-Alex.

Original comment by Alex.Rui...@gmail.com on 17 Aug 2007 at 2:05

GoogleCodeExporter commented 8 years ago
Thanks Paul for including FEST at your session at Agile 2007. That is totally
awesome! What a great honor for us! Totally cool!! :)

-Alex.

Original comment by Alex.Rui...@gmail.com on 17 Aug 2007 at 2:10

GoogleCodeExporter commented 8 years ago
Any thoughts about the FEST + Groovy + Easyb article?
http://www.jroller.com/aalmiray/entry/fest_easyb_making_ui_testing

Do you think this is the direction forming a DSL for FEST-Swing might head?

Original comment by simeon.f...@gmail.com on 28 Jun 2008 at 5:16

GoogleCodeExporter commented 8 years ago
I really, really like what Andres has done with easyb and FEST. I think that by
combining these two tools, Andres has significantly reduced the amount of work 
from
our part. I've been discussing with Andres several approaches for the FEST 
Groovy DSL
and we will start a prototype pretty soon. At the same time I will be posting 
our
progress in the mailing list as soon as we start and, as always, feedback is 
welcome!! :)

Original comment by Alex.Rui...@gmail.com on 2 Jul 2008 at 11:26

GoogleCodeExporter commented 8 years ago
I really like the result too. My initial reaction would be to recommend that we
encourage easyb to be the best bdd framework that it can be and FEST to be the 
best
GUI testing framework that it can be. Then using the two together should 
hopefully be
easy and powerful. Of course, that doesn't always work in practice.

Original comment by Paul.Kin...@gmail.com on 3 Jul 2008 at 10:38

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Set the module as a label, instead of being part of the title.

Original comment by Alex.Rui...@gmail.com on 30 Nov 2008 at 11:54

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
did my comments get submitted?

Original comment by Michel.L...@gmail.com on 2 Dec 2008 at 9:22

GoogleCodeExporter commented 8 years ago
I just posted a rather large comment with my DSL experience in my current 
project,
but I don't see it. Is this under review or something?

Original comment by Michel.L...@gmail.com on 2 Dec 2008 at 9:24

GoogleCodeExporter commented 8 years ago
Hi Michel,

I don't know why your comment didn't appear. It is not under review or anything 
like
that. It should have shown (probably a bug in Google Code?)

Please feel free to send me an e-mail to alex.ruiz.05 at gmail.com with your 
comment.
I'll re-post it.

Thanks,
-Alex

Original comment by Alex.Rui...@gmail.com on 2 Dec 2008 at 1:22

GoogleCodeExporter commented 8 years ago
Hi Michel,

I saw your comment about a (very nice) Groovy DSL on issue 221. Is that the 
comment
you were referring to?

-Alex

Original comment by Alex.Rui...@gmail.com on 2 Dec 2008 at 1:24

GoogleCodeExporter commented 8 years ago
I actually need to create a new module in the issue tracker for this issue. We 
have
decided that the Groovy DSL will be a separate module, with its own release 
cycle. We
prefer to have this module to depend more on the releases of Groovy itself 
rather
than FEST. For now, I'll assign it to release 1.1.

Original comment by Alex.Rui...@gmail.com on 4 Dec 2008 at 6:01

GoogleCodeExporter commented 8 years ago

Original comment by Alex.Rui...@gmail.com on 5 Feb 2009 at 5:10

GoogleCodeExporter commented 8 years ago

Original comment by Alex.Rui...@gmail.com on 5 Feb 2009 at 7:12