| < Day Day Up > |
|
Beck, Kent, 17, 72, 85
beta testing, 29, 71
billing and time tools, 13–14, 14
BitKeeper software, 38, 39
black-box testing, 164
Boggs, Michael, 23
Boggs, Wendy, 23
Branch command, 36-37, 36–37
branching, 47–48
breadth-first coding, 27
Brooks, Fred, 11
BSD (Berkeley Source Distribution) licenses, 262
bug tracking, 156–173, See also debug
checklist, 173
excess process in, 170
overview, 156
politics of, 162-163
with quality assurance testing, See also testing;
unit testing
black-box testing, 164
compatibility testing, 164
conformance testing, 163–164
functional testing, 163
on networked computers, 166–168
overview, 163
performance testing, 164
regression testing, 164
smoke testing, 164
stress testing, 164
unit testing, 163
when working solo, 165–166
white-box testing, 164
and resolving
by design, 161
duplicate bugs, 161
by fixing, 162
as not reproducible, 161–162
by postponing, 161
by reassigning, 162
as won’t fix, 162
risk management and
bug triage, 160–163
overview, 156
risk assessment, 156–158
risk control, 158–159
steps in, 158–160
top five risks lists, 159–160
tools
choosing, 169–171
FogBUGZ, 171–173, 172
overview, 169
workflow in, 162
building code. See code; coding;
source code
“Building Secure Assemblies” article, 188
Buzan, Tony, 4
| < Day Day Up > |
|