Skip to content

BUG - Mockserver and ETAG handling #997

@ARiesterer

Description

@ARiesterer

Related Feature

Mockserver supporting ETAG

Description

I think there´s an issue related to the ETag handling in the mock-server:
When doing two changes (on same or different fields) the Etag error pops up. A third change (after refresh within the Etag error popup dialog) is then accepted. Then the fourth change will again lead to the error and so on.
Reason (my assumption):
The ETag timestamp from the response of the previous change should be the If-Match timestamp of the payload of the following change. This is not the case on the second change leading to the error. After the refresh and another change, the If-Match is then set correctly and the change succeeds.

Steps to Reproduce

This can be reproduced in one of our Playwright test apps:

  • Start app Etag-support
  • load data into the ListReport by pressing the Go button
  • select any of the Products to navigate to the ObjectPage
  • press the Edit button
  • change field Requester in the General information section and leave the field pressing the TAB key
  • change field Product Description in the General information section and leave the field pressing the TAB key
  • now you see the ETAG Error which should not be shown

Expected results

No ETAG errors should be shown by just changing two fields in one session

Actual results

see above

Screenshots

See the two changed fields and the error:

Image

Version/Components/Environment

Add any other context about the problem here
OS:

  • Mac OS

Root Cause Analysis

Problem

{describe the problem}

Fix

{describe the fix}

Why was it missed

{Some explanation why this issue might have been missed during normal development/testing cycle}

How can we avoid this

{if we don’t want to see this type of issues anymore what we should do to prevent}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions