Project trial worksheet

How to use the result

Define a task and expected result before running the project. Record the exact version/configuration, actual observation and an evidence location you are authorized to share. Use passed, failed and unverified separately. A successful process exit is not enough to mark a task passed. The summary counts every item, including unverified ones; it never turns a partial trial into a certification. Generate a Markdown record, inspect it and download before leaving.

A worked example

For a document converter, enter 'Read an invoice table', expect the marked invoice total in its correct row, then record the actual exported cells. If a scanned file exits successfully but exports no text, mark that check failed with the observed output location. Add a second check for a file you have not tried and leave it unverified. The summary must still include that unverified item in the total. Do not put confidential invoice text into a shared report.

What this cannot establish

This is your record, not a Git-Stars test claim. The tool does not open evidence links or verify that an observation is true. It cannot establish security, performance on other inputs or legal permission. Data stays in page memory without autosave. Only HTTP/HTTPS evidence URLs become links in the exported table; other text is escaped. Changing language or refreshing may lose the form. Save the report and review its contents before sharing it.

Sources and further reading

• MarkItDown official usage: validate the resulting output ↗
• A converter can exit successfully and still miss the task →