Testing Project Description
Adam Rivard
My group went to class yesterday to ask questions of the professor, but he
was absent. We are looking for clarification on a few points:
First, 2 questions pertaining to: "Section 2: Feature Description (a table
listing feature IDs, and a short English description for each basic feature
ID in Call Forwarding)"
1. What constitutes a "feature"? Is not being able to call forward to
yourself a feature? If not, what is an example of a feature? Is there
documentation on what a feature is?
2. Do things other than Call Forwarding have features that we are supposed
to list here, or are we ONLY supposed to put Call Forwarding features down?
The reason we ask is because it sounds like you want other features listed,
but only the ones for CF described.
Second, we went to class with the explicit intention of getting official
confirmation from the professor about System Tests being run manually.
Since he wasn't there, our only recourse is to ask here. We know it has
been asked before, but it has also not been officially answered by course
staff.
Thirdly, pertaining to: "You are required to identify all test cases which
are inferred by the criterion for each method but implement and run only 5
of these test cases." Do Control Flow Graphs identify all test cases
sufficiently? Are we supposed to mark on the CFG's where the test cases
come from? Are we supposed to list all possible test cases and mark which
ones we picked? Is this a decision that is left to us to make, or is there
a set form we are supposed to use? We aren't entirely sure what this
sentence means in terms of what is required of us.
Thank you for your time and assistance
-Adam, Steve, Wes
Aaron Gourley
Source: http://en.wikipedia.org/wiki/Feature
In telephony, a feature is an atomic piece of functionality that can be sold
individually to customers or combined with others to create a composite
service.
"Adam Rivard" <ari...@uwaterloo.ca> wrote in message
news:e03ruf$6f7$1...@rumours.uwaterloo.ca...