Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use OCR in locust tests #71

Closed
hrj opened this issue Apr 2, 2021 · 0 comments · Fixed by #83
Closed

Use OCR in locust tests #71

hrj opened this issue Apr 2, 2021 · 0 comments · Fixed by #83
Assignees
Milestone

Comments

@hrj
Copy link
Contributor

hrj commented Apr 2, 2021

We are currently always testing with wrong answers. For proper testing, we need to submit answers that are known to be right or wrong.

For the tests to know what the right answer is, there are two possibilities:

  1. We add a debug flag, which provides a hint in the challenge response. However, this requires us to put compromisable code in production path.
  2. We add a DebugCaptchaProvider, which provides very simple challenges that are easily solved with OCR. This can be disabled by default, and a config.json can be provided by test scripts that enable this provider.

I prefer $2 because it means production code needn't have any hacks in it.

@hrj hrj added this to the version 1.1 milestone Apr 3, 2021
@hrj hrj self-assigned this Apr 12, 2021
@hrj hrj closed this as completed in #83 Apr 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant