Clarifications for the Testing Framework

[Kostas Kontogiannis]

Hi all,

Some clarifications on the documents you are drafting.

1. SRS pertains only for the extensions
2. SDD pertains both to the extensions and the testing infrastructure

For the testing infrastructure in the SDD (and in addition of what
you will be specifying for the system extensions
FWDing/Internationalization - in the SDD) you include the following:

A. For the Testing Framework in the SDD

*Design decisions
*Component Diagram with description of external interfaces
*Detailed class diagram with data dictionary
*Object Diagram
*Message Sequence Chart
*Pseudocode for the major methods of your framework (not include
helper methods or accessors and mutators. Pseudocode can be as
detailed as your implementation or as abstract as real pseudocode
(English mixed with code)
*Schema for test drivers and stub oracles

B For the system extensions in the SDD
As specified in project description and the notes.


Greetings,

Kostas Kontogiannis

[Ricky Wing Ki Chan]

Regarding the message sequence chart for the testing framework in the SDD
- Isn't a message sequence chart usually in the SRS along with the use
case scenarios? How would a message sequence chart look like for the
testing framework, since it doesn't have any actors? Would it be
essentially a call graph between drivers, classes, and stubs?

Thanks,
Ricky Chan

Post by Kostas Kontogiannis
Hi all,
Some clarifications on the documents you are drafting.
1. SRS pertains only for the extensions
2. SDD pertains both to the extensions and the testing infrastructure
For the testing infrastructure in the SDD (and in addition of what
you will be specifying for the system extensions FWDing/Internationalization
A. For the Testing Framework in the SDD

...

Post by Kostas Kontogiannis
*Message Sequence Chart

...

[Jonathan]

Are we required to use stub oracles for our testing framework?

-Jonathan

Post by Kostas Kontogiannis
Hi all,
Some clarifications on the documents you are drafting.
1. SRS pertains only for the extensions
2. SDD pertains both to the extensions and the testing infrastructure
For the testing infrastructure in the SDD (and in addition of what
you will be specifying for the system extensions
A. For the Testing Framework in the SDD
*Design decisions
*Component Diagram with description of external interfaces
*Detailed class diagram with data dictionary
*Object Diagram
*Message Sequence Chart
*Pseudocode for the major methods of your framework (not include
helper methods or accessors and mutators. Pseudocode can be as
detailed as your implementation or as abstract as real pseudocode
(English mixed with code)
*Schema for test drivers and stub oracles
B For the system extensions in the SDD
As specified in project description and the notes.
Greetings,
Kostas Kontogiannis