golang-check.v1 0.0+git20161208.0.20d25e2-2 source package in Ubuntu

Changelog

golang-check.v1 (0.0+git20161208.0.20d25e2-2) unstable; urgency=medium

  [ Paul Tagliamonte ]
  * Team upload.
  * Remove Built-Using from arch:all -dev package

 -- Michael Hudson-Doyle <email address hidden>  Wed, 27 Sep 2017 08:40:08 -0400

Upload details

Uploaded by:
Debian Go Packaging Team
Uploaded to:
Sid
Original maintainer:
Debian Go Packaging Team
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Bionic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
golang-check.v1_0.0+git20161208.0.20d25e2-2.dsc 2.3 KiB 79813cc418d06e9a4d191b18edf64eb53df95cab3b56eb0d4f29e132c69601bb
golang-check.v1_0.0+git20161208.0.20d25e2.orig.tar.xz 26.4 KiB 4a396c69e002b446ad3f7635744e144b8c121301fe10b2cf878a3e3bdec5467f
golang-check.v1_0.0+git20161208.0.20d25e2-2.debian.tar.xz 4.0 KiB 7ca3dada579e19d74291dd73f9942490d81d145be95557dfd4091f5dee8e15e2

No changes file available.

Binary packages built by this source

golang-check.v1-dev: Transitional package for golang-gopkg-check.v1-dev

 This is a transitional package to ease upgrades to the
 golang-gopkg-check.v1-dev package. It can safely be removed.

golang-gopkg-check.v1-dev: Rich testing extension for Go's testing package

 The Go language provides an internal testing library, named testing, which is
 relatively slim due to the fact that the standard library correctness by
 itself is verified using it. The check package, on the other hand, expects the
 standard library from Go to be working correctly, and builds on it to offer a
 richer testing framework for libraries and applications to use.
 .
 Package "gopkg.in/check.v1" includes features such as:
 .
    - Helpful error reporting to aid on figuring problems out
    - Richer test helpers: assertions which interrupt the test immediately,
      deep multi-type comparisons, string matching, etc
    - Suite-based grouping of tests
    - Fixtures: per suite and/or per test set up and tear down
    - Benchmarks integrated in the suite logic (with fixtures, etc)
    - Management of temporary directories
    - Panic-catching logic, with proper error reporting
    - Proper counting of successes, failures, panics, missed tests, skips, etc
    - Explicit test skipping
    - Support for expected failures
    - Verbosity flag which disables output caching (helpful to debug hanging
      tests, for instance)
    - Multi-line string reporting for more comprehensible failures
    - Inclusion of comments surrounding checks on failure reports
    - Fully tested (it manages to test itself reliably)