I think you’re talking about iso.qa.ubuntu.com (QA or Quality Assurance tracker).
In that case I’d PASS the test, as it worked.
The bug can still be linked in the bug section (not CRITICAL as that would mean you were unable to complete the test; it was a show-stopper level bug). My 2c anyway.
– IN PROGRESS
I use this status when I start the test, it contains a copy of the hardware (copied from a text file with my ~27 boxes), eg. if I was using this box I’d use the line
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
(just copy & paste that detail; most is from
lshw namely make/model (cpu, ram, video))
If it’s a install QA-test, I’d next add a line representing the test from our checklist, eg. if box was in BIOS mode, I was doing a full disk install, no encryption, no internet I’d use something like
testcase: full disk, no encryption, BIOS, no internet
In the checklist I can see I performed that test last for groovy using the 2020-10-22 ISO on a dell optiplex 755 (one I label 8). We’ve not started recording that information yet for 20.04.2 or 21.04.
For live I may write what I plan to do, then when I’ve done it, either amend or add some details. Not everything needs to go there … or many people just leave it blank. It’s up to you.
– PASSED or FAILED
When test is completed; it’s PASS usually. If you were unable to complete test (show-stopper bug, install failed, or system crashed/locked-up, then it’s a FAIL).
Bugs go in “bug section” unless critical.