Getting up to speed on QA
Hello.
My company is in the process of developing a major low-level upgrade of our application. It's a
a WATCOM C application, and we are porting
it from 16-bit DOS to 32-bit NT. it is NOT
a windows application: it runs from the command prompt.
Most of the development is being done offsite.
Early testing has convinced me that we have
an exhaustive QA effort ahead of us, both in
identifying what exactly needs to be tested, and
actually doing the testing.
Can anyone offer any suggestions as to how
to approach this task? Either some actual
pointers, or perhaps suggesting a book (for
us to learn) or a tool (that might aid our
efforts)?
Many thanks!
stevefromc
My company is in the process of developing a major low-level upgrade of our application. It's a
a WATCOM C application, and we are porting
it from 16-bit DOS to 32-bit NT. it is NOT
a windows application: it runs from the command prompt.
Most of the development is being done offsite.
Early testing has convinced me that we have
an exhaustive QA effort ahead of us, both in
identifying what exactly needs to be tested, and
actually doing the testing.
Can anyone offer any suggestions as to how
to approach this task? Either some actual
pointers, or perhaps suggesting a book (for
us to learn) or a tool (that might aid our
efforts)?
Many thanks!
stevefromc
ASKER
Not exhaustive nor paticularly formal. They know that the general concepts (dealing with 16/32 bit integer issues, screen handling issues, etc) but I do not believe a detailed, formal spec exists.
Thanks
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks. I think that writing up the test cases, and asking for input from others (in
this case it might be other people in my programming/tech support departments).
Your ponts are very valid and personally I am always in favor of detailed functional specs.
These methods aside, do you (or anyone else out there) know of any good QA books
that might help?
Thanks again
stevefromc
this case it might be other people in my programming/tech support departments).
Your ponts are very valid and personally I am always in favor of detailed functional specs.
These methods aside, do you (or anyone else out there) know of any good QA books
that might help?
Thanks again
stevefromc
AW