This is from feedback from Ghotit, found in ZD here: https://hypothesis.zendesk.com/agent/tickets/5816

https://h.readthedocs.io/en/latest/api/using-oauth/#implementing-oauth-flow
In paragraph 2:

After the user authorizes the application, it will receive an authorization code via a call to the redirect URI. The application must exchan

Steps to reproduce

1. On iOS, activate VoiceOver. (nb. Before activating VO, I recommend changing the "Typing" mode in VO settings to "Direct touch typing", as using the on-screen keyboard to enter a URL in Safari is painfully slow otherwise)
2. Open Safari and navigate to https://hypothes.is/docs/help
3. Select and activate the sidebar toggle button to close it
4. Select and try to activate

It will be extremely helpful to have some code examples , so it will be easier to start using Schemathesis.

• Straightforward test. the whole api, without filtration or app insights
• Filters for specific endpoints
• Tests with insights about the app data (id of some existing DB object for GET / PUT calls)
• Using subtesthack to unlock pytest fixtures per hypothesis test

It's not clear that the browser extension needs it own oauth client registered in h. Both the docs and the readme files should make mention of this so its clear how to set up a custom client in a browser extension running on a local instance of h.

For example
http://localhost:5000/admin/oauthclients

![Screen Shot 2019-09-09 at 9 06 59 AM](https://user-images.githubusercontent.com/3939074/

https://github.com/Zac-HD/hypothesis-jsonschema/blob/3047ec70fc05123d7253be09bfb74490e59e06e6/tests/test_canonicalise.py#L192-L196

This test will pass when merged can tell that "required": ["name"] in the first schema conflicts with "additionalProperties": False in the second, and returns the empty schema {"not": {}}.

Note that if other types of value are allowed, it should instead

Might make the API docs a bit more concrete