Test Suites from Test-Generation Tools (Test-Comp 2020)

<p>This archive contains the test suites that were generated during the<br> 2nd Competition on Software Testing (Test-Comp 2020)<br> <a href="https://test-comp.sosy-lab.org/2020/">https://test-comp.sosy-lab.org/2020/</a></p> <p>The competition was run by Dirk Beyer, LMU Munich, Germany.<br> More information is available in the following article:<br> Dirk Beyer. Second Competition on Software Testing: Test-Comp 2020.<br> In Proceedings of the 23rd International Conference on Fundamental Approaches to Software Engineering<br> (FASE 2020, Dublin, April 28-30), 2020. Springer.<br> <a href="https://doi.org/10.1007/978-3-030-45234-6_25">https://doi.org/10.1007/978-3-030-45234-6_25</a></p> <p>Copyright (C) Dirk Beyer<br> <a href="https://www.sosy-lab.org/people/beyer/">https://www.sosy-lab.org/people/beyer/</a></p> <p>SPDX-License-Identifier: CC-BY-4.0<br> <a href="https://spdx.org/licenses/CC-BY-4.0.html">https://spdx.org/licenses/CC-BY-4.0.html</a></p> <p>&nbsp;</p> <p>Contents:</p> <p>LICENSE.txt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specifies the license<br> README.txt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this file<br> witnessFileByHash/&nbsp; This directory contains test suites (witnesses for coverage).<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Each witness in this directory is stored in a file whose name is the SHA2 256-bit hash<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of its contents followed by the filename extension .zip.<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The format of each test suite is described on the format web page:<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; https://gitlab.com/sosy-lab/software/test-format<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A test suite contains also metadata in order to relate it<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the test problem for which it was produced.<br> witnessInfoByHash/&nbsp; This directory contains for each test suite (witness) in directory witnessFileByHash/<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a record in JSON format (also using the SHA2 256-bit hash of the witness as filename,<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with .json as filename extension) that contains the meta data.<br> witnessListByProgramHashJSON/<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For convenient access to all test suites for a certain program, this directory represents<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a function that maps each program (via its SHA2256-bit hash) to a set of test suites<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (JSON records for test suites as described above) that the test tools have produced<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for that program.&nbsp; For each program for which test suites exist, the directory contains<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a JSON file (using the SHA2 256-bit hash of the program as filename, with .json as<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; filename extension) that contains all JSON records for test suites&nbsp; for that program.</p> <p>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> <a href="https://doi.org/10.1109/MSR.2019.00026">https://doi.org/10.1109/MSR.2019.00026</a></p> <p>&nbsp;</p> <p>Overview over archives from Test-Comp 2020 that are available at Zenodo:</p> <p><a href="https://doi.org/10.5281/zenodo.3678275">https://doi.org/10.5281/zenodo.3678275</a>&nbsp;&nbsp; Witness store (containing the generated test suites)<br> <a href="https://doi.org/10.5281/zenodo.3678264">https://doi.org/10.5281/zenodo.3678264</a>&nbsp;&nbsp; Results (XML result files, log files, file mappings, HTML tables)<br> <a href="https://doi.org/10.5281/zenodo.3678250">https://doi.org/10.5281/zenodo.3678250</a>&nbsp;&nbsp; Test tasks, version testcomp20<br> <a href="https://doi.org/10.5281/zenodo.3574420">https://doi.org/10.5281/zenodo.3574420</a>&nbsp;&nbsp; BenchExec, version 2.5.1</p> <p>All benchmarks were executed<br> for Test-Comp 2020, <a href="https://test-comp.sosy-lab.org/2020/">https://test-comp.sosy-lab.org/2020/</a><br> by Dirk Beyer, LMU Munich<br> based on the components<br> git@github.com:sosy-lab/sv-benchmarks.git&nbsp; testcomp20-0-gd6cd3e5dd4<br> git@gitlab.com:sosy-lab/test-comp/bench-defs.git&nbsp; testcomp19-84-gac76836<br> git@github.com:sosy-lab/benchexec.git&nbsp; 2.5.1-0-gffad635</p> <p><br> Feel free to contact me in case of questions:<br> <a href="https://www.sosy-lab.org/people/beyer/">https://www.sosy-lab.org/people/beyer/</a></p>