Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Beliagal/qa-report-automation/llms.txt

Use this file to discover all available pages before exploring further.

The Valoraclick QA Tool ships with a config.json file in the project root that stores configurable defaults for tester names and the current application version. The file is part of the project structure and is ready for a future integration that will populate the Tester field automatically — in the current release, gui.py does not read it at startup, so edits will not affect the running application until that wiring is complete.

​
Default Configuration

The file ships with two default tester identities and version 1.0.0:
config.json
{
    "testers": [
        "Tester General",
        "QA Lead"
    ],
    "version_actual": "1.0.0"
}

​
Field Reference

​
testers
array of strings
required
The list of tester display names available in the tool. Each entry is a string representing a team member’s name or role. Add, remove, or rename entries to match your QA team roster.
​
version_actual
string
required
The current application version string. This value is intended to be shown in generated reports and should be kept in sync with your release tag (e.g. "2.7.0").

​
How to Customize

Open config.json in any text editor — Notepad, VS Code, or any editor of your choice — and modify the values directly:
  • Add a tester: append a new string to the testers array.
  • Remove a tester: delete the corresponding line (and its trailing comma if needed).
  • Update the version: change the version_actual string to match the version you are releasing.
Save the file after editing. The changes will take effect once gui.py is updated to read config.json at startup (see the note below).

​
Example: Custom Team Configuration

The following example shows a configuration updated for a four-person QA team and a 2.7.0 release:
config.json
{
    "testers": [
        "Ana García",
        "Carlos López",
        "Maria Rodríguez",
        "QA Lead"
    ],
    "version_actual": "2.7.0"
}
config.json is intended for future integration where the Tester dropdown in the UI will be populated automatically from the testers array. In the current release, gui.py does not yet read this file at startup — testers can type their name freely in the Tester field in the metadata section. The file is in place so the integration can be wired up without a structural change to the project.
config.json must contain valid JSON at all times. A missing comma, an unmatched bracket, or a stray trailing comma will cause a parse error when the file is read in a future release. Use a JSON validator (such as the built-in validator in VS Code) to check the file before saving.

Build docs developers (and LLMs) love

Get started for freeTalk to us