JvanOverveldt
Occasional Contributor
Joined 18 years ago
User Profile
User Widgets
Contributions
Strange behaviour loadtests with more threads
The situation: - A testcase with 5 teststeps, each another operation. - Loadtest: 5 threads and Total runs 1000 Problem: The teststeps fail in a strange way: Teststep 2 fails because the answer is not correct. But when I investigate the answer I notice the answer of Teststep 2 is in fact the answer of Teststep 1 (another operation). This way almost every teststep fails and the results of the loadtest are not useable. I can't see why soapUI does this but I think it has something to do with the threads. The problem does not occur when we only run one thread.1.9KViews0likes1CommentDifferent behavior DataSource in LoadTest
In our project we have to run several loadtests with a datasource. We ran those tests with 5 or more threads. When a "Grid" datasource is used, soapUI always selects the next row. So if we put the values 1,2,3,4,5,6,...,20 in the grid and we run with five threads with total runs=20 all of the numbers are used. When we used excel or textfile as grid, only the first 5 values where used. Every seperate thread keeps using the same value. We need the behavior of the "Grid" datasource but we want to use another source. The "loop Datasource" step was no solution because one testcase only ends when all records are read.2KViews0likes0CommentssoapUI does not save 'Outgoing WSS' for endpoint
We have to send several requests with outgoing WSS. When the correct profile is selected we can only run those tests if we do not close the interface tab. After closing the tab and after a soapUI restart the selected profile is gone.2.1KViews0likes0CommentsExporting results via groovy teststep
We want to add a groovy teststep at the end of each testcase that writes the results to a DB or file. I know how to run a case through groovyscript and get the results from this run but I want to get the results from the steps before. What is the best way to go? Can somebody provide a sample script?1.9KViews0likes1CommentTeam 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.2.6KViews0likes1CommentClone assertions: Delete existing assertions
Hi, Many of our test steps use the same assertions. When I notice that I have to create some new ones and delete some of the existing I have to delete all the old assertions manually per teststep. It would be easier to have an option in the Clone Assertion wizard to delete the existing assertions in the target test steps before the cloning. I am aware that this option has some risks when selecting it unintentionally. I think it is best to let the option be unselected by default and give a warning-message before the deletion. It would also be nice that it's possible to delete all assertions at once per testcase.2.2KViews0likes1CommentRafactor tool enhancement
We updated our services and one of the changes is an element that has moved one place deeper in the three structure: old situation: element A - element B - element C new situation: element A - element B - element C It would be nice if it would be possible to link "element C" from the old situation with element C of the new situation. Is this something the team is working on? We are facing major rework of our testcases and it would be nice if we could avoid that.2.2KViews0likes1CommentTestrunner: errors if one or more assertions fail.
If I use the testrunner, it always ends with an error-message if there are failed assertions (see below). It seems that all documentation is generated as it should. Is this a bug or is it supposed to give the error message? I would like to add to this that the use of ":" in the teststep names gives also errors with the generation of the report files. The log shows file errors and the files are not created as it should be. "... Response Headers: {Content-type=text/xml;charset=utf-8, Date=Wed, 30 Jan 2008 12:22:11 GMT, #status#=HTTP/1.1 200 OK, Content-length=1417, Soapaction="", X-powered-by=Servlet/2.4, Server=Sun-Java-System/Application-Server} at com.eviware.soapui.tools.SoapUITestCaseRunner.throwFailureException(SoapUITestCaseRunner.java:377) at com.eviware.soapui.tools.SoapUITestCaseRunner.runRunner(SoapUITestCaseRunner.java:345) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:114) at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:66) at com.eviware.soapui.SoapUIProTestCaseRunner.main(SourceFile:30) "2.5KViews0likes2Comments