New answers tagged api-testing
1
According to JMeter Test Elements execution order listeners are being executed after post processors and your prev.setIgnore() instruction prevents passing the sample result to the listeners.
One of possible options is writing the response data into a file in the JSR223 Post Processor itself, the relevant code would be something like:
new File('/path/to/your/...
0
So, looking at this again, I had the properties for protocol, hostname and port set as: modules.jmeter.properties.environment.protocol and same for hostname. For port, I had modules.jmeter.properties.environment.port..
This naming convention worked fine when I set the properties in a text file as a single line. I.e...
modules.jmeter.properties.environment....
0
if I then run the test using bzt -o modules.jmeter.properties.protocol=TEST then the test runs just fine
that shouldn't happen as you will get MalformedURLException
overall status code of the bzt command execution will still be 0 (success) unless you have custom pass/fail criteria
If I remove the setting of the property from the file (e.g. .bzt-rc) but ...
1
It is possible to "ignore" them on JMeter level, just add JSR223 PostProcessor as the child of the request(s) you want to ignore or if you want to ignore the whole Thread Group - put it at the same level as Samplers (see JMeter Scoping Rules for more details)
Use the following code to discard the sample result:
prev.setIgnore()
where prev is the ...
0
make sure you are importing org.testng.annotations.Test and not org.junit.Test
1
Add the next line to user.properties file:
sample_variables=phone
Restart JMeter to pick up the change
Instead of ${phone} in the Flexible File Writer use variable#0
If you need to write more than one variable:
sample_variables=phone,device_id
and then in the Flexible File Writer:
variable#0 - instead of ${phone}
variable#1 - instead of ${device_id}
...
1
As a QA what should be our response to such a design ?
We should poin developers into right direction.
Should it be ignored or are there are any good practices QA follows to ensure the quality of a REST endpoint?
We should be compliant with HTTP protocol, REST dissertaion from Roy Fielding and making sure that REST API is readable, testable and well ...
Top 50 recent answers are included
