The goal of the artefacts track is to provide a community service whereby people can submit artefacts that become a basis for conducting and evaluating relevant research.
Authors will submit a one page paper (PDF format) file containing:
- Authors and affiliations.
- A brief introduction and detailed instructions on how to setup the artefact.
- A discussion on how the artefact can be used to address a relevant research problem in software testing, verification and validation.
- Description on how to access the artefacts:
- A URL link to download the artifact, such as a GitHub or bitbucket repository, Dropbox or Google Drive folder.
- In case the link cannot be provided, authors must provide instructions on how the track chairs will get access to the artifacts.
- In case the submitted artefact has been used in a published paper, a reference to that paper should be provided.
The submitted artefacts will be evaluated based on:
- The effort to understand and reuse the artifacts according to the provided instructions.
- How it can be used to address a relevant research problem in software testing, verification & validation.
All submitted artefacts will be evaluated by the artefacts track chairs and be classified into either successfully evaluated or rejected. Successfully evaluated artefacts will be made publicly available.
For a list of known artefacts types, please see:
|Submission||January 12th, 2018|
|Notification of acceptance||February 12th, 2018|