You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
We add a debug flag, which provides a hint in the challenge response. However, this requires us to put compromisable code in production path.
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: