Documentation
Test plans, cases, and runs
Structure suites, execute runs, link cases to features, and feed QA metrics into project reports.
Updated 2026-05-228 min read
- QA
- Test plans
Structure: plan → suite → case
A test plan belongs to a project and groups suites (e.g. Smoke, Regression, Integration). Each suite contains ordered test cases with steps and expected results.
Executing a test run
- Open Testing → select a plan → Start run.
- Assign executors; each case records pass, fail, blocked, or skipped.
- Link failures to bugs created from the run screen.
- Close the run to lock results for reporting.
QA in project reports
- Testing report templates show pass rate, open failures, and execution by tester.
- Filter by plan or run to compare release readiness week over week.
Continue reading
Projects, boards, and work items
Tasks, bugs, and features share one model across board, list, Gantt, calendar, and reports—without duplicate entry.
Read guideWhy approval-first workspace AI beats silent autofill
Teams want AI speed without losing control. Proman in Projectman drafts and proposes—then waits for your approve before any save.
Read guideNetwork Pro explained: visibility boosts, SEO fields, and what they actually do
An honest look at Network Pro: Pro badge, discovery boost slots, featured hub/industry placement, product highlights, advanced SEO FAQ, and showcase analytics—without overclaiming search rankings.
Read guide