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.

This guide walks end-users — QA analysts who just need to document and export test results — through downloading and running the pre-built Valoraclick QA Tool executable. There is no Python to install, no dependencies to manage, and no configuration required before your first launch. From download to your first exported PDF takes under two minutes.

Generate Your First Report

1

Download the Executable

Go to the Latest Release page on GitHub and download QA_Tool_v2.7.exe. Save it anywhere on your Windows machine — your Desktop or Downloads folder works fine. No installer or setup wizard is involved.
2

Launch the Application

Double-click QA_Tool_v2.7.exe to open the tool. The application will launch in a maximized window titled QA Tool v1.0.0 Secure. Windows Defender SmartScreen may show a prompt on first run — click More info → Run anyway to proceed. No administrator privileges are required.
3

Fill in the Report Metadata

Complete the fields in the top metadata grid before adding any test steps. These values appear in the header of your final PDF report:
FieldWhat to Enter
AplicaciónThe name of the application under test
TesterYour name or tester identifier
FechaTest date in DD/MM/YYYY format (pre-filled with today’s date)
Historia de UsuarioThe user story or ticket reference being tested
RequisitosRequirement IDs or acceptance criteria references
VersiónThe build or version number under test
DependenciasAny external systems or services the test depends on
Resumen EjecutivoA short executive summary describing the scope and outcome of the test session
The Fecha field enforces a DD/MM/YYYY format — only digits and forward-slashes are accepted, and a date format warning is shown at export time if the value does not match.
4

Log Your Test Steps

Use the step entry form below the metadata grid to record each test action:
  1. Acción — Type what action you are performing (e.g., “Click the Login button with valid credentials”).
  2. Esperado — Describe the expected result.
  3. Obtenido — Describe the actual result observed.
  4. 📸 Imagen — Optionally click the image button to attach a PNG or JPEG screenshot. The button changes to ✅ Imagen Ok when a file is selected.
  5. Pass / Fail — Use the dropdown to set the step verdict.
  6. Click AÑADIR PASO to commit the step.
The real-time preview panel at the bottom of the screen updates instantly, showing each step color-coded: green for Pass, red for Fail. Repeat this process for every test case in your session.
5

Export the PDF and Back Up to Google Drive

When all steps are logged, click the EXPORTAR PDF button in the top-right toolbar. A save dialog will appear — choose a filename and location for your PDF. Once you confirm:
  • The PDF report is generated with all metadata, step details, Pass/Fail color coding, and embedded screenshots.
  • A CSV backup of the session data is automatically written to your Google Drive sync folder via your Windows shortcut — no extra action needed.
A confirmation dialog will report whether the Drive backup succeeded or was unavailable (e.g., if Google Drive for Desktop is not running).
Session data is saved automatically to sesion_testing.json in the same folder as the executable every time you add a test step. If the application closes unexpectedly — or you simply close it mid-session — all your metadata, step log, and image paths will be fully restored the next time you launch the tool. Your work is never lost.
To clear all current data and start a fresh test session, click RESET TOTAL in the top-right toolbar. You will be prompted to confirm before anything is deleted. This removes both the in-memory session and the sesion_testing.json file, giving you a clean slate for the next test cycle.

Next Steps

Fill in Report Metadata

Learn how each metadata field maps to sections of the final PDF report and how to structure your entries for consistent, professional output.

Log Test Steps

Discover best practices for writing clear Action, Expected, and Obtained entries, attaching screenshot evidence, and managing multi-step test cases.

Build docs developers (and LLMs) love