[swtbot-dev] Antwort: Re: Proposal for a test recorder for SWTBot

[Timur.Achmetow@xxxxxxxxxxxxxx]

Hello,

I think this is a really amazing feature
for the SWTBot project. 
Exist a bug entry for this feature?

When will be this feature ready for
the next release?
____________________________________
Mit freundlichen Grüßen

i.A. Timur Achmetow
Entwicklung

INDUSTRONIC GmbH & Co. KG
Carl-Jacob-Kolb-Weg 1
97877 Wertheim / Germany
fon: +49 (0) 9342/871-240

fax: +49 (0) 9342/871-565
mailto:timur.achmetow@xxxxxxxxxxxxxx
http://www.industronic.com



Von:      
 Aurélien Pupier <aurelien.pupier@xxxxxxxxxxxxxx>
An:      
 SWTBot developers list
<swtbot-dev@xxxxxxxxxxx>
Datum:      
 07.01.2013 11:04
Betreff:    
   Re: [swtbot-dev]
Proposal for a test recorder for SWTBot
Gesendet von:    
   swtbot-dev-bounces@xxxxxxxxxxx

---

Hi Mickaël,

I'm happy to see that you are working on a swtbot recorder :-)
The generated code seems very close to what we would code by hand (except
for i18n and use of IDialogConstants).

I will try it asap.

Thanks


2012/12/19 Mickael Istria <mistria@xxxxxxxxxx>
Hi all,

In the context of JBoss Tools, we spend a lot of time writing tests. We
mainly rely on SWTBot for that, and we find out that a recorder for SWTBot
that would take as input user actions and generate the Java code for that
would be very helpful to save us time, and also to get higher quality reports
(people reporting bugs could directly use this tool to report a test-case).
So we've worked on a simple-but-yet-efficient recorder for SWTBot, together
with Rastislav Wagner (JBoss Tools team too).

Since the JBoss Tools team also has its specific test framework (called
RedDeer), we made this generic and extensible enough to provide the ability
to plug another framework that SWTBot into it. So by default, the generator
would generate code conforming to SWTBot API, but one can easily install
the RedDeer support and then choose to generate code that targets the RedDeer
API; and it's the same for any API.
The implementation just looks at Events and find a matching rule to generate
code for each Event. Support of (1 operation == N events) will probably
come later. It's pretty easy to contribute support for new UI actions,
it's just a matter of providing a new class.

This is in a very early state, but already supports the most common UI
stuff. You can see a demo of the generator in action here: https://vimeo.com/55953990

The contribution is currently there https://git.eclipse.org/r/#/c/9301/
. I'd really like to integrate it into SWTBot soon to gather some usage,
feedback, and contributions. But before I check this into codebase, I'd
like to hear some feedback from this mailing-list.
-- 
Mickael Istria
Eclipse developer at JBoss,
by Red Hat
My
blog - My
Tweets

_______________________________________________
swtbot-dev mailing list
swtbot-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/swtbot-dev




--

Aurelien Pupier
R&D Engineer, BOS Studio Development Leader

email : aurelien.pupier@xxxxxxxxxxxxxx

This message and any attachment (the "message") is intended solely
for the addressees and is confidential. If you receive this message by
mistake, please delete it and notify the sender immediately. Any use not
in accordance with its purpose, any out-spread or disclosure, either as
a whole or partially, is prohibited except with formal approval. Internet
cannot guarantee the integrity of this message, therefore BonitaSoft will
not be liable for the message if modified. 

-- 
This message has been scanned for viruses and 
dangerous content by MailScanner,
and is 
believed to be clean. _______________________________________________
swtbot-dev mailing list
swtbot-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/swtbot-dev