SoapUI OS over SoapUI Pro
Hi, For the project I am working on we are currently using SoapUI Pro for functional testing. However the prices for it are quite big so we are considering the possibility of switching for SoapUI...
Forum Discussion
Subjective. That depends on what features of Pro are you currently using. Would you please clarify?
Of course, the test can be executed from Jenkins.
For different environments, use external properties file for configuring environment specifics. For example, use separate file for each dev.properties, qa.properties, production.properties for environment specifics and pass the respective file for the execution as per the environment. This each property file can include the data ranging from data base, to endpoints.
If someone can handle or write code for the custom needs(if any), then SoapUI OS is pretty good enough to use. Of course, it may take some time to implement and require more programming skills like a developer. For QA engineers, thats where Pro helps to get things independantly and little quicker.
Of course, the test can be executed from Jenkins.
For different environments, use external properties file for configuring environment specifics. For example, use separate file for each dev.properties, qa.properties, production.properties for environment specifics and pass the respective file for the execution as per the environment. This each property file can include the data ranging from data base, to endpoints.
If someone can handle or write code for the custom needs(if any), then SoapUI OS is pretty good enough to use. Of course, it may take some time to implement and require more programming skills like a developer. For QA engineers, thats where Pro helps to get things independantly and little quicker.
Thanks nmrao,
I will analyze each need of our team and come back with comments and help requests if needed. The idea with the external properties for configuring environment is a nice one!
- Yes. using external properties file, use property expansion in the project and pass it at run time. This even reduces the effort of changing environment name each time.
