> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.friendlycaptcha.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How Can I Test If My Integration Is Working?

We have compiled some tests for you to check if your Friendly Captcha integration is fully functional and secure.

# Check What Happens if the Solution of the Puzzle Is Wrong

1. Go to the web page where the widget is embedded.
2. Request a puzzle for the form to be tested. (With the default settings you just have to start filling out the form.)
3. Then go to the Friendly Captcha widget in the source code of your page. Therefore, make a right click on the Friendly Captcha widget and select "Inspect Element".
![View Page Source or Inspect Element (This may vary if you are using other browsers)](https://storage.crisp.chat/users/helpdesk/website/7dd4d7e38b874000/screenshot-view-page-source_15ipcc4.png)
4. Look for the input tag containing `name="frc-captcha-solution"` for v1 of Friendly Captcha. In v2 of Friendly Captcha the input tag has the attribute `name="frc-captcha-response`.

![Captcha Solution (The exact value is always unique)](https://storage.crisp.chat/users/helpdesk/website/7dd4d7e38b874000/screenshot-puzzle-solution-ful_1uh8tud.png)

5. Manually **change or delete some characters** of the `value` of the input tag.
6. Submit the form to be tested.

###### Two things can happen:
1. The form **can not** be sent and you get the feedback that something went wrong with the captcha. This should be the case if implemented correctly.
2. The form **can** be sent and the request is delivered to you. This should not happen, an integration bug seems to have been made.

|| If the form was sent despite the manipulation of the tag, you should check how you verify the solution. Please refer to our [documentation for v1](https://developer.friendlycaptcha.com/docs/v1/api/) or accordingly [documentation for v2](https://developer.friendlycaptcha.com/docs/v2/api/).

# Check What Happens if the Solution of the Puzzle Is Empty

1. Go to the web page where the widget is embedded.
2. Request a puzzle for the form to be tested. (With the default settings you just have to start filling out the form.)
3. Then go to the Friendly Captcha widget in the source code of your page. Therefore, make a right click on the Friendly Captcha widget and select "Inspect Element".
![Inspect Element or View Page Source (This may vary if you are using other browsers)](https://storage.crisp.chat/users/helpdesk/website/7dd4d7e38b874000/screenshot-view-page-source_15ipcc4.png)
4. Look for the input tag containing `name="frc-captcha-solution"` for v1 of Friendly Captcha. In v2 of Friendly Captcha the input tag has the attribute `name="frc-captcha-response`.

![Captcha Solution (The exact value is always unique)](https://storage.crisp.chat/users/helpdesk/website/7dd4d7e38b874000/screenshot-puzzle-solution-ful_1uh8tud.png)
5. Manually **delete** the `value` of the tag.
6. Submit the form to be tested.

###### Two things can happen:
1. The form **can not** be sent and you get the feedback that something went wrong with the captcha. This should be the case if implemented correctly.
2. The form **can** be sent and the request is delivered to you. This should not happen, an integration bug seems to have been made.

|| If the form was sent despite the manipulation of the tag, you should check how you verify the solution. Please refer to our [documentation for v1](https://developer.friendlycaptcha.com/docs/v1/api/) or accordingly [documentation for v2](https://developer.friendlycaptcha.com/docs/v2/api/).

# Check if the Form Can Be Sent Without JavaScript

1. Go to the web page where the widget is embedded.
2. Go to the development settings of your browser and disable JavaScript there.
3. Reload the page.
4. Try to submit the form to be tested with JavaScript disabled.

###### Two things can happen:
1. The form **can not** be sent and you get the feedback that something went wrong with the captcha. This should be the case if implemented correctly.
2. The form **can** be sent and the request is delivered to you. This should not happen, an integration bug seems to have been made.

|| If the form was sent despite JavaScript being disabled, you should check the handling of the `<noscript>` tag as well as your backend verification logic. This is described in our [documentation for v1](https://developer.friendlycaptcha.com/docs/v1/guides/browser-support#noscript) and accordingly in the [documentation for v2](https://developer.friendlycaptcha.com/docs/v2/guides/browser-support#noscript).

||| Quick reminder: Make sure to re-enable JavaScript in your browser after the test.