This is a HTTP mock server for reproducing issues on the front-end using a recorded HTTP archive(*.har file).
The gimmick is that for a given endpoint it stores all the responses and serves them in a round-robin sequence.
This way you can simulate situations where e.g. a request has been retried after the JWT expired, or something special happens when an item is added to a list, and the list is refreshed afterwards - basically every case in which you need backend state.
It works... sometimes. Each new project I'm in uncovers new issues.
That being said with the test team giving me both videos and *.har files of the bug reproduction I was able to solve a few long standing bugs in one legacy system.
This is a HTTP mock server for reproducing issues on the front-end using a recorded HTTP archive(*.har file).
The gimmick is that for a given endpoint it stores all the responses and serves them in a round-robin sequence.
This way you can simulate situations where e.g. a request has been retried after the JWT expired, or something special happens when an item is added to a list, and the list is refreshed afterwards - basically every case in which you need backend state.
It works... sometimes. Each new project I'm in uncovers new issues.
That being said with the test team giving me both videos and *.har files of the bug reproduction I was able to solve a few long standing bugs in one legacy system.