---
metadata:
  - name: generator
    content: Diplodoc Platform v5.48.2
alternate:
  - https://admin.contest.yandex.ru/docs/en/guide/contest/reports.md
---
> **Documentation Index:** Fetch the complete configuration index at https://admin.contest.yandex.ru/docs/en/llms.txt

# Testing and report for participants

Select a contest and in the menu on the left, open **Settings** → **Testing and report for participants**.

## Testing settings {#set-testing}

#### Use AC instead of OK

After passing sample tests and the checker, the solution receives an AC (accepted for check) verdict instead of OK.

#### Abort testing when first error occurs

If an error occurs during a test, testing stops.

#### Stop testing at first error in test set

If an error occurs within one test set, testing of that test set stops and continues in the next test set.

#### For failed tests

This action is performed if the solution fails one or more sample tests specified in the problem settings.

## Test report settings {#set-reports}

#### Simplified submission report

Determines whether to display the table with previously submitted solutions and the results of their check on the problem page.

#### Show submission result when participation ends
   
The participant will see the scores and verdicts for submissions after completing the contest. Does not affect the results displayed on the leaderboard.

#### Time and memory used by program

Which tests resource consumption will be shown for when testing the solution.

#### Verdict

Display the verdict for individual tests and the problem in general:
- **On all submissions**: Individual verdicts for all tests are used to deliver the final verdict.
- **Only on sample testing results**: The verdict is AC if all sample tests are passed and failed tests are not included in the samples, or OK if all tests are passed.
    
Use the drop-down list to configure how verdicts are displayed on the test report page for users.

#### Score

The report shows the score for individual tests and samples.

#### Input
   
The report shows the input data for testing the solution.

#### Output
   
The report shows the data received after testing the solution.

#### Correct answer

The report shows the expected result after testing the solution.

#### stderr

The report shows errors that occur while testing solutions.

#### Checker output

The report shows data received after running the problem checker.

#### Postprocessor output

The report shows data returned by the problem postprocessor.

<!-- source: en/_includes/reusables/support-button.md -->
<a href="../../troubleshooting">
  <span class="button">Write to Support</span>
</a>



<!-- endsource: en/_includes/reusables/support-button.md -->