Hi,
my company has recently started using Rational
Robot to automate the testing of our products. We've found that because Robot
effectively needs a completed GUI before the tests can be created the test
design etc phase of our development projects now starts later in the project
that when we used traditional written test plans. This causes the duration of
our project to now take longer than they used to.
I fully appreciate that future phases of the
project will have reduced testing times because the tests will be automated, but
this is not of such great benefit as we originally thought since our particular
applications often require new GUIs to be developed for each phase / iteration
in an applications development.
Has anyone else had this problem or can recommend
an approach where we reduce our project delivery times and start the testing
phase earlier than before the GUI is complete.
thanks,
Derek |