~/talk

Bug Report — A Developer Task or a Serious Document?

on YouTube 16m
TalkinRussianat QA Fest 2016 · 2016-09-30..10-01· [testing]

speaker

name:Artem Bykovets
website:https://www.abykovets.com

resources

video:https://youtu.be/yYXzYE1YQ-U
slides:none on file

summary

Covers how to write effective bug reports for QA: identifies common mistakes testers make (even experienced ones) when under time pressure and shows n ways reports get ignored. Reviews essential elements like clear summary, reproduction steps, and expected/actual results, and explains what constitutes a good bug report for functional testing.

AI-written summary · about

chapters (12)

  1. 0:00Introduction
  2. 2:27Bug reports ignored
  3. 3:30Labels and logs
  4. 4:53Tester independence
  5. 6:18Duplicate checks
  6. 7:00Defect localization
  7. 8:47Critical defect case
  8. 10:32Defect priority impact
  9. 11:35Bad bug report example
  10. 12:39Writing bug reports
  11. 13:43Quality in small teams
  12. 14:43Tester as defect doctor

related talks

~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.