Debian Codegraph @

debian/control

raw
1 Source: golang-github-poy-onpar
2 Section: golang
3 Priority: optional
4 Maintainer: Debian Go Packaging Team <[email protected]>
5 Uploaders:
6 Luca Soler <[email protected]>,
7 Rules-Requires-Root: no
8 Build-Depends:
9 debhelper-compat (= 13),
10 dh-sequence-golang,
11 golang-any,
12 golang-github-fatih-color-dev,
13 # golang-sourcehut-nelsam-hel-dev, # Required for tests but not yet packaged in Debian
14 Testsuite: autopkgtest-pkg-go
15 Standards-Version: 4.7.2
16 Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-poy-onpar
17 Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-poy-onpar.git
18 Homepage: https://github.com/poy/onpar
19 XS-Go-Import-Path: github.com/poy/onpar
20
21 Package: golang-github-poy-onpar-dev
22 Architecture: all
23 Multi-Arch: foreign
24 Depends:
25 ${misc:Depends},
26 Description: Parallel testing framework for Go (library)
27 Onpar provides a BDD style of testing, similar to what you might find with
28 something like ginkgo or goconvey. The biggest difference between onpar and its
29 peers is that a BeforeEach function in onpar may return a value, and that value
30 will become the parameter required in child calls to Spec, AfterEach, and
31 BeforeEach.
32 .
33 This allows you to write tests that share memory between BeforeEach, Spec, and
34 AfterEach functions without sharing memory with other tests. When used
35 properly, this makes test pollution nearly impossible and makes it harder to
36 write flaky tests.