[Bug 66156] New: Script replay logs in View results showing as passed but data is not updating in the backend

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66156

            Bug ID: 66156
           Summary: Script replay logs in View results showing as passed
                    but data is not updating in the backend
           Product: JMeter
           Version: 5.4.2
          Hardware: PC
            Status: NEW
          Severity: critical
          Priority: P2
         Component: HTTP
          Assignee: issues@jmeter.apache.org
          Reporter: mailmeatswapna@gmail.com
  Target Milestone: JMETER_5.5

The request under the transaction controller is showing as passed in View
results tree. But the data is not getting updated in the application. 
All dynamic parameters are passed as expected and also compared the requests
with developer tools from chrome browser. 

All are same. 

Not sure about the issue. could you please help as it highly critical.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66156] Script replay logs in View results showing as passed but data is not updating in the backend

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66156

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 OS|                            |All
           Severity|critical                    |normal

--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
This is probably better asked on the users mailing list first. For information
on how to subscribe, see https://jmeter.apache.org/mail2.html#JMeterUser

If you want to get help, you will have to describe the problem in a way, that
someone not sitting at your computer, can understand it. (I can't.)

A minimal test plan to show the behaviour helps a lot. If you can't provide
one, try to give as much other information, as you can (log-files, info about
the runtime, screenshots (favor text-copy for log files instead of pictures).

And last but not least, this issue might be highly critical to you, but not for
everyone, so in most cases leave the priority to normal (or lower). And
remember this is an open source project run by volunteers, so help might not
instant (or gotten at all).

-- 
You are receiving this mail because:
You are the assignee for the bug.