# Block Qualified Test Proof

In order to obtain a test credential, the user must first provide a proof that shows they have necessary knowledge to obtain it.

## Generating a Proof

You can use the `@bq-core/lib` library to generate such proofs, passing the following parameters to the `generateTestProof` function:

* `identity`: the [Semaphore identity](https://semaphore.appliedzkp.org/docs/guides/identities) of the user generating the proof.
* `testAnswers`: composed of:
  * `multipleChoiceAnswers`: list containing the user's answers to the multiple choice component.
  * `openAnswers`: list containing the user's answers to the open answers component.
* `testVariables`: the parameters that define the test, these being the `minimumGrade`, `multipleChoiceWeight`, `nQuestions`, `multipleChoiceRoot`, `openAnswersHashesRoot`, and `openAnswersHashes`; as described in [Block Qualified Tests](/bq2/technical-reference/block-qualified-tests.md).
* `identityGroup`: the group to which the user will be added, this logic being enforced by [the smart contract](/bq2/technical-reference/contracts.md#solving-a-test):
  * If the grade obtained is above the specified `minimumGrade` for this test, this will be the credentials group.
  * Otherwise, `minimumGrade` must be set to `0` so that the proof does not revert, and this will be the no-credentials group.
* `gradeGroup`: the Semaphore-like group containing the [grade commitments](/bq2/technical-reference/circuits.md#grade-tree-inclusion) of all users that attempted to obtain the credential.
* `testPassed`: boolean value indicating whether the test was passed or not, which is later verified at the smart contract level.
* `snarkArtifacts`: the [`zkey`](https://github.com/0xdeenz/bq-core-v2/blob/main/packages/lib/snark-artifacts/test.zkey) and [`wasm`](https://github.com/0xdeenz/bq-core-v2/blob/main/packages/lib/snark-artifacts/test.wasm) trusted setup files.
* `testId`: the ID for this test, used to compute the value for the empty leaf when Merkle proofs are provided instead of groups.

{% hint style="warning" %}
When providing a group to this function, an empty leaf is added in order to generate the corresponding Merkle proofs.

If the proof is later accepted by the smart contract and the corresponding on-chain groups get updated, developers should use the [`updateMember`](https://github.com/semaphore-protocol/semaphore/blob/main/packages/group/src/group.ts#L86) function to update their off-chain groups. Using the [`addMember`](https://github.com/semaphore-protocol/semaphore/blob/main/packages/group/src/group.ts#L67) function instead would create a new leaf *after* the empty leaf that was added before.
{% endhint %}

## Verifying a Proof Off-Chain

You can use the `@bq-core/lib` library to verify a generated proof via the `verifyTestProof` function:

```js
import { verifyTestProof } from "@bq-core/lib"

await verifyTestProof(testProof) // true or false.
```

Which returns a promise that resolves to true or false.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://deenz.gitbook.io/bq2/guides/proofs/bq-test-proof.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.