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

Mainul Islam

dblp:121/6364 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2014
—ORCID · none

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

Software engineering, systems software and programming languages · 1 · 1 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
1 paper
Software testing · 50% Program analysis · 50%

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

TopicWeightPapersLastEvidence papers
Program analysis
constraint solving
0.212014
Generating Test Cases for Programs that Are Coded against Interfaces and Annotations · ACM Trans. Softw. Eng. Methodol. 2014
Program analysis › symbolic execution
dynamic symbolic execution
0.212014
Generating Test Cases for Programs that Are Coded against Interfaces and Annotations · ACM Trans. Softw. Eng. Methodol. 2014
Software testing › test infrastructure
mock generation
0.212014
Generating Test Cases for Programs that Are Coded against Interfaces and Annotations · ACM Trans. Softw. Eng. Methodol. 2014
Software testing
test generation
0.212014
Generating Test Cases for Programs that Are Coded against Interfaces and Annotations · ACM Trans. Softw. Eng. Methodol. 2014

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

reflection · 0.2dynamic symbolic execution · 0.2constraint solver · 0.2
YearPublicationVenuePosition
2014 Generating Test Cases for Programs that Are Coded against Interfaces and Annotations
abstract
Automatic test case generation for software programs is very powerful but suffers from a key limitation. That is, most current test case generation techniques fail to cover testee code when covering that code requires additional pieces of code not yet part of the program under test. To address some of these cases, the Pex state-of-the-art test case generator can generate basic mock code. However, current test case generators cannot handle cases in which the code under test uses multiple interfaces, annotations, or reflection. To cover such code in an object-oriented setting, we describe a novel technique for generating test cases and mock classes. The technique consists of collecting constraints on interfaces, annotations, and reflection, combining them with program constraints collected during dynamic symbolic execution, encoding them in a constraint system, solving them with an off-the-shelf constraint solver, and mapping constraint solutions to test cases and custom mock classes. We demonstrate the value of this technique on open-source applications. Our approach covered such third-party code with generated mock classes, while competing approaches failed to cover the code and sometimes produced unintended side-effects such as filling the screen with dialog boxes and writing into the file system.
Mainul Islam, Christoph Csallner
ACM Trans. Softw. Eng. Methodol.1