Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
17
datasets available to search
ShareScore release 0.9.0
Dataset results
17 results for “Exploratory Testing”
Supplemental material for: Software System Testing assisted by Large Language Models: An Exploratory Study
<p>This is the supplemental material of the paper titled as “Software System Testing Assisted by Large Language Models: An Exploratory Study” presented at the 36th International Conference on Testing Software and Systems.</p> <p>It contains the raw execution data generated by both models, GPT-4o and GPT-4omini, during the exploratory study. The supplementary material includes the following files:</p> <ul> <li><em>GPT-4ominiRQ1-2ExecutionData.zip</em>: contains the JSON outputs from the OpenAI API for the GPT-4o mini model. Each output is labeled according to the research question number and the corresponding timestamp (for RQ1) or the requested test case (for RQ2), all provided in plain text format.</li> <li><em>GPT-4oRQ1-2ExecutionData.zip</em>: contains the JSON outputs from the OpenAI API for the GPT-4o model. Like the previous file, each output is named in plain text format based on the research question number and timestamp (for RQ1) or the requested test case (for RQ2).</li> </ul> <p>To cite this work: </p> <p>C. Augusto, J. Morán, A. Bertolino, C. de la Riva and J. Tuya, “S<em>oftware System Testing assisted by Large Language Models: An Exploratory Study</em>”, in <em>Testing Software and Systems</em> (pp. 239–255). Springer Nature Switzerland. https://doi.org/10.1007/978-3-031-80889-0_17</p>
Data and Code for the paper "GUI Testing of Android Applications: Investigating the Impact of the Number of Testers on Different Exploratory Testing Strategies"
<p>This package contains data and code to replicate the findings presented in our paper titled "<em>GUI Testing of Android Applications: Investigating the Impact of the Number of Testers on Different Exploratory Testing Strategies</em>".</p> <p><strong>Abstract</strong></p> <p>Graphical User Interface (GUI) testing plays a pivotal role in ensuring the quality and functionality of mobile apps. In this context, Exploratory Testing (ET), a distinctive methodology in which individual testers pursue a creative, and experience-based approach to test design, is often used as an alternative or in addition to traditional scripted testing. Managing the exploratory testing process is a challenging task, that can easily result either in wasteful spending or in inadequate software quality, due to the relative unpredictability of exploratory testing activities, which depend on the skills and abilities of individual testers. A number of works have investigated the<br> diversity of testers’ performance when using ET strategies, often in a crowdtesting setting. These works, however, investigated ET effectiveness in detecting bugs, and not in scenarios in which the goal is to generate a re-executable test suite, as well. Moreover, less work has been conducted on evaluating the impact of adopting different exploratory testing strategies. As a first step towards filling this gap in the literature, in this work we conduct an empirical evaluation involving four open-source Android apps and twenty masters students, that we believe can be representative of practitioners partaking in exploratory testing activities. The students were asked to generate test suites for the apps using a Capture and Replay tool and different exploratory testing strategies. We then compare the effectiveness, in terms of aggregate code coverage, that different-sized groups of students using different exploratory testing strategies may achieve. Results provide deeper insights into code coverage dynamics to project managers interested in using exploratory approaches to test simple Android apps, on which they can make more informed decisions.</p> <p> </p> <p><strong>Contents and Instructions</strong></p> <p>This package contains:</p> <ul> <li><strong>apps-under-test.zip</strong> A zip archive containing the source code of the four Android applications we considered in our study, namely MunchLife, TippyTipper, Trolly, and SimplyDo.</li> <li><strong>apps-under-test-instrumented.zip</strong> A zip archive containing the instrumented source code of the four Android applications we used to compute branch coverage.</li> <li><strong>students-test-suites.zip</strong> A zip archive containing the test suites developed by the students using Uninformed Exploratory Testing (referred to as "Black Box" in the subdirectories) and Informed Exploratory Testing (referred to as "White Box" in the subdirectories). This also includes coverage reports.</li> <li><strong>compute-coverage-unions.zip </strong>A zip archive containing Python scripts we developed to compute the aggregate LOC coverage of all possible subsets of students. The scripts have been tested on MS Windows. To compute the LOC coverage achieved by any possible subsets of testers using IET and UET strategies, run the <em>analysisAndReport.py</em> script. To compute the LOC coverage achieved by mixed crowds in which some testers use a U+IET approach and others use a UET approach, run the <em>analysisAndReport_UET_IET_combinations_emma.py</em> script.</li> <li><strong>branch-coverage-computation.zip </strong>A zip archive containing Python scripts we developed to compute the aggregate branch coverage of all considered subsets of students. The scripts have been tested on MS Windows. To compute the branch coverage achieved by any possible subsets of testers using UET and I+UET strategies, run the <em>branch_coverage_analysis.py</em> script. To compute the code coverage achieved by mixed crowds in which some testers use a U+IET approach and others use a UET approach, run the <em>mixed_branch_coverage_analysis.py</em> script.</li> <li><strong>data-analysis-scripts.zip</strong> A zip archive containing R scripts to merge and manipulate coverage data, to carry out statistical analysis and draw plots. All data concerning RQ1 and RQ2 is available as a ready-to-use R data frame in the <em>./data/all_coverage_data.rds</em> file. All data concerning RQ3 is available in the <em>./data/all_mixed_coverage_data.rds </em>file.</li> </ul>
Classifying the Correctness of Generated White-Box Tests: An Exploratory Study
<p>White-box test generator tools rely only on the code under test to select test inputs, and capture the implementation's output as assertions. If there is a fault in the implementation, it could get encoded in the generated tests. Tool evaluations usually measure fault-detection capability using the number of such fault-encoding tests. However, these faults are only detected, if the developer can recognize that the encoded behavior is faulty. We designed an exploratory study to investigate how developers perform in classifying generated white-box test as faulty or correct. We carried out the study in a laboratory setting with 54 graduate students. The tests were generated for two open-source projects with the help of the IntelliTest tool. The performance of the participants were analyzed using binary classification metrics and by coding their observed activities. The results showed that participants incorrectly classified a large number of both fault-encoding and correct tests (with median misclassification rate 33% and 25% respectively). Thus the real fault-detection capability of test generators could be much lower than typically reported, and we suggest to take this human factor into account when evaluating generated white-box tests.<br> <br> This material contains the dataset and the recorded videos of the study.</p>
How are Solidity smart contracts tested in open source projects? An exploratory study
<p>A dataset with 139 Github Solidity projects containing information about testing files, testing tools, and testnets that each project uses.</p>
Classifying Generated White-Box Tests: An Exploratory Study
<p>The data and analysis scripts for our paper entitled Classifying Generated White-Box Tests: An Exploratory Study</p>
An Exploratory Study on the Usage and Readability of Messages Within Assertion Methods of Test Cases
<p>This is the code and dataset that accompanies the study: "<strong>An Exploratory Study on the Usage and Readability of Messages Within Assertion Methods of Test Cases</strong>." This study has been accepted for publication at the 2023 International Workshop on Natural Language-based Software Engineering.</p> <p><strong><em>Following is the abstract of the study:</em></strong></p> <p>Unit testing is a vital part of the software development process and involves developers writing code to verify or assert production code. Furthermore, to help comprehend the test case and troubleshoot issues, developers have the option to provide a message that explains the reason for the assertion failure. In this exploratory empirical study, we examine the characteristics of assertion messages contained in the test methods in 20 open-source Java systems. Our findings show that while developers rarely utilize the option of supplying a message, those who do, either compose it of only string literals, identifiers, or a combination of both types. Using standard English readability measuring techniques, we observe that a beginner's knowledge of English is required to understand messages containing only identifiers, while a 4th-grade education level is required to understand messages composed of string literals. We also discuss shortcomings with using such readability measuring techniques and common anti-patterns in assert message construction. We envision our results incorporated into code quality tools that appraise the understandability of assertion messages. </p>
Online Appendix for "An Exploratory Study of the State of Practice of Performance Testing in Java-Based Open Source Projects"
<p>Here we collect some raw data and additional material to the paper <em>"An Exploratory Study of the State of Practice of Performance Testing in Java-Based Open Source Projects"</em>, by Philipp Leitner and Cor-Paul Bezemer.</p>
An Exploratory Study on Code Quality, Testing, Data Accuracy, and Practical Use Cases of IoT Wearables
<p>Data used in IoT Wearable Study</p>
FIGURE 1 in Making biodiversity discovery more efficient: An exploratory test using Mexican birds
FIGURE 1. Two example predictions of possible distributions of 'unknown' species (i.e., restricted range and poorly known species used here to simulate unknown species) based on ecological characteristics of more widely distributed congener species. The dark outline indicates the 100 km buffer around known occurrences of the less well-known species
Exploratory Study of Precise Therapy for Advanced Tumor Patients With Malignant Hydrothorax or Ascites by Using PTC Drug Sensitivity Testing
ClinicalTrials.gov study NCT06413212. IPD Sharing: Not stated. Countries: 1. Publications: 14.
Usability test used for inspiraconciencia exploratory tool analysis
<p>This dataset contains the analysis and questionnaire of the material collected during the workshops conducted educators to evaluate the usuability of the exploratory tool inspiraconciencia. It is part of a study by Calvera-Isabal M. (to be published). </p> <p>This work has been funded by PID2020-112584RB-C33 funded by MCIN/AEI/10.13039/501100011033, the CS Track project, EU Horizon 2020 programme [grant agreement No 872522] and H2O Learn project PID2020-112584RB-C33 funded by MCIN/ AEI / 10.13039/501100011033.</p>
An Exploratory Psoriasis Plaque Test Study With Different Dose Combinations of Calcipotriol Plus Betamethasone Dipropionate in the Daivobet® Gel Vehicle in Psoriasis Vulgaris
ClinicalTrials.gov study NCT01837576. IPD Sharing: NO. Countries: 1. Publications: 0.
Exploratory Analysis of Enhanced Liver Function (ELF) Test to Detect Early Fatty Liver in High Risk Population
ClinicalTrials.gov study NCT06225193. IPD Sharing: NO. Countries: 1. Publications: 0.
Exploratory Study of the Relevance of a Blood Test in the Management of Patients in the Context of Colorectal Cancer Screening
ClinicalTrials.gov study NCT04767568. IPD Sharing: Not stated. Countries: 1. Publications: 0.
An Exploratory Psoriasis Plaque Test Study With LEO 29102 Plus Calcipotriol, Ointment, in Psoriasis Vulgaris
ClinicalTrials.gov study NCT01466478. IPD Sharing: NO. Countries: 1. Publications: 0.
Exploratory Study to Investigate Efficacy of LAS41004 in a Psoriasis Plaque Test
ClinicalTrials.gov study NCT01360944. IPD Sharing: Not stated. Countries: 1. Publications: 0.
Efficacy of a 14-Day Bismuth-Containing Quadruple Therapy Guided by Drug Susceptibility Testing in Patients with Extremely Refractory Helicobacter Pylori Infection: an Exploratory Study
ClinicalTrials.gov study NCT06731023. IPD Sharing: UNDECIDED. Countries: 1. Publications: 0.
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.