2013
DOI: 10.1016/j.compbiomed.2013.01.024
|View full text |Cite
|
Sign up to set email alerts
|

Integration testing through reusing representative unit test cases for high-confidence medical software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0
1

Year Published

2014
2014
2024
2024

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 34 publications
0
5
0
1
Order By: Relevance
“…Approaches that compose integration tests from unit tests and some software modules [24], [29], [31], [32] address a different angle of the problem than ASSIST -the latter concentrate on producing effective integration tests efficiently, while it is unclear how the former approach addresses a problem of reducing the large number of combinations of unit tests into integration tests.…”
Section: Related Workmentioning
confidence: 99%
“…Approaches that compose integration tests from unit tests and some software modules [24], [29], [31], [32] address a different angle of the problem than ASSIST -the latter concentrate on producing effective integration tests efficiently, while it is unclear how the former approach addresses a problem of reducing the large number of combinations of unit tests into integration tests.…”
Section: Related Workmentioning
confidence: 99%
“…Z kolei programiści z wielu firm przedstawiają wykorzystanie napisanych testów jednostkowych jako testów regresyjnych, które w krótkim czasie są w stanie potwierdzić działanie całego produktu [9]. Natomiast koreańscy naukowcy przedstawiają mo liwość wykorzystania istniejących testów jednostkowych do wygenerowania testów integracyjnych, jako bazę scenariuszy testowych [10]. Odnosząc się do znanej mantry "red-green-refactor" [7] z metodyki TDD, mo na do niej przypisać odpowiednie kroki schematu:…”
Section: Znaczenie Testów Jednostkowychunclassified
“…According to [10], [11], testing accounts for more than 50% of the cost of software development. In software testing, two methodologies are often used: black box and white box [12]. The former is concerned with testing the functionality of the software under test without knowledge of the structure or implementation specifics.…”
Section: Introductionmentioning
confidence: 99%