i have found that when i miss bugs, it is convenient and effective to build a new check into the checklist to prevent a recurrence of the missed bug while testing future builds or apps. (every test failure recognized is a lesson learned for which the solution is built into the master checklist\u2014a mistake is not necessarily a bad thing when you can build upon it.)
\ue000virus scan:use f-prot or similar virus scanner to check master disk sets. scan test machines periodically.
\ue000nt taskmanager:tracks resource usage, threads, performance, etc.
\ue000windiff/examdiff:compare file differences. registry dumps, dir c:\*.* /s, or ini file snapshot changes over time\u2014take
\ue000sysinfo:msoffice app that lists all info about currently loaded modules in memory. (comes with msoffice.)
\ue000shotgun:compares differences in registry between different snapshots over time. does much more.
\ue000wmem:checks system resources (user & gdi) and memory used by loaded apps
\ue000dr.watson:debug tool that lists machine configuration, task list, module list, stack dump.
\ue000performance profiling:used to determine where bottlenecks occur in code, etc. built-into vb4.0 enterprise.
\ue000complexity analysis:cyclomatic complexity metric, mccabe\u2019s metric, etc. to determine complexity of source code.
\ue000coverage analysis:ensure that testing hit all lines code, all functions, etc.
\ue000dialog check:runs standard battery of tests against dialog boxes.
\ue000smart monkey:ivan, koko, etc. excellent tools for quickly automating.
\ue000simulators:while testing modules, can use drivers or other simulators to provide inputs to functions / apps being tested. vb
\ue000visual test: automation where appropriate (repeatable).
\ue000macro recorder:used to reproduce intermittent bugs easily without effort of visual test.
\ue000test data generator:used to populate tables with test data.
Now bringing you back...
Does that email address look wrong? Try again with a different email.