Martina Marré

dblp:50/6465 · DBLP profile ↗
← Back
6ranked-venue papers
3as first author
0since 2021 · last 2003
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 6 · 3 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
5 papers
Software testing · 92% Program analysis · 4% Compilers and program optimization · 4%

Topics — the 12 heaviest of 13, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software testing › test adequacy
coverage criteria
0.122003
Using Spanning Sets for Coverage Testing · IEEE Trans. Software Eng. 2003
Reducing and Estimating the Cost of Test Coverage Criteria · ICSE 1996
Software testing › regression testing
test suite reduction
0.012003
Using Spanning Sets for Coverage Testing · IEEE Trans. Software Eng. 2003
Software testing › test process
test cost estimation
0.021996
Unconstrained Duals and Their Use in Achieving All-Uses Coverage · ISSTA 1996
Reducing and Estimating the Cost of Test Coverage Criteria · ICSE 1996
Software testing › test coverage › code coverage
branch coverage
0.021994
Automatic Generation of Path Covers Based on the Control Flow Analysis of Computer Programs · IEEE Trans. Software Eng. 1994
A Meaningful Bound for Branch Testing (Abstract) · ISSTA 1994
Software testing › test generation › white-box test generation
test path generation
0.021996
Automatic Generation of Path Covers Based on the Control Flow Analysis of Computer Programs · IEEE Trans. Software Eng. 1994
Unconstrained Duals and Their Use in Achieving All-Uses Coverage · ISSTA 1996
Software testing › structural testing
data flow testing
0.011996
Unconstrained Duals and Their Use in Achieving All-Uses Coverage · ISSTA 1996
Software testing › test process
test cost reduction
0.011996
Reducing and Estimating the Cost of Test Coverage Criteria · ICSE 1996
Program analysis
control flow analysis
0.011994
Automatic Generation of Path Covers Based on the Control Flow Analysis of Computer Programs · IEEE Trans. Software Eng. 1994
Compilers and program optimization › compiler analysis
dominator trees
0.011994
Automatic Generation of Path Covers Based on the Control Flow Analysis of Computer Programs · IEEE Trans. Software Eng. 1994
Software testing › test coverage
path cover
0.011994
Automatic Generation of Path Covers Based on the Control Flow Analysis of Computer Programs · IEEE Trans. Software Eng. 1994
Software testing
structural testing
0.011994
Automatic Generation of Path Covers Based on the Control Flow Analysis of Computer Programs · IEEE Trans. Software Eng. 1994
Software testing
test coverage
0.011994
A Meaningful Bound for Branch Testing (Abstract) · ISSTA 1994

Methods — techniques the papers use, named apart from their topics

subsumption relation analysis · 0.0empirical study · 0.0graph theory · 0.0subsumption analysis · 0.0branch testing · 0.0
YearPublicationVenuePosition
2003 Using Spanning Sets for Coverage Testing
abstract
A test coverage criterion defines a set E/sub r/ of entities of the program flowgraph and requires that every entity in this set is covered under some test Case. Coverage criteria are also used to measure the adequacy of the executed test cases. In this paper, we introduce the notion of spanning sets of entities for coverage testing. A spanning set is a minimum subset of E/sub r/, such that a test suite covering the entities in this subset is guaranteed to cover every entity in E/sub r/. When the coverage of an entity always guarantees the coverage of another entity, the former is said to subsume the latter. Based on the subsumption relation between entities, we provide a generic algorithm to find spanning sets for control flow and data flow-based test coverage criteria. We suggest several useful applications of spanning sets: They help reduce and estimate the number of test cases needed to satisfy coverage criteria. We also empirically investigate how the use of spanning sets affects the fault detection effectiveness.
Martina Marré, Antonia Bertolino
IEEE Trans. Software Eng.1
1996 Reducing and Estimating the Cost of Test Coverage Criteria
Martina Marré, Antonia Bertolino
ICSE1
1996 Unconstrained Duals and Their Use in Achieving All-Uses Coverage
abstract
Testing takes a considerable amount of the time and resources spent on producing software. It would therefore be useful to have ways 1) to reduce the cost of testing and 2) to estimate this cost. In particular, the number of tests to be executed is an important and useful attribute of the entity "testing effort". All-uses coverage is a data flow testing strategy widely researched in recent years. In this paper we present spanning sets of duas for the all-uses coverage criterion. A spanning set of duas is a minimum set of duas (definition-use associations) such that a set of test paths covering them covers every dua in the program. We give a method to find a spanning set of duas using the relation of subsumption between duas. Intuitively, there exists a natural ordering between the duas in a program: some duas are covered more easily than others, since coverage of the former is automatically guaranteed whenever the latter are covered. Those duas that are the most difficult to be covered according to this ordering are called unconstrained. A spanning set of duas is composed of unconstrained duas. Our results are useful for reducing the cost of testing, since the generation of test paths can be targeted to cover the smaller spanning set of duas, rather than all those in a program. On the other hand, assuming that a different path is taken to cover each dua in a spanning set, the cardinality of spanning sets can be used to estimate the cost of testing. Other interesting uses of spanning sets of duas are also discussed.
Martina Marré, Antonia Bertolino
ISSTA1
1996 How Many Paths are Needed for Branch Testing?
Antonia Bertolino, Martina Marré
J. Syst. Softw.2
1994 A Meaningful Bound for Branch Testing (Abstract)
abstract
Branch coverage is often used to evaluate testing thoroughness. For this reason, it is useful to set a lower bound on the number of test paths needed to achieve branch coverage when estimating how much effort will be needed to test a given program.
Antonia Bertolino, Martina Marré
ISSTA2
1994 Automatic Generation of Path Covers Based on the Control Flow Analysis of Computer Programs
abstract
Branch testing a program involves generating a set of paths that will cover every arc in the program flowgraph, called a path cover, and finding a set of program inputs that will execute every path in the path cover. This paper presents a generalized algorithm that finds a path cover for a given program flowgraph. The analysis is conducted on a reduced flowgraph, called a ddgraph, and uses graph theoretic principles differently than previous approaches. In particular, the relations of dominance and implication which form two trees of the arcs of the ddgraph are exploited. These relations make it possible to identify a subset of ddgraph arcs, called unconstrained arcs, having the property that a set of paths exercising all the unconstrained arcs also cover all the arcs in the ddgraph. In fact, the algorithm has been designed to cover all the unconstrained arcs of a given ddgraph: the paths are derived one at a time, each path covering at least one as yet uncovered unconstrained arc. The greatest merits of the algorithm are its simplicity and its flexibility. It consists in just visiting recursively in combination the dominator and the implied trees, and is flexible in the sense that it can derive a path cover to satisfy different requirements, according to the strategy adopted for the selection of the unconstrained arc to be covered at each recursive iteration. This feature of the algorithm can be employed to address the problem of infeasible paths, by adopting the most suitable selection strategy for the problem at hand. Embedding of the algorithm into a software analysis and testing tool is recommended.>
Antonia Bertolino, Martina Marré
IEEE Trans. Software Eng.2