Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kelly_Ki]

So, is system testing always at the end of a project. Is there anything that can be done before-hand?

Kelly

[JennyK]

Typically yes; as you need a certain degree of functionality in order to run a system test.

[7cats]

System test requires that the test subject be 'complete' or at least 'usable'.  You are using a 'real' environment, which can be adversely affected if there are significant problems with the item to be tested.  Thus 'at the end' is usually the most practical and most effective place for system testing.

Of course, there are times when some degree of overlap with earlier steps in the process is deemed necessary.  In these cases, it is best if the test systems are isolated from anything else, so if they are 'damaged' by the subject of test, nobody else is affected.  Furthermore, be prepared for 'duplication of work' as multiple phases end up being affected by the same problem, and more 'retesting' of the problem areas.  The better the approved agreement between the various parties, the less contention there is likely to be when things 'bog down'.

Note that System Test is not really the 'very last step'.  There is generally some form of 'customer acceptance' or 'usability' test.  This often is done by customers (early ship program or beta test) before general availability, or formally or informally after GA.  In this case where no such testing will be done pre-GA, the smart system tester will include some of this testing in their system test.

Thanks,
John

[DaveT]

In my experience system testing can get squeezed because it occurs later on in the project. I wish more effort was made in planning the system testing to get the most out of it.

Gaz

[7cats]

Of course it can.  If one or more previous steps 'runs over', then the System test either starts late or starts without every thing needed (via an approved Deviation from the Entry Criteria).  Changing the System test end date is difficult at best.  So when planning the test, you need to be aware of this. 

I will tell you how long it will really take you to test anything: longer than you think it will.

Therefore, we always planned for the likely 'worst case scenario' when determining our initial test length estimates.  And we never planned to spend more time in each week than a normal  (40 hour) work week during the test.  This gave us 2 additional shifts per day and the weekends to compensate for things worse than the worst case scenario (such as earlier steps significantly missing their dates).  The people we saw who used planned overtime for their tests very often came to grief as they did not have enough days to compensate for the unexpected, and the testers lost efficiency as they got worn out. 

John