Forum Discussion
mydoghasworms
12 years agoNew Contributor
I think you have somehow missed the point of my suggestion, or maybe I have not explained myself well.
The suggestion is to make a server application out of soapUI, as an alternative to the desktop app i.e. instead of running it on the desktop, you would install it on a server and access it through a web interface.
The functionality would remain the same, i.e. you have projects where you add service definitions and test cases and execute them. The projects could reside as XML files on the server or even in a database.
It would allow users to collaboratively edit projects, define test cases etc. In addition, you could add functionality such as the scheduling of tests.
(Yes, versioning of projects would be a neat idea too, though arguably you don't need SVN for that - nor Jenkins ;-) )
The suggestion is to make a server application out of soapUI, as an alternative to the desktop app i.e. instead of running it on the desktop, you would install it on a server and access it through a web interface.
The functionality would remain the same, i.e. you have projects where you add service definitions and test cases and execute them. The projects could reside as XML files on the server or even in a database.
It would allow users to collaboratively edit projects, define test cases etc. In addition, you could add functionality such as the scheduling of tests.
(Yes, versioning of projects would be a neat idea too, though arguably you don't need SVN for that - nor Jenkins ;-) )