Great experience with Groovy steps
I'd like to commend the eviware team for choosing Groovy as a scripting language and for SoapUI's implementation of it.
I'm primarily a tester, but I can do a little bit of scripting and have some knowledge of OO concepts. I'm finding the Groovy steps to be pretty painless to implement: the language is not troublesome for a novice and the steps themselves, which can be tested on the spot, are novice-friendly. I've even managed to create a class and use it successfully in a step.
And since Groovy uses Java, help with the language itself is easy to find on the Web. The SoapUI docs were also very helpful in getting me started.
I'm already far further along on some common testing task items than I thought I ever would be. Within a few minutes, I can create steps to generate random numbers and date-time stamps - normally this doesn't end well for me.
Thanks eviware and Groovy developers; I can easily say that it's been a pleasure so far learning how to use this aspect of SoapUI.
I'm primarily a tester, but I can do a little bit of scripting and have some knowledge of OO concepts. I'm finding the Groovy steps to be pretty painless to implement: the language is not troublesome for a novice and the steps themselves, which can be tested on the spot, are novice-friendly. I've even managed to create a class and use it successfully in a step.
And since Groovy uses Java, help with the language itself is easy to find on the Web. The SoapUI docs were also very helpful in getting me started.
I'm already far further along on some common testing task items than I thought I ever would be. Within a few minutes, I can create steps to generate random numbers and date-time stamps - normally this doesn't end well for me.
Thanks eviware and Groovy developers; I can easily say that it's been a pleasure so far learning how to use this aspect of SoapUI.
