Manual Integration Test: Stateful Session OData V4 App
DESCRIPTION
Test Stateful Session OData V4 App.
PREPARATION
To check console errors open the developer tools before starting the application and check
with each step, that there are no errors and warnings.
Testing with mock data
Start the Sticky application with following URL (adjust host and port if necessary):
Testing with back end
Configure your IDE to be able to run the Sticky application against an ABAP
back-end system.
Start the Sticky application with the URL (adjust host and port if necessary):
REALIZE and CHECK
Note:
To check correct session handling you may check whether the header
SAP-ContextId
is fetched correctly from the server response once a stateful
session is opened and sent with all following requests until the session is closed.
The session is opened with Edit
and closed via Save
or
Discard
buttons.
Check: If realOData=true
, open the network tab in the browser's
developer tools and check that each request following the "prepare" request contains the
header SAP-ContextId
. (Note that headers are case-insenstive.)
For realOData=false
you may only check that no errors are displayed,
- neither in the message popover nor in the browser console (after app is started)
Check stateful session handling
- After the application is started, within the table select the Sticky Type with Id
10
, for realOData=true
the Id doesn't matter
Save scenario:
- Press
Edit
button in order to open a new back-end session.
- Within the
Sticky Type Details
enter a value for content
.
- Press
TAB
in order to invoke a change for the value entered.
- Press
Save
in order to close the back-end session.
Discard scenario:
- Press
Edit
button in order to open a back-end session.
- Within the
Sticky Type Details
enter a value for content
.
- Press
TAB
in order to invoke a change for the value entered.
- Press
Discard
in order to close the back-end session.