You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Tong Sun <su...@gmail.com> on 2024/04/11 15:24:02 UTC
Strange Assertion failure message:Response was null
Hi,
I've got a very strange Assertion failure message, which I cannot replicate
on any of public available urls, which basically says
*Response was null*
[image: image.png]
while actually the response has content:
[image: image.png]
what's more strange is that it only happens to one specific API returns,
I.e., the above "post" request, which goes through the *very same assertion*,
passes flawlessly:
[image: image.png]
Here is the common assertion:
[image: image.png]
I'm wondering what the fix from the JMeter side can be, as I worry that if
I report the problem to our devs, they'd say it's the JMeter's problem, as
everyone has been using it fine for years.
Thanks
Re: Strange Assertion failure message:Response was null
Posted by Tong Sun <su...@gmail.com>.
On Thu, Apr 11, 2024 at 1:30 PM Tong Sun <su...@gmail.com> wrote:
>
>
> On Thu, Apr 11, 2024 at 12:54 PM Tong Sun <su...@gmail.com> wrote:
>
>> The response in Response Body is just plain jason, as the header
>> indicated, whose format is almost the same as the previous "post" one.
>>
>> On Thu, Apr 11, 2024 at 12:53 PM Aditya Singh <at...@gmail.com>
>> wrote:
>>
>>> Hi
>>> What’s the response in Response Body?
>>>
>>> Regards
>>> Aditya
>>>
>>> On Thu, 11 Apr 2024 at 8:57 PM, Tong Sun <su...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I've got a very strange Assertion failure message, which I cannot
>>>> replicate on any of public available urls, which basically says
>>>>
>>>> *Response was null*
>>>>
>>>> [image: image.png]
>>>> while actually the response has content:
>>>>
>>>> [image: image.png]
>>>>
>>>> what's more strange is that it only happens to one specific API
>>>> returns, I.e., the above "post" request, which goes through the *very
>>>> same assertion*, passes flawlessly:
>>>>
>>>
My bad -- the common assertion check was at the Test Plan level. The above
failure was failing at the transaction actually, not my request.
>
>>>> [image: image.png]
>>>>
>>>> Here is the common assertion:
>>>>
>>>> [image: image.png]
>>>>
>>>>
>
> What's more interesting is, there is another assertion before it, and it
> just passes without an issue:
>
> [image: image.png]
>
> Comparing this and above, the *only* change is using the "Not", and the
> "Response was null" *will not be there*.
> So I'm more inclined to think it is something related to Jmeter.
>
> [image: image.png]
>
> I'm wondering what the fix from the JMeter side can be, as I worry that if
>>>> I report the problem to our devs, they'd say it's the JMeter's problem, as
>>>> everyone has been using it fine for years.
>>>>
>>>> Thanks
>>>>
>>>>
Re: Strange Assertion failure message:Response was null
Posted by Tong Sun <su...@gmail.com>.
On Thu, Apr 11, 2024 at 12:54 PM Tong Sun <su...@gmail.com> wrote:
> The response in Response Body is just plain jason, as the header
> indicated, whose format is almost the same as the previous "post" one.
>
> On Thu, Apr 11, 2024 at 12:53 PM Aditya Singh <at...@gmail.com>
> wrote:
>
>> Hi
>> What’s the response in Response Body?
>>
>> Regards
>> Aditya
>>
>> On Thu, 11 Apr 2024 at 8:57 PM, Tong Sun <su...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I've got a very strange Assertion failure message, which I cannot
>>> replicate on any of public available urls, which basically says
>>>
>>> *Response was null*
>>>
>>> [image: image.png]
>>> while actually the response has content:
>>>
>>> [image: image.png]
>>>
>>> what's more strange is that it only happens to one specific API returns,
>>> I.e., the above "post" request, which goes through the *very same
>>> assertion*, passes flawlessly:
>>>
>>> [image: image.png]
>>>
>>> Here is the common assertion:
>>>
>>> [image: image.png]
>>>
>>>
What's more interesting is, there is another assertion before it, and it
just passes without an issue:
[image: image.png]
Comparing this and above, the *only* change is using the "Not", and the
"Response was null" *will not be there*.
So I'm more inclined to think it is something related to Jmeter.
[image: image.png]
I'm wondering what the fix from the JMeter side can be, as I worry that if
>>> I report the problem to our devs, they'd say it's the JMeter's problem, as
>>> everyone has been using it fine for years.
>>>
>>> Thanks
>>>
>>>
Re: Strange Assertion failure message:Response was null
Posted by Tong Sun <su...@gmail.com>.
The response in Response Body is just plain jason, as the header indicated,
whose format is almost the same as the previous "post" one.
On Thu, Apr 11, 2024 at 12:53 PM Aditya Singh <at...@gmail.com>
wrote:
> Hi
> What’s the response in Response Body?
>
> Regards
> Aditya
>
> On Thu, 11 Apr 2024 at 8:57 PM, Tong Sun <su...@gmail.com> wrote:
>
>> Hi,
>>
>> I've got a very strange Assertion failure message, which I cannot
>> replicate on any of public available urls, which basically says
>>
>> *Response was null*
>>
>> [image: image.png]
>> while actually the response has content:
>>
>> [image: image.png]
>>
>> what's more strange is that it only happens to one specific API returns,
>> I.e., the above "post" request, which goes through the *very same
>> assertion*, passes flawlessly:
>>
>> [image: image.png]
>>
>> Here is the common assertion:
>>
>> [image: image.png]
>>
>> I'm wondering what the fix from the JMeter side can be, as I worry that
>> if I report the problem to our devs, they'd say it's the JMeter's problem,
>> as everyone has been using it fine for years.
>>
>> Thanks
>>
>>
Re: Strange Assertion failure message:Response was null
Posted by Aditya Singh <at...@gmail.com>.
Hi
What’s the response in Response Body?
Regards
Aditya
On Thu, 11 Apr 2024 at 8:57 PM, Tong Sun <su...@gmail.com> wrote:
> Hi,
>
> I've got a very strange Assertion failure message, which I cannot
> replicate on any of public available urls, which basically says
>
> *Response was null*
>
> [image: image.png]
> while actually the response has content:
>
> [image: image.png]
>
> what's more strange is that it only happens to one specific API returns,
> I.e., the above "post" request, which goes through the *very same
> assertion*, passes flawlessly:
>
> [image: image.png]
>
> Here is the common assertion:
>
> [image: image.png]
>
> I'm wondering what the fix from the JMeter side can be, as I worry that if
> I report the problem to our devs, they'd say it's the JMeter's problem, as
> everyone has been using it fine for years.
>
> Thanks
>
>