As pointed out, the whole purpose of captcha is to prevent automated
attacks. The solution for automated testing of captcha is to make a
back door, make it configurable or both.
All solutions require a code change. You can check to see if
development already has something in there. Solutions might be, a flag
in a configuration file disables captcha. This would require a change
to a file in the operating system and possibility a restart of the web
application.
Another solution is to make the captcha so it will always accept two
inputs. The first is the randomly generated string we present to the
user and the other is a secret back door value. So if you input the
secret backdoor key it is always accepted. If you hard code the key
there is a the danger it will get out to the public. For example,
installing Microsoft products requires a key. Twenty years ago
Microsoft hard coded the key 11111-11111-11111-11111. It was always
accepted. A former employee of Microsoft told some friends who told
some friends and in no time everyone knew you could install any
Microsoft product by just holding down the 1 key when asked for the
product registration key.
Same thing can happen with a captcha. If the secret captcha key is
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
sooner or later this will get out and you'll have to release a new
version of the product with a different key. If the developers can
make the secret key a configurable value, you just need to edit the
configuration file to change the key, if someone happens to give the
key out to a friend.
Don't even think about asking development to put the captcha key in an
attribute of the image. The people who attempt to bypass captchas will
notice the attribute and use it to their advantage. The captcha key
should NEVER be available via the web browser or an API call.
Bottom line, see if development has already put a work around in the
code. If they have not, they will have to change the code to enable
automated use of the captcha.