Download
1 / 11
110 likes | 232 Views
jUCMNav Testing Project. Team members: Mohammad Al- Subaie Ahmed Al- Saleh Faisal Al- Eshiwy Mohammad Al- Dulaijan Ali Al- Nuami. Outline. About jUCMNav System. Phase 1: Test Plan. Phase 2: Generating Test cases ( Junit ). Phase 3: Input Space Partitioning. About jUCMNav System.
E N D
jUCMNav Testing Project Team members: Mohammad Al-Subaie Ahmed Al-Saleh Faisal Al-Eshiwy Mohammad Al-Dulaijan Ali Al-Nuami
Outline • About jUCMNavSystem. • Phase 1: Test Plan. • Phase 2: Generating Test cases (Junit). • Phase 3: Input Space Partitioning .
About jUCMNav System • jUCMNav is a free, Eclipse-based graphical editor and an analysis and transformation tool for the User Requirements Notation (URN). • URN is intended for the elicitation, analysis, specification, and validation of requirements. • URN combines two complementary views: one for goals provided by the Goal-oriented Requirement Language (GRL) and one for scenarios provided by the Use Case Map (UCM) notation.
Phase 1: Test Plan • Roles of each team member:
Phase 1: Test Plan In this phase we developed the test plan document, containing : • Software Project Introduction: • This section describes project overview and deliverables. • Software Overview: • This section provide the software size information • jUCMNav contains 1737 Classes & 138000 LOC
Phase 1: Test Plan • Software Inspection • After performing software inspection on 151 classes we found the following results: • Total number of defects is 334 defects. • No. of Defects per class is 2.2 defects. • No. of Defects per type is 11.3 defects. • Test Plan • In this section, 33 TCs were created without looking on the internal design of the system.
Phase 2: Generating Test cases (Junit) • Roles of each team member:
Phase 2: Generating Test cases (Junit) In this phase we generated test cases using Junit. • Configuration Details • UCM\Scenario package was chosen to apply Junit test on it. • UCM\Scenario package contains 9 major classes. • Coverage Level • Total number of TCs generated is approx. 68 TCs. • The coverage level were 49% of the package.
Phase 3: Input Space Partitioning • Roles of each team member:
Phase 3: Input Space Partitioning In this phase we conducted Input Space Partitioning for UCM\Scenario package. • Input Space Partitioning Based Testing. • We used interface-based input space partitioning. • For the coverage, we used All Combination Coverage (ACoC) Each Choice Coverage (ECC). • We created 196 Combination for the methods tested in Phase 2.
