DOI: 10.5281/zenodo.3856669
title: Test Suites from Test-Generation Tools (Test-Comp 2019)

description: This file describes the contents of an archive of the<br> 1st Competition on Software Testing (Test-Comp 2019)<br> https://test-comp.sosy-lab.org/2019/ The competition was run by Dirk Beyer, LMU Munich, Germany.<br> More information is available in the following article:<br> Dirk Beyer. First International Competition on Software Testing: Test-Comp 2019.<br> International Journal on Software Tools for Technology Transfer, 2020. Copyright (C) Dirk Beyer<br> https://www.sosy-lab.org/people/beyer/ SPDX-License-Identifier: CC-BY-4.0<br> https://spdx.org/licenses/CC-BY-4.0.html Contents: LICENSE.txt specifies the license<br> README.txt this file<br> witnessFileByHash/ This directory contains test suites (witnesses for coverage).<br> Each witness in this directory is stored in a file whose name is the SHA2 256-bit hash<br> of its contents followed by the filename extension .zip.<br> The format of each test suite is described on the format web page:<br> https://gitlab.com/sosy-lab/software/test-format<br> A test suite contains also metadata in order to relate it<br> to the test problem for which it was produced.<br> witnessInfoByHash/ This directory contains for each test suite (witness) in directory witnessFileByHash/<br> a record in JSON format (also using the SHA2 256-bit hash of the witness as filename,<br> with .json as filename extension) that contains the meta data.<br> witnessListByProgramHashJSON/<br> For convenient access to all test suites for a certain program, this directory represents<br> a function that maps each program (via its SHA2 256-bit hash) to a set of test suites<br> (JSON records for test suites as described above) that the test tools have produced<br> for that program. For each program for which test suites exist, the directory contains<br> a JSON file (using the SHA2 256-bit hash of the program as filename, with .json as<br> filename extension) that contains all JSON records for test suites for that program. A similar data structure was used by SV-COMP and is described in the following article:<br> Dirk Beyer. A Data Set of Program Invariants and Error Paths.<br> In Proceedings of the 2019 IEEE/ACM 16th International Conference on Mining Software Repositories<br> (MSR 2019, Montreal, Canada, May 26-27), pages 111-115, 2019. IEEE.<br> https://doi.org/10.1109/MSR.2019.00026 Overview over archives from Test-Comp 2019 that are available at Zenodo: https://doi.org/10.5281/zenodo.3856669 Witness store (containing the generated test suites)<br> https://doi.org/10.5281/zenodo.3856661 Results (XML result files, log files, file mappings, HTML tables)<br> https://doi.org/10.5281/zenodo.3856478 Test tasks, version testcomp19<br> https://doi.org/10.5281/zenodo.2561835 BenchExec, version 1.18 All benchmarks were executed<br> for Test-Comp 2019, https://test-comp.sosy-lab.org/2019/<br> by Dirk Beyer, LMU Munich<br> based on the components<br> git@github.com:sosy-lab/sv-benchmarks.git testcomp19-0-g6a770a9c1<br> git@gitlab.com:sosy-lab/test-comp/bench-defs.git testcomp19-0-g1677027<br> git@github.com:sosy-lab/benchexec.git 1.18-0-gff72868 <br> Feel free to contact me in case of questions:<br> https://www.sosy-lab.org/people/beyer/