I love having the ability to test Forms processes using the beaker in Version 12. It would be fantastic if in addition to alternate task recipients, alternate mail recipients, and alternate repository paths that it would not force CAPTCHA if CAPTCHA is turned on. 

I can't tell you how many times I have started to test a lengthy form, gotten to the end, noticed CAPTCHA (which always produces the error below if ran from Forms), navigated to the process diagram, turned it off, returned again to test, and hopefully remembered to turn CAPTCHA back on.  CAPTCHA is important to us because we use a lot of public forms, some of which do not require any sort of authentication. 

Maybe it is possible that a setting could be changed somewhere to allow processes with CAPTCHA to not produce this error when they are ran in Forms instead of at the assigned public URL?