| Running software testing projects is far
| |
| | That is no small responsibility to take
|
| more difficult than people outside of the
| |
| | on.
|
| software testing arena seem to realize.
| |
| | So why is it that it always falls on the
|
| It is not uncommon for senior management,
| |
| | software test team to bring in the
|
| project management and development teams
| |
| | schedule when projects start slipping?
|
| to adversely pressurize the test team to
| |
| | We'll, that isn't a difficult one to
|
| cut corners in order to meet delivery
| |
| | answer although there are a couple of
|
| deadlines. Yes, everyone wants to release
| |
| | reasons, one of which might surprise you.
|
| a quality product, on time and on budget.
| |
| | Firstly as testing commonly falls at the
|
| Believe it or not even the software
| |
| | end of the development cycle the software
|
| testing team want to hit the delivery
| |
| | testing component is the only area left
|
| date, with a product that is on budget.
| |
| | where it is even possible to make up
|
| Pushing the software testing team to cut
| |
| | time. Secondly, and possibly more
|
| corners is not the answer though.
| |
| | interestingly, those who have little
|
| It is easy to see that everyone involved
| |
| | knowledge of complexities of software
|
| with a development project wants to
| |
| | testing (for example project mangers)
|
| achieve the same goal and the same
| |
| | think that a little less testing will
|
| successful release, it is just that the
| |
| | only have a little impact on the quality
|
| test team are more cautious than most.
| |
| | of the product. How wrong that assumption
|
| And for good reason; Software testing is
| |
| | can be!Releases of products with serious
|
| difficult! There is no set process that
| |
| | defects usually happen because the
|
| ensures a successful testing project and
| |
| | software test team are forced to cut
|
| there are no software testing tools which
| |
| | corners.
|
| guarantee a successful release. Yet
| |
| | The imprecise nature of software testing,
|
| despite these clearly obvious facts
| |
| | and the pressure to cut corners, means it
|
| senior managers, project managers
| |
| | is very difficult to confidently target
|
| anddevelopment teams always seem to think
| |
| | the test areas such that you minimize the
|
| it is the software test team that can
| |
| | risk of releasing with serious defects
|
| perform some magical act to bring a
| |
| | left uncovered. The very fact that we
|
| project back on schedule when project
| |
| | leave some areas of our testing
|
| deliver schedules start to slip. Well
| |
| | incomplete means we have no idea about
|
| they can't!
| |
| | what we are leaving uncovered. Software
|
| At least they can't if they continue to
| |
| | testing tools can help but as in many
|
| act professionally, accurately and
| |
| | walks of life it all comes down to a
|
| effectively. The test team are, without
| |
| | trade offs between quality and time, but
|
| question, the last check point prior to a
| |
| | with software testing the consequences of
|
| company potentially releasing a product
| |
| | getting the trades offs wrong can be
|
| that destroys the companies reputation.
| |
| | disastrous.
|
