client questioning your test results?
[link] my test documentation should always include: a. test map: trace-referenced, logged, and updated to include all the scenario branches that were actually tested at the time of testing; b. test evidences: vid captures, screen captures, actual app outputs (images, jsons, txt files, etc), app exe file, that prove how the app behaved at the time of testing -- any and all relevant artefacts that captured the app's behaviour; c. bug/issue reports: replete with STRs (steps to replicate), evidences, paired against expected results; d. the app build or version number tested; e. the platform tested; d. Pass/fix statement on the test report: indicating (a), (b), (c), (d), (e); this is why, broadly speaking, all testing should have these elements to provide a thorough proof that testing was executed to properly evaluate the software under test. Any misses will be self evident with this method of documentation.