Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Full cycle testing

Pros of RCPTT - readability of the test script, recorder, clear separation of setup vs tests
Cons of RCPTT - slow execution of the tests (it takes time for the tool to assemble the AUT), no documented way to run the tests from the workspace where you are developing your code, assertions can only be done on objects reachable from the UI

Pros of SWTBot - all java based, runs directly from the IDE, can tests UI and Java model
Cons of SWTBot - tests are hard to produce and read, they appeared to be more brittle

Overall I think they both cover a different use case. SWTBot is really neat for unit testing (e.g test a view, an editor, a dialog), whereas RCPTT is best suited for integration tests.

HTH



On 15-10-23 02:27 PM, Eugene Kondrashev wrote:
Appreciate your comment much.
I was looking into swtbot as a result of early research. Are there any difference between swtbot and rcptt? I was trying to find comparison between those two, but failed to find any reasonable pros/cons arguments. 

2015-10-23 21:11 GMT+03:00 Pascal Rapicault <pascal@xxxxxxxxxxxxx>:
Your best bet it is use RCPTT (https://www.eclipse.org/rcptt/)
It allows to drive the Eclipse UI, write assertions, etc.
The tests written with RCPTT can be executed using a Maven plugin.

However know that at this point RCPTT does not deal with installation / uninstallation using p2, so you may have to resort to write something manually for this.


On 15-10-23 02:04 PM, Eugene Kondrashev wrote:
Hi guys,
I'm interest in implementing full cycle testing for eclipse plugin.

By full cycle I mean, testing starting from installation, launching, execution basic operations(crud for projects/files), perhaps compilation/execution of some classes(jdt), shutdown, etc.
In other words common scenarios would be:
launch -> installation -> restart-> create project->verify operation->shutdown
launch -> installation -> restart -> uninstallation
...
Those scenarios should be executed with maven.

Are there any instruments available to implement such testing scenarios? Any similar examples?

Thanks,
Eugene


_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user


_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user



_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user


Back to the top