🔒 Locked

Testing procedures

Started by rsegal Aug 1, 2003 at 1:53 PM 4 replies 650+ views

Original Post

Aug 1, 2003 at 1:53 PM

For those who have actually developed a commercial software project of some kind (not necessarily a game), what kind of testing procedures did you use? I''m curious to here, -Did you use an external beta test? -Did you have public users come in and do in house testing? -What percentage of the project schedule did you devote to testing? -What worked or didn''t work? And anything else people can think of. What worked, didn''t work. Testing is perhaps not a very largely discussed topic in game development but it is part of every type of software project which of course includes games.

khawk

Aug 4, 2003 at 12:09 PM

quote:
Original post by rsegal
For those who have actually developed a commercial software project of some kind (not necessarily a game), what kind of testing procedures did you use?

I''m curious to here,

-Did you use an external beta test?

We do internal testing prior to the customer test.

quote:

-Did you have public users come in and do in house testing?

After we do our own internal testing phase, the customers/users come in and execute the test procedures on their own. They are also given a period to execute the system without any procedures.

quote:

-What percentage of the project schedule did you devote to
testing?

~15-20%

quote:

-What worked or didn''t work?

What doesn''t work: Changing and adding requirements during testing. If you want to slip schedule and blow up costs, requirement changes in testing is the way to go.

What does work: Iterative builds with testing. Internal testing prior to customer tests.

MichaelCarr

Aug 4, 2003 at 7:22 PM

-Did you use an external beta test?
Sometimes, depends how much work the test department has.

-Did you have public users come in and do in house testing?
yes

-What percentage of the project schedule did you devote to
testing?
30-40%

-What worked or didn''t work?
It doesn''t work isolating the test department from the developers. Makes it really difficult to get answers when you need more information.

Michael

rsegal

Aug 31, 2003 at 7:46 PM

How about regression testing on new software? Ideally you would want to test everything again to see how it plays out with the new implemented features. However, obviously it takes a good chunk of time which is not always available. Any stories out there on whether regression testing is worth the effort?

khawk

Sep 3, 2003 at 8:11 AM

quote:
Original post by rsegal
How about regression testing on new software? Ideally you would want to test everything again to see how it plays out with the new implemented features. However, obviously it takes a good chunk of time which is not always available. Any stories out there on whether regression testing is worth the effort?

It depends on the status of the project. If we''re in development, then regression testing is left up to the engineer. If we''re in testing, then regression testing is performed after each test build (the ones with defect fixes).

bgreen

Sep 3, 2003 at 8:28 AM

I used to work on the core transaction processing system for a major bank. Makes you realise just how important regression testing is, especially in a mission critical application such as one that pretty much processes every transaction that is generated.

This was done incorrectly (or not even at all) once, and the amount of headaches that the support team went through once the software was installed still gives me nightmares!

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.