SCM to Support Software Testing

Area of
Interest
Software
Configuration
Management
Software
Traceability
Software
Testing
Hypothesis/Problem Statement:
How the test case maintenance could be supported through Software
Configuration Management (SCM) and traceability approaches for
maintenance testing?
Research Keywords
Software Configuration
Management
Version Control
Manage Changes
Software Configuration
Management
Change control system
Configuration management
Change request
Versioning
Problem Change Request
Modification request
Change propagation

Software Test Maintenance

Test case
Test suite
Test case strategies
Test maintenance
Manage test case
Manage test
GUI test case
Test suite management
Test case management
Test case evolutionary
Software traceability
Related Papers
> 60
Test
Management
Related
> 60
Traceability
Related
> 60
SCM Related
SWEBOK Ch.6
Software
Maintenance
Fundalmental
Technical
issues
Impact analysis
Management
issues
Process
Maintenance
Cost Estimation
Cost Estimation
Evolution of
Software
Key Issues in Software
Maintenance
Evolution of
Software
Key Issues in Software
Maintenance
Management
issues
Process
Software
Maintenance
Fundalmental
SCM to Support Software Testing
Bertolino 2007 Software Testing Research: Achievement, Challenges and Dreams
Research Context
No. Research Questions Objectives Activities Deliverables
1. Why current test case maintenance
approaches do not satisfy the
developer/tester during software testing
lifecycle?
To investigate and
evaluate current existing
approaches to support
software maintenance
testing
Literature Study

Comparative study
Result of comparative
study

Analysis of the result
2. How to support test case maintenance
during maintenance testing phase in the
best way?
To develop a new
approach that utilizes
SCM and traceability
features and create
supporting tool that
support the proposed
approach
Building a proposed
approach

Building a
supportive tool
The proposed
approach

The supporting tool
3. How to measure the approach? To demonstrate the
capability of the
proposed approach
Applying case
studies

Analyse the results
Results analysis
4. How to validate the effectiveness of the
proposed approach in supporting test
case maintenance to some significance
degree?
To evaluate the
effectiveness of the
proposed approach
against the existing test
case maintenance
approaches through
obtained results using the
supporting tool.
Experimentation

Measuring results
gained fromtool

Analyse the results
1. Usability values
2.
3. Results analysis

Research
Questions
Are there any existing
approaches?
How to support test case
maintenance?
How to measure the test case
maintenance approach?
How to validate the approach to
some significance degree?
SCM to Support Software Testing
Comparative I
O
l
i
v
e
t
t
o

2
0
0
7
.

S
o
f
t
w
a
r
e

a
r
t
e
f
a
c
t
s

t
r
a
c
e
a
b
i
l
i
t
y

Are there any existing approaches? (RQ1)
Comparative II
B
u
c
k
l
e
y

2
0
0
5

e
t
.

a
l
.

S
o
f
t
w
a
r
e

t
a
x
a
n
o
m
y

e
v
o
l
u
t
i
o
n

Comparative III
B
u
c
k
l
e
y

2
0
0
5

e
t
.

a
l
.

S
o
f
t
w
a
r
e

t
a
x
a
n
o
m
y

e
v
o
l
u
t
i
o
n

Comparative IV
E
s
t
u
b
l
i
e
r
,

2
0
0
0
,

2
0
0
5

S
C
M

i
m
p
a
c
t

o
n

S
E

P
r
a
c
t
i
c
e
s


On The Making
B
e
r
t
i
l
l
i
n
o

2
0
0
7
,

S
o
f
t
w
a
r
e

T
e
s
t
i
n
g

R
e
s
e
a
r
c
h

R
o
a
d
m
a
p


Research
Questions
Are there any existing
approaches?
How to support test case
maintenance?
How to measure the test case
maintenance approach?
How to validate the approach to
some significance degree?
SCM to Support Software Testing
The Idea
Some of rational questions on change trace?
(L.Murta et. al. 2007)
Who changed it?
What was changed?
When was it changed?
Using one of these SCM approaches
Structural Based Versioning
Component based
Operational based
File Based Versioning
Model based
File Text based
How to support test case maintenance? (RQ2)
Conceptually
Superclass
S
Subclass
S1
Subclass
s1-1
Subclass
s1-2
Subclass
S2
Subclass
s2-1
CSC v1
CSU s1-1 v1 CSU s1-2 v1 CSU s1-3 v1
CSC s1 v1
Text Based Structure Based Structure Based Versioning
Superclass
S
Subclass
S1
Subclass
s1-1
Subclass
s1-2
Subclass
S2
Subclass
s2-1
Subclass
s2-2
CSC v1
CSU s1-1 v1 CSU s1-2 v1 CSU s1-3 v1
CSU s1-3-1 v1
CSC s1 v1
Workflow
Index all the
artefacts
Set artefact
new version
1 2
Establish
Traceability
Data
base
Changes
(PCR)
3
Upon PCR, auto
created child node
from artefacts tree
& update
traceability
4
Parsing all
artefacts
read
write
Identify possible
impact upon
creating new version
of artefacts (i.e. test
case point of view)
5
Results
Able to visualize the old version and new
version of artefacts using version control
Able to see which changes that cause the test
case tree to be updated with new node
Able to measure completeness between
changes from req. to testing phase.
The Model
Indexed Testing Elements of
Case Studies Repository
Test Element
Viewer
Version Control of
Testing Elements
Establish
Traceability links
Automate
Changes
Execution
Change
Request
s
Versioned of Testing
Elements
Initializing
Testing
Elements
Indexing Test
Elements
Existing Case Studies
Repository
Parsing
Testing
Elements
Traceability
Visualizatio
n
Traceability
Visualizatio
n with
changes
C
h
a
n
g
e

P
r
o
c
e
s
s

Traceability
Generator
The prototype model
Research
Questions
Are there any existing
approaches?
How to support test case
maintenance?
How to measure the test case
maintenance approach?
How to validate the approach to
some significance degree?
SCM to Support Software Testing
Measurement would be based on these criteria:
Efficacy
Completeness
Link evolution
Level of granularity
Coarse
Medium
Fine
Artefacts
Static evolution
Dynamic evolution


SCM to Support Software Testing
How to measure test case maintenance? (RQ3)


SCM to Support Software Testing
How to measure test case maintenance? (RQ3)
Quantitative Based
Observation
Finding Research
Gap
Hypothesis Problem Statement
Controlled
Experimentation
Quasi
Experimentation
Statistical Analysis
Empiricism
Math Proof
An overview plan revisited
Phase I
Phase II
Research
Questions
Are there any existing
approaches?
How to support test case
maintenance?
How to measure the test case
maintenance approach?
How to validate the approach to
some significance degree?
SCM to Support Software Testing
Using Quality Model ISO/IEC 9126-1:2001(E)



SCM to Support Software Testing
How to validate the approach? (RQ4)
Threats to Validity
Need a complete set of software
documentations as well as the source codes
Relying on object oriented approach and this
approach will ceased to work on structure
oriented development approach
Scalability i.e.: Global Software Development
platform is too complex and complicated
involved demographic issues.
Online Reference Links
Resources
IEEE Xplore @
ieeexplore.ieee.org
ACM Digital Library @
www.portal.acm.org
Google Scholar @
scholar.google.com