Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Patrick J. Schroeder

dblp:02/58 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 2002
—ORCID · none

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

Software engineering, systems software and programming languages · 2 · 2 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
2 papers
Software testing · 100%

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

TopicWeightPapersLastEvidence papers
Software testing
black-box testing
0.122002
Generating Expected Results for Automated Black-Box Testing · ASE 2002
Black-box test reduction using input-output analysis · ISSTA 2000
Software testing
combinatorial testing
0.012002
Generating Expected Results for Automated Black-Box Testing · ASE 2002
Software testing › test generation
test suite generation
0.012002
Generating Expected Results for Automated Black-Box Testing · ASE 2002
Software testing › test optimization
test case reduction
0.012000
Black-box test reduction using input-output analysis · ISSTA 2000

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

input-output relationship analysis · 0.0automated input-output analysis · 0.0
YearPublicationVenuePosition
2002 Generating Expected Results for Automated Black-Box Testing
abstract
In this paper we describe a technique for generating expected results for automated black-box testing. Generating expected results allows larger automated test suites to be created, moving us toward continuous product testing. Our technique uses a program's Input-Output (IO) relationships to identify unique combinations of program inputs that influence program outputs. With this information, a small set of test cases is executed and checked for correctness. Given the correctness of this set, the expected results for the larger combinatorial test set can be generated automatically. Included in the paper is an experimental study in which checking the results of 384 test cases allows us to generate expected results and fully automate nearly 600,000 test cases.
Patrick J. Schroeder, Pat Faherty, Bogdan Korel
ASE1
2000 Black-box test reduction using input-output analysis
abstract
Test reduction is an important issue in black-box testing. The number of possible black-box tests for any non-trivial software application is extremely large. For the class of programs with multiple inputs and outputs, the number of possible tests grows very rapidly as combinations of input test data are considered. In this paper, we introduce an approach to test reduction that uses automated input-output analysis to identify relationships between program inputs and outputs. Our initial experience with the approach has shown that it can significantly reduce the number of black-box tests.
Patrick J. Schroeder, Bogdan Korel
ISSTA1