Lessons Learned in Software Testing
Index[A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] [Z] backward compatibility bandwidth batch files Windows Task Scheduler behavioral testing [See dynamic black-box testing] black-box testing beta releases beta testing plans for 2nd beta tests defined planning for 2nd big-bang model black-box testing equations and formulas product specifications techniques 2nd 3rd 4th websites 2nd blank conditions blocks bottom-up testing boundary conditions 2nd 3rd powers-of-two types of boundary edges testing 2nd branch coverage testing buddy reviews [See peer reviews] buffer overflows [See buffer overruns] buffer overruns 2nd C/C++ functions secure/unsecure functions bug bug fixes fix/no-fix decision making process bug bashes bug committee bug reports bugs bug committee bug fixes Change Control Boards deferring postponing priorities, setting 2nd bug graphs bug tracking database 2nd queries 2nd 3rd classifications priority severity comparison errors computation errors configuration bugs isolating control flow errors costs of conformance external failures internal failures nonconformance data declaration errors data reference errors defined finding inspections static white-box testing using automated tools finding in configurations input/output errors isolating isolating bugs 2nd 3rd process 2nd life cycles 2nd Microsoft bugs regressions reporting 2nd 3rd automated reporting/tracking 2nd 3rd manual reporting/tracking Test Incident Report tracking systems reproducible bugs reproducing bugs 2nd sources state bugs states deferred state open state resolved state review state sub-boundaries subroutine errors testing for 2nd outside testers website resources websites discovering bugs (software) 2nd 3rd 4th 5th 6th [See also software bugs] causes of 2nd 3rd costs of 2nd defined defining diagnosing finding bug bashes fixing/not fixing latent bugs pesticide paradox testing for builds |