Zobrazeno 1 - 10
of 625
pro vyhledávání: '"Meyer, Bertrand"'
Automatic program repair usually relies heavily on test cases for both bug identification and fix validation. The issue is that writing test cases is tedious, running them takes much time, and validating a fix through tests does not guarantee its cor
Externí odkaz:
http://arxiv.org/abs/2405.01309
Autor:
Meyer, Bertrand
Techniques to achieve various forms of test coverage, such as branch coverage, typically do not iterate loops; in other words, they treat a loop as a conditional, executed zero or one time. Existing work by the author and collaborators produces test
Externí odkaz:
http://arxiv.org/abs/2403.08923
Techniques of Automatic Program Repair (APR) have the potential of thoroughly facilitating the task of producing quality software. After a promising start, however, progress in making APR practical has been hindered by the lack of a common framework
Externí odkaz:
http://arxiv.org/abs/2402.14471
The regression test suite, a key resource for managing program evolution, needs to achieve 100% coverage, or very close, to be useful. Devising a test suite manually is unacceptably tedious, but existing automated methods are often inefficient. The m
Externí odkaz:
http://arxiv.org/abs/2309.04232
The technology of formal software verification has made spectacular advances, but how much does it actually benefit the development of practical software? Considerable disagreement remains about the practicality of building systems with mechanically-
Externí odkaz:
http://arxiv.org/abs/2301.02206
Autor:
Meyer, Bertrand
A description of language design choices that have profound effects on software quality, criticism of how ordinary OO languages address them, and explanation of the thinking behind Eiffel's corresponding mechanisms.
Externí odkaz:
http://arxiv.org/abs/2211.16597
Autor:
Naumcheva, Maria, Ebersold, Sophie, Naumchev, Alexandr, Bruel, Jean-Michel, Galinier, Florian, Meyer, Bertrand
A paradox of requirements specifications as dominantly practiced in the industry is that they often claim to be object-oriented (OO) but largely rely on procedural (non-OO) techniques. Use cases and user stories describe functional flows, not object
Externí odkaz:
http://arxiv.org/abs/2209.02189
Autor:
Huang, Li, Meyer, Bertrand
A successful automated program proof is, in software verification, the ultimate triumph. In practice, however, the road to such success is paved with many failed proof attempts. Unlike a failed test, which provides concrete evidence of an actual bug
Externí odkaz:
http://arxiv.org/abs/2208.09873