JvanOverveldt
18 years agoOccasional Contributor
Team sharing
Hi,
We are working a while in team to create testcases for one webservice. Unfortunatly we have to conclude that -altough it is a great tool- at this moment soapUI is not designed for teamwork. This is mainly because using a versioning tool like CVS does not allow us to work in one project at te same time.
We believe the problem is that soapUI works with one great project-file. This makes it impossible to work with two persons on one project. We where forced to divide our Webservice into one project per operation so we can work on different operations at te same time. This creates other problems like the use of projectproperties and reusable testcases (like a datasource testcase that is called from almost every other testcase). We have to copy them into each project. One change in those properties/testcases means we have to sync with all other projects. This generates a lot of extra work.
Is it possible to think trough some solutions to make teamwork easier. One of the things could be to save for example Testsuites or even TestCases in seperate files. This way, more people could work on the same project. You can go even futher by enabling CVS or SVN within the software.
I know this might be a feature request with a rather enormous impact on the coding but I believe adding teamsharing posibilities will add great value to your product.
We are working a while in team to create testcases for one webservice. Unfortunatly we have to conclude that -altough it is a great tool- at this moment soapUI is not designed for teamwork. This is mainly because using a versioning tool like CVS does not allow us to work in one project at te same time.
We believe the problem is that soapUI works with one great project-file. This makes it impossible to work with two persons on one project. We where forced to divide our Webservice into one project per operation so we can work on different operations at te same time. This creates other problems like the use of projectproperties and reusable testcases (like a datasource testcase that is called from almost every other testcase). We have to copy them into each project. One change in those properties/testcases means we have to sync with all other projects. This generates a lot of extra work.
Is it possible to think trough some solutions to make teamwork easier. One of the things could be to save for example Testsuites or even TestCases in seperate files. This way, more people could work on the same project. You can go even futher by enabling CVS or SVN within the software.
I know this might be a feature request with a rather enormous impact on the coding but I believe adding teamsharing posibilities will add great value to your product.