File: control

package info (click to toggle)
pytest-golden 1.0.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 216 kB
  • sloc: python: 412; makefile: 2
file content (46 lines) | stat: -rw-r--r-- 1,913 bytes parent folder | download
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
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Source: pytest-golden
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Uploaders:
 Edward Betts <edward@4angle.com>,
Section: python
Priority: optional
Build-Depends:
 debhelper-compat (= 13),
 dh-sequence-python3,
 pybuild-plugin-pyproject,
 python3-all,
 python3-hatchling,
Build-Depends-Indep:
 python3-atomicwrites <!nocheck>,
 python3-pytest <!nocheck>,
 python3-ruamel.yaml <!nocheck>,
 python3-testfixtures <!nocheck>,
Standards-Version: 4.7.2
Homepage: https://github.com/oprypin/pytest-golden
Vcs-Browser: https://salsa.debian.org/python-team/packages/pytest-golden
Vcs-Git: https://salsa.debian.org/python-team/packages/pytest-golden.git
Testsuite: autopkgtest-pkg-pybuild

Package: python3-pytest-golden
Architecture: all
Depends:
 python3-ruamel.yaml,
 ${misc:Depends},
 ${python3:Depends},
Description: pytest plugin to store expected test outputs in separate data files
 This library is a plugin for pytest that supports golden testing by storing
 expected outputs in YAML data files. Tests can retrieve both input and
 expected output values directly from files, allowing for more maintainable and
 clear assertion data, especially when working with complex results. Instead of
 hardcoding expected values within the test code, data files are used as the
 single source of truth for what should be returned by tests.
 .
 The plugin provides a fixture for conveniently loading and updating these data
 files. When code changes alter the output, a dedicated pytest command-line
 option enables automated population or updating of expected results within the
 corresponding YAML files.
 .
 Files are automatically associated with test functions via decorator-based
 parameters or by explicit file references inside test bodies. Multiple test
 cases can be defined by placing several YAML files under organized directories,
 each representing a variation of input and output data pairs.