Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
13Activity
0 of .
Results for:
No results containing your search query
P. 1
Generic Test Checklist

Generic Test Checklist

Ratings:

4.5

(2)
|Views: 1,002 |Likes:
Published by api-3698888

More info:

Published by: api-3698888 on Oct 14, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as RTF, PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

application: app x
-1 -
print date:10/14/08
version:
1.00.00
tester:
john doe
generic test checklist
version 97-03-26
document bookmarks:
application:
app x
version:
1.00.00
tester:
john doe
company:
your company
group:
your group
printed:
11/25/97 7:47 am
checklist items are based predominantly upon several texts (esp. cem kaner\u2019s book - bug list appendix) + experience + other

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.)

template filename:c:\testing\docs\testkit\07_generictestchecklist.rtf
create date:
12/08/96 12:19 pm
template by:
matt pierce
filesize:
113,428 bytes
application: app x
-2 -
print date:10/14/08
version:
1.00.00
tester:
john doe
revision history
tester
date
comments
people responsible for app

test lead:
tester:
developer:

developer lead:
program manager:
other people associated with app
support analyst:
brief application description
schedule
#
milestone name
sched\u2019d
date
actual
date
checklist instructions
template filename:c:\testing\docs\testkit\07_generictestchecklist.rtf
create date:
12/08/96 12:19 pm
template by:
matt pierce
filesize:
113,428 bytes
application: app x
-3 -
print date:10/14/08
version:
1.00.00
tester:
john doe
document file notes:
\u2022
rtf file:the document is saved as an rtf file to avoid the compatibility confusion (is the doc saved as win word 6.0, 95, or
97\u2026and what version of word do you have?).
\u2022
read only:the document has the read only attribute set. this is the ancient method of converting a document into a template.
when user goes to save the read only file, the save as dialog is popped up every time. (did this because saved file as an .rtf.)
\u2022
question format:all checklist line items are written so that answers of yes are \u2018a bad thing\u2019, and answers of no are \u2018a good
thing.\u2019
preparation
front end tools
tracking tools:
\ue000bug tracking:testing must have a bug tracking tool. use raid, access app, etc.
\ue000test case manager:used to track status of test cases, avoid duplication of efforts (re-use test cases with slight modification),
etc. use access .mdb, word .doc, etc.
\ue000configuration management:use visual source safe (or sim. prod.) to save test cases, test plans, etc. also use it to look for
code changes, churn rate, version control, etc.
diagnostic tools:

\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

snapshots both before and after broken state occurs\u2026then compare. (or use fc.exe f/nt too).
\ue000wps:debug tool that lists all modules loaded into memory at a given point. (applet comes with windows nt.) save list and
windiff multiple lists over time, or across o.s.\u2019s.
\ue000perfmon:nt performance monitor. check out processor, ram, disk access, network, server performance. (in nt4.0, type
\u2018diskperf\u2019 at command prompt to activate disk stats after reboot.

\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.

automation tools:

\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

code = good tool.

\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.

template filename:c:\testing\docs\testkit\07_generictestchecklist.rtf
create date:
12/08/96 12:19 pm
template by:
matt pierce
filesize:
113,428 bytes

Activity (13)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Sushil Bora liked this
muhammad_omair liked this
Gevita Gv liked this
Jagg_Royal liked this
prakashkommu6904 liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->