Initiate test cases [message #736038] |
Thu, 13 October 2011 12:31 |
Richard Skoog Messages: 62 Registered: October 2011 |
Member |
|
|
Hi,
Does anyone have a winning concept for how to initiate test cases checking all the stuff that has to be active and reset before running a new test case?
As a start there is the build in module "complex_app_init", but that one only checks if the the application is started and that the window is active. There is always more stuff to initiate to get a robust test suite.
For example how do I do a check if old projects are available and then they should be deleted? Of course I can do select of the project and delete, but if it isn't available then I will get an error when trying to select and delete something which isn't available.
One way to handle this could be if there is some way to do something like an IF statement.
IF <projects available> THEN
...
ENDIF;
Any ideas?
Regards Richard
[Updated on: Thu, 13 October 2011 13:04] Report message to a moderator
|
|
|
Re: Initiate test cases [message #736053 is a reply to message #736038] |
Thu, 13 October 2011 13:10 |
Andrey Platov Messages: 28 Registered: July 2009 |
Junior Member |
|
|
Hi Richard,
There are some tools on the market introducing a concept of "Contexts", which are supposed to work exactly like you described. If speak about testing of Eclipse applications some of these tools provides following types of contexts out-of-the-box, like:
* Workspace Context - ensuring that particular files/projects are present (or absent) in the workspace before test run.
* Workbench Context - ensuring specific perspective, views, editors, etc are open or closed before test run.
* Other
Very important thing about Context is it is not only to "check" that your AUT is in required state, but also force your application into required state. For example, if some test specifies that your application requires project A with concrete set of files, the tool will check these files to be presented and provision them before test run (if they are not present).
This is really cool concept, which drastically changes your way to test automation.
I do not know if it would be easy to add such concept to Jubula, however since Jubula is an open source project this would be doable. Also it looks to be nice idea to come with at Jubula Competition at the EclipseCon
Kind Regards,
Andrey
|
|
|
|
|
|
|
Re: Initiate test cases [message #742065 is a reply to message #741417] |
Thu, 20 October 2011 06:19 |
Richard Skoog Messages: 62 Registered: October 2011 |
Member |
|
|
That's a solution, but not maybe the nicest one. It will be a lot of test cases to cover all dialogs. Is there any available test case to close a dialog (press the "X" in the corner of the window)?
My main question was if there is some kind of a general test case or other funtionality within Jubula that kills all hanging dialogs without knowing the name of the dialog, but probably that's not available then?
Regards Richard
[Updated on: Thu, 20 October 2011 06:25] Report message to a moderator
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03681 seconds