currently evaluating ReadyAPI.
One of the usage scenarios we want to tackle is the ability to work with re-usable testfragments in ReadyAPI. These should be relatively small tests which can be ‘knotted together’ in our Integration test suites.
The key thing here is that changes being done on testfragments are taken over in the integration test suites. So not just a plain import & export of testcases (which result in loss of changes in imported testcases)
Can anyone tell if this usage scenario is being supported in current version of ReadyAPI?
As far as I know, there is something called a "composite project" option within ReadyAPI. This allows you to run small tests within integration test suites, it also benefits the team by team sharing.
Please find the link below to read up more on this.
Is this what you was looking for? Apologies if I've misunderstood your query
If I understand you correctly, yes you can make reusable components, I do this extensively. The quick answer is you use the the Run TestCase Test Step, Please see the following posts I've made previously which expand on this:
Let me know if this answers your query, if not I can try to expand further.
Note: A Composite Project just relates to the way it is stored on the disk. Composite projects split the single project file into multiple files, thus making Ready API play nicer with source control.
In addition to what I mentioned above you can also create stand alone reusable Groovy Script libraries, See:
The first line of this page is probably the best description of their use:
"ReadyAPI supports the libraries for Groovy classes. With these libraries, you can centralize common tasks and functionality, or create full-scale script extensions to be used within your projects."
thanks for the help, this looks very promising indeed!
I will dive into it, and let you know if I have questions!