## Testing Workflow

Once you have integrated libuhttpmock into your tests, your workflow will consist out of the following steps:

- Log: After doing changes in your application that cause wanted changes in behavior (e.g. a different response after the API has changed), you want to record a new trace. For this you enable both logging and online modes, as described above.

- Compare: If you want to make sure the server still behaves as you expect (sends you the expected responses), you can disable logging and enable the online mode. libuhttpmock will then query the actual online server, but won't overwrite the trace file and will error out if any response from the server has changed.

- Test: When running tests in CI or when releasing your application for downstreams to package it (and run tests), you want both logging and the online mode to be disabled. In this case libuhttpmock will mock the responses of the actual online server. That way no internet access is required for your tests, API keys required for testing don't have to be shipped and so on.