This README.txt file was generated on 20200119 by Chu-Pan Wong # # General instructions for completing README: # For sections that are non-applicable, mark as N/A (do not delete any sections). # Please leave all commented sections in README (do not delete any text). # ------------------- GENERAL INFORMATION ------------------- 1. Title of Dataset: Efficiently Finding Higher-Order Mutants # # Authors: Include contact information for at least the # first author and corresponding author (if not the same), # specifically email address, phone number (optional, but preferred), and institution. # Contact information for all authors is preferred. # 2. Author Information First Author Contact Information Name: Chu-Pan Wong Institution: Carnegie Mellon University Address: 5000 Forbes Avenue, Pittsburgh, Pennsylvania, USA, 15213 Email: chupanw@cs.cmu.edu Phone Number: Corresponding Author Contact Information Name: Leo Chen Institution: Carnegie Mellon University Address: 5000 Forbes Avenue, Pittsburgh, Pennsylvania, USA, 15213 Email: leochen@cmu.edu Phone Number: Author Contact Information (if applicable) Name: Jens Meinicke Institution: Carnegie Mellon University Address: 5000 Forbes Avenue, Pittsburgh, Pennsylvania, USA, 15213 Email: Phone Number: --------------------- DATA & FILE OVERVIEW --------------------- # # Directory of Files in Dataset: List and define the different # files included in the dataset. This serves as its table of # contents. # Directory of Files: A. Filename: SSHOM-Finder.zip Short description: Main executable artifacts for reproducing our results. It contains two jars and a README that documents how to use the jars. B. Filename: Results.zip Short description: Raw data we used at the time of writing our paper. These results were obtained by running SSHOM-Finder.zip. We share the raw data here for easy reference. C. Filename: VariationalExecution.zip Short description: Jars for running variational execution to generate BDDs. The jars in SSHOM-Finder.zip already contain pre-computed BDDs. Additional Notes on File Relationships, Context, or Content (for example, if a user wants to reuse and/or cite your data, what information would you want them to know?): Instructions for how to use our tools (i.e.o, SSHOM-Finder.jar and VariationalExecution.zip) are available in separate zip files. Heuristic-based search strategies involve certain undeterministic components (e.g., mutation and crossover in the genetic algorithm of search_gen) and thus results might be different in a different run. In our evaluation, we repeat experiments when needed to mitigate this issue and publish the raw data we obtained for reference (Results.zip). # # File Naming Convention: Define your File Naming Convention # (FNC), the framework used for naming your files systematically # to describe what they contain, which could be combined with the # Directory of Files. # File Naming Convention: In Results.zip, files are named in the format of __.txt. # # Data Description: A data description, dictionary, or codebook # defines the variables and abbreviations used in a dataset. This # information can be included in the README file, in a separate # file, or as part of the data file. If it is in a separate file # or in the data file, explain where this information is located # and ensure that it is accessible without specialized software. # (We recommend using plain text files or tabular plain text CSV # files exported from spreadsheet software.) # ----------------------------------------- DATA DESCRIPTION FOR: [FILENAME] ----------------------------------------- 1. Number of variables: 2. Number of cases/rows: 3. Missing data codes: Code/symbol Definition Code/symbol Definition 4. Variable List # # Example. Name: Wall Type # Description: The type of materials present in the wall type for housing surveys collected in the project. # 1 = Brick # 2 = Concrete blocks # 3 = Clay # 4 = Steel panels A. Name: Description: Value labels if appropriate B. Name: Description: Value labels if appropriate -------------------------- METHODOLOGICAL INFORMATION -------------------------- # # Software: If specialized software(s) generated your data or # are necessary to interpret it, please provide for each (if # applicable): software name, version, system requirements, # and developer. #If you developed the software, please provide (if applicable): #A copy of the software’s binary executable compatible with the system requirements described above. #A source snapshot or distribution if the source code is not stored in a publicly available online repository. #All software source components, including pointers to source(s) for third-party components (if any) 1. Software-specific information: Name: Java SE Development Kit Version: 8u281 System Requirements: see https://www.oracle.com/java/technologies/javase/javase-jdk8-downloads.html Open Source? (Y/N): N (if available and applicable) Executable URL: https://www.oracle.com/java/technologies/javase/javase-jdk8-downloads.html Source Repository URL: N/A Developer: Oracle Product URL: https://www.oracle.com/java/technologies/javase/javase-jdk8-downloads.html Software source components: N/A Name: SSHOM-Finder Version: N/A System Requirements: JDK 1.8 (see above) Open Source? (Y/N): Y (if available and applicable) Executable URL: In SSHOM-Finder.zip Source Repository URL: https://github.com/poosomooso/SSHOM-Search Developer: Leo Chen, Jens Meinicke, Chu-Pan Wong Product URL: https://github.com/poosomooso/SSHOM-Search Software source components: N/A Additional Notes(such as, will this software not run on certain operating systems?): Running our tools on Windows machines has not been tested and might have issues related to file paths and EOL because of the subject systems we use. # # Equipment: If specialized equipment generated your data, # please provide for each (if applicable): equipment name, # manufacturer, model, and calibration information. Be sure # to include specialized file format information in the data # dictionary. # 2. Equipment-specific information: N/A Manufacturer: Model: (if applicable) Embedded Software / Firmware Name: Embedded Software / Firmware Version: Additional Notes: # # Dates of Data Collection: List the dates and/or times of # data collection. # 3. Date of data collection (single date, range, approximate date) : 2019