Menu

A recaptcha test that proves something, and the ones that only go green
πŸ“°

A recaptcha test that proves something, and the ones that only go green

DEV Community: backendΒ·Tom HargreavesΒ·about 10 hours ago
#7Z9x0W71
#devtobackend#devto#dev#token#test
Reading 0:00
15s threshold

Most reCAPTCHA problems I get asked about turn out not to be captcha problems. They are tests that pass for the wrong reason: a green pipeline, a production form that keeps rejecting real people, and nobody able to say which of the two changed. Separating the two is mostly a matter of deciding what you actually mean by a recaptcha test.

Three different things people call "testing the captcha"

When someone says their suite covers the captcha, it is usually one of these:

The widget renders. The g-recaptcha element exists, the iframe loads, grecaptcha.render did not throw. Runs in milliseconds, works offline, says nothing about your backend.

Verification works. Your server posts whatever token it received to Google's siteverify endpoint and branches on success .

The whole flow works for a person. A real challenge was shown, a real token was minted, the form submitted, and a row landed in the database.

Levels 1 and 2 belong on every commit. Level 3 belongs in a release check, run once and on purpose.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.