Project wiki in Treseko: documentation alongside QA work
Record project decisions, criteria and procedures in Markdown pages scoped to the project and its permissions.
This page is part of Treseko public resources for quality management, automation, evidence and release decisions.
Documentation where the work happens
QA agreements often end up scattered across chats, documents and the memory of whoever attended the meeting. The project wiki gives the team a place tied to its project to record criteria, procedures and decisions in Markdown pages.
Team members can create and edit pages from the project’s Wiki / Documentation area. Someone returning to a test can find the context without reconstructing the whole story.
A healthy boundary for documentation
Use the wiki for working agreements and decisions. Do not store passwords, tokens or other secrets there. Access and available actions depend on permissions configured for the installation.
The wiki is collaborative documentation; it does not replace execution history or evidence attached to a test case. Keeping each record in its place prevents a note from being mistaken for an executed test.
Explore each capability
View documentation · Explore QA solutions · Browse QA resources