jUCMNav Testing ProjectTeam members:

Mohammad Al-SubaieAhmed Al-SalehFaisal Al-EshiwyMohammad Al-DulaijanAli Al-Nuami

Outline

About jUCMNav System.Phase 1: Test Plan.Phase 2: Generating Test cases (Junit).Phase 3: Input Space Partitioning .

About jUCMNav SystemjUCMNav 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:

Member Role

Ahmed Al-Saleh Responsible for Inspection (PM)

Mohammad Al-Dulaijan

Responsible for Inspection

Mohammad Al-Subaie Responsible for Test Plan

Faisal Al-Eshiwy Responsible for Test Plan

Ali Al-Nuami Responsible for Test Scheduling

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

informationjUCMNav 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 PlanIn 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:

Member Role

Ahmed Al-Saleh Worked on Generating TCs

Mohammad Al-Dulaijan

Worked on Generating TCs

Mohammad Al-Subaie Worked on Generating TCs

Faisal Al-Eshiwy Worked on Generating TCs (PM)

Ali Al-Nuami Worked on Generating TCs

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 LevelTotal number of TCs generated is approx. 68

TCs. The coverage level were 49% of the package.

Phase 2: Generating Test cases (Junit)

Phase 3: Input Space Partitioning Roles of each team member:

Member Role

Ahmed Al-Saleh Worked on partitioning system inputs

Mohammad Al-Dulaijan

Worked on partitioning system inputs

Mohammad Al-Subaie Worked on partitioning system inputs (PM)

Faisal Al-Eshiwy Worked on partitioning system inputs

Ali Al-Nuami Worked on partitioning system inputs

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.

Phase 3: Input Space Partitioning

Thank You Very Much