Thread: Robot - basic question

Hi,

I am currently struggling with a problem I really hope someone here can help with:
Our corporate tool of choice for test automation is Robot, my problem is I am being told it is only possible start planning and scripting for automated testing using Robot once the application has been built, manually tested and will not change in future.

This seems a little off to me as I thought you could tie verification points to elements of the software (UML) design and therefore create some basic tests while the software was in development, hence increasing the test efficiency.

Any and all help appreciated.

Kind regards,
A PM

Hi,

It is very true that there is no point in automating any application that is not stable enough. This limiatation is not with Robot alone but with any tool.

Reason behind this is since Automation is built upon objects in the AUT, if objects / Navigation flows keep changing very frequently, the scripts would have to be changed as frequently.

Yes but incase the application is in Dev stage but is stable to a good extent, we can definitely kick off automation. As long as the Navigational flow remains more or less the same and Change requests are limited ot Object additions or property changes, scripts can be maintained.

Using VP's we can definitely find out as to what the expected object / property would be and accordingly configure our scripts

Originally Posted by bizzzzzare

Hi,

It is very true that there is no point in automating any application that is not stable enough. This limiatation is not with Robot alone but with any tool.

Reason behind this is since Automation is built upon objects in the AUT, if objects / Navigation flows keep changing very frequently, the scripts would have to be changed as frequently.

Yes but incase the application is in Dev stage but is stable to a good extent, we can definitely kick off automation. As long as the Navigational flow remains more or less the same and Change requests are limited ot Object additions or property changes, scripts can be maintained.

Using VP's we can definitely find out as to what the expected object / property would be and accordingly configure our scripts

Thanks for your help bizzzzzare.

I completely agree with the reply by Bizzzare

Hi dude,

You can do one thing, you have got all the requirements and the test plan for it. Using Rational test manager you can start to create a complete Automation test plan wherein You Create the Plan and the whole structure of how the tests would run and at what iteration(of SDLC. like inception ellaboration). and all those thing this would surely help u speed up things and make you ready for scripts.

once the build is delivered you dont need to wait just playback the whole apllication and create all the needed script with the VPs and then test it.