Forum Discussion
FredrikWiden
11 years agoNew Contributor
Thanks for the quick reply.
We're using WADL but I think I've pretty much found how to update testcases using Groovy through detective work. This is what I mean when I talk about editing the test cases, poor choice of words by me. Although I'd be focusing more on updating the json request and assertions of the response rather than the definition itself.
The thing is though that test cases or even entire test suites might become superfluous and if that happens I don't want to force the user to manually go through all the test cases. On top of that if I can't just remove them all at the beginning of script execution and create everything from scratch I'll have to implement checks if it exists from before then update otherwise create. It's possible but it would be easier to just remove all and create them from scratch.
If it isn't possible in groovy to remove test cases and suites I'll probable try to move all the test cases to a Remove_this test suite and rename test suites to remove. Then create everything from scratch.
I'm a tester and will soon have to work on automated tests for a database migration and a new system for calculating compensation for a benefit. I'm just helping some of our developers automate their unit tests while I wait for requirements to get done so I can start working with that. So I don't know how much time I'll have to do this.
Also while I'm at it are there any good resources for groovy I should know about? I work alot with shell script, perl etc and sometimes even some java and for all of those google usually have the answers I seek. But I'm having a hard time finding good information about groovy.
We're using WADL but I think I've pretty much found how to update testcases using Groovy through detective work. This is what I mean when I talk about editing the test cases, poor choice of words by me. Although I'd be focusing more on updating the json request and assertions of the response rather than the definition itself.
The thing is though that test cases or even entire test suites might become superfluous and if that happens I don't want to force the user to manually go through all the test cases. On top of that if I can't just remove them all at the beginning of script execution and create everything from scratch I'll have to implement checks if it exists from before then update otherwise create. It's possible but it would be easier to just remove all and create them from scratch.
If it isn't possible in groovy to remove test cases and suites I'll probable try to move all the test cases to a Remove_this test suite and rename test suites to remove. Then create everything from scratch.
I'm a tester and will soon have to work on automated tests for a database migration and a new system for calculating compensation for a benefit. I'm just helping some of our developers automate their unit tests while I wait for requirements to get done so I can start working with that. So I don't know how much time I'll have to do this.
Also while I'm at it are there any good resources for groovy I should know about? I work alot with shell script, perl etc and sometimes even some java and for all of those google usually have the answers I seek. But I'm having a hard time finding good information about groovy.