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
My case involves more performance gains in e2e tests than anything else.
Currently my authentication flows need captcha to work and this is expected for security reasons,
the big question is that using captcha in test environments is very expensive, as it involves downloading the google library,
and generate its configuration (which takes time, mainly in unstable or bad connections as it happens in emerging countries like Brazil - where I am at the moment).
The idea in this case, is to create a kind of "fallback" / "mock" for the GRecaptcha functions so that the fake captcha flows continue to work in test.
What I thought was to add an option:
// controllerisActive=window.ENABLE_RECAPTCHA// (each app will have their owns)
Hello, how is everything?
My case involves more performance gains in e2e tests than anything else.
Currently my authentication flows need captcha to work and this is expected for security reasons,
the big question is that using captcha in test environments is very expensive, as it involves downloading the google library,
and generate its configuration (which takes time, mainly in unstable or bad connections as it happens in emerging countries like Brazil - where I am at the moment).
The idea in this case, is to create a kind of "fallback" / "mock" for the GRecaptcha functions so that the fake captcha flows continue to work in test.
What I thought was to add an option:
With this kind of control, we could only enable recaptcha when is really needed.
PS: I can work on this improvement ;)
The text was updated successfully, but these errors were encountered: