Functionality & Best Practices: Validate Database
Hi all, I'm a SOAP UI newbie & am using a trial version of Pro. I know this is probably very easy, but I'm wondering what the best approach/practices are.
I have several SOAP services that (among other things) perform CRUD actions on Oracle 10g (release 2) database tables. I have numerous test cases set up to challenge the logic & functionality of those services based on applicable business rules. Being able to create a data storage area for input values was worth the Pro upgrade by itself! But I'm still having to go to SQL Developer manually to verify that the data was inserted or updated properly & I know there is a better way.
I have also set up a project level JDBC connection which appears to be working perfectly.
Not sure what the best approach is to eliminate the manual database inspection step. I've read about assertions, JCBC Requests & a little bit about scripts, but not sure about the best way to put it all together.
All advice greatly appreciated!
I have several SOAP services that (among other things) perform CRUD actions on Oracle 10g (release 2) database tables. I have numerous test cases set up to challenge the logic & functionality of those services based on applicable business rules. Being able to create a data storage area for input values was worth the Pro upgrade by itself! But I'm still having to go to SQL Developer manually to verify that the data was inserted or updated properly & I know there is a better way.
I have also set up a project level JDBC connection which appears to be working perfectly.
Not sure what the best approach is to eliminate the manual database inspection step. I've read about assertions, JCBC Requests & a little bit about scripts, but not sure about the best way to put it all together.
All advice greatly appreciated!