CoChat

DocTer: documentation-guided fuzzing for testing deep learning API functions

Open access
Xie, Danning, Li, Yitong, Kim, Mijung, Pham, Hung Viet, Tan, Lin, Zhang, Xiangyu, Godfrey, Michael W. · 2022 · Proceedings of the 31st ACM SIGSOFT International Symposium on Software Testing and Analysis

The DOI matches its Crossref record; 53 of the 54 references it cites were found in a registry or an index.

Abstract

Input constraints are useful for many software development tasks. For example, input constraints of a function enable the generation of valid inputs, i.e., inputs that follow these constraints, to test the function deeper. API functions of deep learning (DL) libraries have DL-specific input constraints, which are described informally in the free-form API documentation. Existing constraint-extraction techniques are ineffective for extracting DL-specific input constraints.

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/3533767.3534220

Cites

53 of 53 references verified0 citation errors · 0 not checkable

Statistics

Figures

Image 1
CC-BY · From the PDF
Figure 2 Overview of DocTer. p T , p S , and p D are the abstract constraints representing the data type , data structure , and number of dimensions of parameter p , respectively. Detailed constraint formats are explained in Section 2.2.
Figure 2 Overview of DocTer. p T , p S , and p D are the abstract constraints representing the data type , data structure , and number of dimensions of parameter p , respectively. Detailed constraint formats are explained in Section 2.2.CC-BY · From the PDF
Table 1: Rule examples and the extracted constraints from TensorFlow, PyTorch, and MXNet
Table 1: Rule examples and the extracted constraints from TensorFlow, PyTorch, and MXNetCC-BY · From the PDF
Figure 3 Ratio of passing inputs
Figure 3 Ratio of passing inputsCC-BY · From the PDF

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 53 references

Cited by

Metadata

Authors
Xie, D., Li, Y., Kim, M., Pham, H. V., Tan, L., Zhang, X., & Godfrey, M. W.
Affiliations
  • Purdue University West Lafayette (US)
  • University of Waterloo (CA)
  • Ulsan National Institute of Science and Technology (KR)
Venue
Proceedings of the 31st ACM SIGSOFT International Symposium on Software Testing and Analysis
Publisher
ACM
Published
2022-07-18
Pages
176-188
OpenAlex
W4285490440
Cited by
81
References
54
Citations by year
2026: 14 · 2025: 27 · 2024: 23 · 2023: 15 · 2022: 2
FWCI
12.63
Type
conference paper
Language
en
Open access
Locations
  • ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) (publishedVersion, cc-by)
  • arXiv (Cornell University) (submittedVersion)
  • Scholarworks@UNIST (Ulsan National Institute of Science and Technology) (submittedVersion)
  • arXiv (Cornell University)
Funders
National Science Foundation (1901242)
Topics
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
deep learning libraries, API testing, input constraints, constraint extraction, API documentation, software testing

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.