Name
Abstract | ||
|---|---|---|
It is a continuous struggle to understand how much a product should be tested before the delivery to the market. Ericsson decided to evaluate the adequacy of unit test coverage criterion that they employed for years as a guide for sufficiency of testing. Naturally, if increasing coverage decreases the number of defects significantly, then coverage measures can be considered as criteria for test sufficiency. To test this hypothesis in practice, we investigated the relationship of unit test coverage measures and post-unit-test defects in a large commercial product of Ericsson. The results indicate that the sheer fulfillment of coverage does not seem to be any tangible help in producing defect-free software.
|
Year | DOI | Venue |
|---|---|---|
2018 | 10.1109/MS.2017.3281318 | IEEE Software |
Keywords | Field | DocType |
code complexity, metrics, test coverage, unit test | Code coverage,Software engineering,Computer science,Cyclomatic complexity,Unit testing,Global software development,Software,Software metric,Software development,Software testing | Journal |
Volume | Issue | ISSN |
35 | 3 | 0740-7459 |
Citations | PageRank | References |
3 | 0.40 | 0 |
Authors | ||
4 | ||
Name | Order | Citations | PageRank |
|---|---|---|---|
| Vard Antinyan | 1 | 11 | 4.00 |
| Jesper Derehag | 2 | 6 | 0.80 |
| Anna Börjesson Sandberg | 3 | 42 | 4.96 |
| Miroslaw Staron | 4 | 486 | 52.25 |