Testing ToolsICST 2023

The Testing Tools Track seeks to bridge the gap between research and practice, focusing on software testing, verification, and validation. Its main goal is to advance both the state of ​the ​art and the state ​of ​the practice. The track invites submissions that describe tools at several stages of maturity, including promising research prototypes, widely used research tools, and commercial tools (if they contribute to the scientific knowledge). This track seeks submissions from both ​academia and industry to foster discussions between researchers and practitioners.

The submission details:

• Testing tool paper (max 10 pages + references) and a demo video of 3-5 mins

Accepted papers will be published in ICST conference proceedings.

Supporters

Diamond Sponsor

Platinum Sponsor

Platinum Sponsor

Gold Sponsor

Silver Sponsor

Bronze Sponsor

Accepted Papers

ICST 2023 Testing Tools Call for Papers

The Testing Tools Track seeks to bridge the gap between research and practice, focusing on software testing, verification, and validation. Its main goal is to advance both the state of ​the ​art and the state ​of ​the practice. The track invites submissions that describe tools at several stages of maturity, including promising research prototypes, widely used research tools, and commercial tools (if they contribute to the scientific knowledge). This track seeks submissions from both ​academia and industry to foster discussions between researchers and practitioners.

The submission details:

• Testing tool paper (max 10 pages + references) and a demo video of 3-5 mins

Accepted papers will be published in ICST conference proceedings.

Tool paper submissions should clearly describe the complexity of the addressed problem, solved technical challenges, and validation that the tool actually works (e.g., from previous published research work, or new experiments, with preferably experiences from using the tool in industry). Researchers are welcome to submit papers that describe novel approaches and how these approaches support tool developers in solving challenging problems.

The tool paper should clearly communicate the following information to the audience:

• The envisioned users of the tool;
• The software engineering challenge the tool addresses;
• The testing process or testing technique implemented by the tool;
• The implied use case scenario for its users;
• The results of validation studies already conducted, for more mature tools, or the design of the planned studies, for early prototypes;
• The potential ways that the tool could be extended (bu the authors or the community) in the future.

The tool itself should be made available, if not already, for researchers or practitioners to use. At minimum, the tool should be accessible (either free to download or for purchase). If possible, the source code of the tool should also be available as well. Exceptions will be made to this rule if a valid reason is provided for why the tool cannot be released (e.g., organizational rules or it was developed for internal use in a company and cannot be made public).

Areas of interest:

The Testing Tools track invites submissions related, but not limited, to the following areas:

• Design and development of novel tools for software testing, verification, and validation;
• Working prototypes for novel research approaches, reporting on the technical challenges and early feedback obtained from practitioners;
• Strategies and challenges for tool adoption as well as lessons learned from technology transfer of academic approaches into open source or commercial tools;
• Case studies and/or experiments involving tools in particular contexts, reporting on lessons learned and negative results (if any).

Evaluation:

Each submission will be evaluated based on:

• The relevance and significance of the addressed problem.
• The innovation element of the approach.
• The availability, maturity, and adoption of the tool.
• The presence of lessons learned from developing or using the tool.
• The quality of the presentation.

Accepted papers will appear in the ICST conference proceedings and the IEEE digital library.

Relationship to Demonstrations track:

Authors of tool papers will be asked to give a demonstration of the tool, in the same way as the authors of demonstration papers (extended abstracts). The extra page space for tool papers compared to demonstration papers is to provide more insight about the tool and how it can be used (e.g., about the Software Engineering challenges and lessons learned behind building such tools). Therefore, authors of tool papers are not allowed to submit a demonstration paper for the same tool. In the case in which the insights provided by a tool paper are not considered of sufficient scientific and engineering quality, the paper could still be accepted as a (shorter) Demonstrations abstract instead (if the authors agree).

Submission​:

Submissions will be handled via EasyChair (ICST2023 / Testing Tools Track).

The Testing Tools Track of ICST 2023 uses ​single-anonymous reviewing,​ which means that authors and tools do not have to be anonymized​. All submitted papers must conform to the two ​column IEEE conference publication format. Templates for Latex and Word are available at: http://www.ieee.org/conferences_events/conferences/publishing/templates.html;​

• It must conform to the IEEE Conference Proceedings Formatting Guidelines (please use the letter format template and conference option).
• Testing tool papers must be submitted as PDF.
• The tool ​papers​ must not exceed 10 pages, including all text, figures, tables, and appendices; two additional pages containing only references are permitted.
• The submissions must have a demo video with length of 3 - 5 minutes, and the submission must have a link to an online location that allows reviewers to watch it.

The submission must also comply with the ACM plagiarism policy and procedures. In particular, the same content must not have been published elsewhere and must not be under review elsewhere while under review for ICST. The submission must also comply with the IEEE Policy on Authorship.