forked from tweag/FawltyDeps
-
Notifications
You must be signed in to change notification settings - Fork 0
/
left-pad.toml
29 lines (27 loc) · 1.52 KB
/
left-pad.toml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
[project]
# General information about the 3rd-party project: Its name, why we test it,
# and where to find the relevant tarball, along with its expected checksum.
name = "left-pad"
description = "A simple project with (almost) no imports and no dependencies."
url = "https://files.pythonhosted.org/packages/a0/34/cd668981dc6818d8a39f1185af8113268ddc71d99b0ba4aa8ceee2a123e7/left-pad-0.0.3.tar.gz"
sha256 = "b842b81fcf157ca09b1e0036c5876295fdfd097640aa85d37f988857eec64654"
# The SHA256 checksum above can be found by running `sha256sum` on the
# downloaded tarball. It is used to ensure that we run tests against the
# expected revision of the 3rd-party project.
# Below are our experiments which run FawltyDeps with various options on the
# above (unpacked) tarball. Each table represents an experiment with the
# command-line arguments we pass to FawltyDeps (in `args`, --json is implicitly
# added by test_real_projects), as well as our expectations for what FawltyDeps
# should return in that scenario. These expectations are encoded as lists of
# import/dependency names which we expect to be present in the corresponding
# parts of the JSON: imports, declared_deps, undeclared_deps, and unused_deps.
# All these fields are optional, and the verification will be skipped for
# missing fields.
[experiments.all]
description = "Running FD on the entire left-pad project"
args = []
# When we run FawltyDeps with the above arguments, we expect these results:
imports = ["setuptools"]
declared_deps = []
undeclared_deps = ["setuptools"]
unused_deps = []