Re: Mark error in JSR223 steps

2020-12-30 Thread Felix Schumacher
Have you tried the simplest test plan you can imagine? Can you post it here? Felix Am 30. Dezember 2020 21:45:51 MEZ schrieb Tong Sun : >Hmm, > >I've put > >SampleResult.with { >successful = false >responseCode = "500" >responseMessage = "some error" >} > >into my catch section, but they are

Re: Mark error in JSR223 steps

2020-12-30 Thread Tong Sun
Hmm, I've put SampleResult.with { successful = false responseCode = "500" responseMessage = "some error" } into my catch section, but they are still green and correct (even error is caught) viewed in Result Tree. I also tried to use SampleResult.setSuccessful(false) but that didn't work

Re: Mark error in JSR223 steps

2020-12-30 Thread Tong Sun
Thanks a lot Mariusz, I could never come up with answers like that myself! On Wed, Dec 30, 2020 at 11:50 AM Mariusz W wrote: > > To see it in reports and listeners: > SampleResult.with { > successful = false > responseCode = "500" > responseMessage = "some error" > } > > Regards, > Mariusz >

Re: Mark error in JSR223 steps

2020-12-30 Thread Mariusz W
To see it in reports and listeners: SampleResult.with { successful = false responseCode = "500" responseMessage = "some error" } Regards, Mariusz On Wed, 30 Dec 2020 at 16:40, Tong Sun wrote: > Hi, > > My JSR223 steps have problems, some even have exceptions, but viewing > from View Result

Re: Mark error in JSR223 steps

2020-12-30 Thread Mark Miller
When you are using a JSR 223 sampler, you are in full programmatic control of the sample and its result. I find it most helpful to get right into the JavaDocs for, in this case, the SampleResult: https://jmeter.apache.org/api/index.html?org/apache/jmeter/samplers/SampleResult.html >From your

Mark error in JSR223 steps

2020-12-30 Thread Tong Sun
Hi, My JSR223 steps have problems, some even have exceptions, but viewing from View Result Tree, they are all green and correct. How to mark those JSR223 steps that have problems red and failed? I tried to throw an exception, but that killed the whole thread. thx