|
At
the August membership meeting our own panel of experts went to work on
a number of questions. Here are the questions they tackled, and the "answers"
They came up with.
Question
#1: How to get testing out of the way and in stages so there isn't crunch-testing
time? Managing changes so that they are coming in for steady stream of
testing and not all at once at the time of testing freeze.
Note: For this question, there
were three breakout groups that addressed the same topic.
Question
#2: What measures should be use to measure IT effectiveness and project
success?
Question
#3: How to keep a regression database up to date and not lose integrity?
Functionality changes, so does time, how do you keep up with time without
losing the integrity of the data you have for regression testing?
Question
#4: Today, we have some customers that document requirements, some that
don't document them at all and some are somewhere in the middle. Often,
the requirements are in different formats. We would like to have a consistent
approach to documenting requirements and a good process to trace test
cases back to the requirements. Any suggestions in the method and tools
to use for documenting requirements and making the requirements traceable
to the test cases would be much appreciated.
|