ContributionsMost RecentMost LikesSolutionsAssert incoming csv file against outcoming multiple jsons Situation: Customer uploads a csv file with multiple rows (REST API). Rows are imported into a database, and converted to multiple json messages, which are send to an event grid (that has to be a mock service for now). I can't think of a way how to create tests for this. How to check f.e. that there are as many json messages arrived in the message broker as there were rows in the csv-file/database? And how to check if the content of the json messages matches with content of the ccs file/database? Any help appreciated, I'm not an experienced user. Re: Executing Load Test as part of a Test Suite So.. Isn't it possible to run them together with the functional tests, by hand? Is that a bug, as they are in the Test Suite? Re: Executing Load Test as part of a Test Suite I want to run a Test Suite wich contains both functional AND load tests. Functional tests do run, load tests don't. I don't understand your answer, what do I have to do or install to fix this? I use SoapUI 5.5.0. Re: Executing Load Test as part of a Test Suite I'm (functional tester....) having the exact same problem, can you explain what you exactly did to solve this? Remove Teardown Script with Groovy Hi, what is the syntax in Groovy to remove a Teardown Script from a Test Case? Re: Response can't be shown as JSON, although it should be I'm sorry, developer was wrong... It's solved. Re: Response can't be shown as JSON, although it should be What is your question? I don't know how this works, if I copy/paste the RAW response in Notepad++ and use JSON viewer, it shows it as JSON. So why isn't SoapUI? Response can't be shown as JSON, although it should be I'm pretty new to REST-testing, and I'm not very "technically". SoapUI 5.5.0: REST-response gives "The content you are trying to view cannot be viewed as JSON". RAW gives the header and a long string, copying this string and viewing it in JSON Viewer in Notepad++ shows that it is JSON-format though. SoapUI decides that it is content-Type: application/octet-stream. Developer says that there must be something wrong with the JSON Viewer in SoapUI? What could be wrong? Solved