I
personally find that each application is diverse enough that writing a generic
test script (script meaning automated process) is often as much work as simply
doing it by hand. So, I use a manual testing process. That said
though, there are times and places where this might be
useful.
For my
manual testing, I first write up a document that lists everything that needs to
be tested (i.e. the requirements for the application), and each test point
includes instructions on how to test the specific requirement. An
additional blurb is included to detail what should be happening, and room is
left for comments.
i.e.
Test
Item # 1: Requirement 1.1.2.3 - A user must be logged in before they can
access any page in the web site.
Directions:
1. Open a new broser.
2. Type in the address to specific files other than
the home page and/or the login page into the browser's address
bar.
Expected Results: The request should be redirected to the home
page.
Observations:
Then
once the complete document has been created, it is passed to somebody to test -
ideally someone who has not worked on the project. That person must sign
off each item that is working properly. When the test plan can be
completed and EVERY item passes, then the project is ready to move to
deployment/delivery. This process itself might need to be recreated if the
testing is not being done onsite (i.e. test in the development enviroment,
deploy the changes, test again).
This
process can be lengthy though - simply writing the test plan for an average size
project can take as long as a week. Executing the test plan also takes a
fair amount of time, possibly another week. Any issues found need to be
fixed and the test plan completed again. So, the testing end of a
development project can (and probably should) take a very long
time.
I'm
sure there is a faster way to do this, like maybe automating some of the grunt
work testing (hitting each page with a different security level, or ensuring
each page will not load if a user has not logged on), but I think you'll get the
best results from human testing.
I'm
open to discussion on better/faster ways to do testing, but that is a
conversation better suited for the programming list I think. I'd also be
intersted in someone else's thoughts on automating the testing
process.
Shawn
Hi Gang,
I know there are masters on programming within this group. Somehow, I want
to know something about testing or QA and system
integration in the software development life cycle.
I have understood part of test methodology, like the knowledge of the
test case, test plan, black box, coverage test. But never touched the
test script writing. Would you please give me an instruction on it.
Maybe my topic is so huge, I would like narrow down the details
following first, like:
1.what script tools u guys have used( whatever Unix/Linux or Windows
platform)?
2.how to do the black box with your test script tool?
3. where can I find the sample code to try or study? or a project to
do the test?(Note: Not the Beta testing please.)
Thanks
Reno
Do you Yahoo!?
Take
Yahoo! Mail with you! Get it on your mobile
phone.
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
