Practices and Tools for Better Software Testing

Davide Spadini

Research output: Chapter in Book/Conference proceedings/Edited volumeConference contributionScientificpeer-review

2 Citations (Scopus)
254 Downloads (Pure)


Automated testing (hereafter referred to as just ‘testing’) has become an essential process for improving the quality of software systems. In fact, testing can help to point out defects and to ensure that production code is robust under many usage conditions. However, writing and maintaining high-quality test code is challenging and frequently considered of secondary importance. Managers, as well as developers, do not treat test code as equally important as production code, and this behaviour could lead to poor test code quality, and in the future to defect-prone production code. The goal of my research is to bring awareness to developers on the effect of poor testing, as well as helping them in writing better test code. To this aim, I am working on 2 different perspectives: (1) studying best practices on software testing, identifying problems and challenges of current approaches, and (2) building new tools that better support the writing of test code, that tackle the issues we discovered with previous studies.
Original languageEnglish
Title of host publicationProceedings of the 26th ACM Joint Meeting on European Software Engineering Conferenceand Symposium on the Foundations of Software Engineering
Place of PublicationNew York, NY
PublisherAssociation for Computing Machinery (ACM)
Number of pages4
ISBN (Electronic)978-1-4503-5573-5
Publication statusPublished - 2018
EventESEC/FSE 2018 : The 2018 26th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering - Lake Buena Vista, United States
Duration: 4 Nov 20189 Nov 2018
Conference number: 26th


ConferenceESEC/FSE 2018
Country/TerritoryUnited States
CityLake Buena Vista


Dive into the research topics of 'Practices and Tools for Better Software Testing'. Together they form a unique fingerprint.

Cite this