Searched for: author%3A%22Brandt%2C+C.E.%22
(1 - 10 of 10)
document
Brandt, C.E. (author)
Developer testing has become an established practice in large software projects. The developers working on the functionality of a project also write short, automated scripts that check the behavior of their code. While the benefits of developer testing are widely accepted, writing tests is still seen as tedious and time-consuming. Researchers...
doctoral thesis 2024
document
Brandt, C.E. (author), Khatami, Ali (author), Wessel, Mairieli (author), Zaidman, A.E. (author)
Test amplification makes systematic changes to existing, manually written tests to provide tests complementary to an automated test suite. We consider developer-centric test amplification, where the developer explores, judges and edits the amplified tests before adding them to their maintained test suite. However, it is as yet unclear which...
journal article 2024
document
Brandt, C.E. (author), Castelluccio, Marco (author), Holler, Christian (author), Kratzer, Jason (author), Zaidman, A.E. (author), Bacchelli, Alberto (author)
Can fuzzers generate partial tests that developers find useful enough to complete into functional tests (e.g., by adding assertions)? To address this question, we develop a prototype within the Mozilla ecosystem and open 13 bug reports proposing partial generated tests for currently uncovered code. We found that the majority of the reactions...
conference paper 2024
document
Brandt, C.E. (author), Wang, D. (author), Zaidman, A.E. (author)
Test amplification generates new tests by mutating existing, developer-written tests and keeping those tests that improve the coverage of the test suite. Current amplification tools focus on starting from a specific test and propose coverage improvements all over a software project, requiring considerable effort from the software engineer to...
conference paper 2023
document
Boone, Casper (author), Brandt, C.E. (author), Zaidman, A.E. (author)
The most common reason for Continuous Integration (CI) builds to break is failing tests. When a build breaks, a developer often has to scroll through hundreds to thousands of log lines to find which test is failing and why. Finding the issue is a tedious process that relies on a developer's experience and increases the cost of software testing....
conference paper 2022
document
Brandt, C.E. (author), Zaidman, A.E. (author)
Developer testing, the practice of software engineers programmatically checking that their own components behave as they expect, has become the norm in today's software projects. With the constantly growing size and complexity of software projects and with the rise of automated test generation tools, understanding a test case is becoming more...
conference paper 2022
document
Brandt, C.E. (author), Zaidman, A.E. (author)
Automatically generating test cases for software has been an active research topic for many years. While current tools can generate powerful regression or crash-reproducing test cases, these are often kept separately from the maintained test suite. In this paper, we leverage the developer’s familiarity with test cases amplified from existing,...
journal article 2022
document
Oosterbroek, W. (author), Brandt, C.E. (author), Zaidman, A.E. (author)
Test amplification generates new tests by modifying existing, manually written tests.<br/>Up until now, this process preserves statements that were relevant for the original test case but are no longer needed for the behavior of the new test case.<br/>These unnecessary statements impact the readability of the tests in question.<br/>As a part of...
conference paper 2021
document
Nijkamp, N. (author), Brandt, C.E. (author), Zaidman, A.E. (author)
Test amplification generates new test cases that improve the coverage of an existing test suite. To convince developers to integrate these new test cases into their test suite, it is crucial to convey the behavior and the improvement in coverage that the amplified test case provides. In this paper, we present NATIC, an approach to generate names...
conference paper 2021
document
Brandt, C.E. (author), Panichella, A. (author), Zaidman, A.E. (author), Beller, M.M. (author)
Build logs are textual by-products that a software build process creates, often as part of its Continuous Integration (CI) pipeline. Build logs are a paramount source of information for developers when debugging into and understanding a build failure. Recently, attempts to partly automate this time-consuming, purely manual activity have come up,...
conference paper 2020
Searched for: author%3A%22Brandt%2C+C.E.%22
(1 - 10 of 10)