You could install Fiddler and modify request headers with the CustomRules.js file
To modify the header with Fiddler:
1- Open Fiddler Web Debugger and in the menu toolbar go to Rules->Customize Rules... (shortcut is Ctrl + R). It opens the CustomRules.js file. Fiddler may suggest you to download Fiddler ScriptEditor but you can edit it with any text editor (I use notepad++)
2- Find OnBeforeRequest(oSession: Session) in the script file.
3- You can add a new header by adding oSession.oRequest["NewHeaderName"] = "New header value"; to OnBeforeRequest function. Also, to remove a header, use oSession.oResponse.headers.Remove("HeaderName"); function.
I had a similar situation in one of the projects. A separate test database is created before starting the tests and the structure of the prod database is copied into it and filled with fake data. Then it is removed.
Tests use a mock object to work with a database, where a test database is substituted instead of a prod.
Sometimes you need to run non-destructive tests on existing records in a prod or stage database; or if it is not convenient to update the test data - you can switch the used database.
I usually make the expected and actual tuples, and I compare them.
expected = ('john doe', '1111', 'something', True)
actual = (
response ["user"],
response ["objects"] [0] ["id"],
response ["objects"] [0] ["event"] [0] ["type"],
response ["reached"]
)
assert expected == actual
Run pytest with the -v switch, then it will clearly show which elements in the tuples are not equal.
Never try to unify something without having a unified thing. Refactoring or optimization is done only if there is working code to compare the results. In your case, write a few examples by hand and then try to find a common denominator. The transition should always be from simple to complex.
