<commit_before>[[validation-runs]]
=== Managing validation runs

<<model,Validation runs>> associate a validation stamp
to a build, and a status describing the validation: passed,
failed, etc.

Additionally, a <<model,run info>> can be associated with
the validation run to show information like a duration,
a source or a trigger.

Validation runs can be created manually, but more often,
they will be created automatically by a CI engine like
<<integration-jenkins,Jenkins>>.

Validation runs can be seen:

* in the branch overview - only their latest status is
  then visible

* in the branch overview, by clicking on a validation run
  (at the intersection of a validation stamp and a build),
  you can either create a new validation run (when there is
  none) or see the list of them and their statuses.

* in the build page

* in the validation stamp page

For one validation run, one can add comments and update
the status to reflect (for example, to mention that
a failure in under investigation).<commit_msg>#176 Validation run data<commit_after>[[validation-runs]]
=== Managing validation runs

<<model,Validation runs>> associate a validation stamp
to a build, and a status describing the validation: passed,
failed, etc.

Additionally, a <<model,run info>> can be associated with
the validation run to show information like a duration,
a source or a trigger.

Validation runs can be created manually, but more often,
they will be created automatically by a CI engine like
<<integration-jenkins,Jenkins>>.

Validation runs can be seen:

* in the branch overview - only their latest status is
  then visible

* in the branch overview, by clicking on a validation run
  (at the intersection of a validation stamp and a build),
  you can either create a new validation run (when there is
  none) or see the list of them and their statuses.

* in the build page

* in the validation stamp page

For one validation run, one can add comments and update
the status to reflect (for example, to mention that
a failure in under investigation).

[[validation-runs-data]]
==== Validation run data

Some additional data can be associated with a validation run, according
to a format defined by their <<validation-stamps-data,validation stamp>>.
For example, passed and total tests, or a coverage percentage.

When creating a validation run, either though the GUI or through any
of the API, the data will be validated according to the rules defined
by the validation stamp.

In particular, the validation run status (passed, warning, failed, etc.)
will be computed in some cases, when a threshold of quality is associated
with the validation stamp (like a % of passed tests).
{'fraction_non_alphanumeric': 0.05615874204417821, 'fraction_numerical': 0.0011231748408835642, 'mean_word_length': 4.555093555093555, 'pattern_counts': {'":': 0, '<': 17, '<?xml version=': 0, '>': 17, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4820789', 'n_tokens_mistral': 660, 'n_tokens_neox': 642, 'n_words': 404}