head	1.2;
access;
symbols;
locks; strict;
comment	@# @;


1.2
date	2016.07.14.20.02.24;	author bsiegert;	state dead;
branches;
next	1.1;
commitid	CfMITqMQd4H2lkez;

1.1
date	2016.07.14.20.01.06;	author bsiegert;	state Exp;
branches;
next	;
commitid	EpA8wNa6GASBkkez;


desc
@@


1.2
log
@Gah, this already exists as devel/go-check. Sorry for the noise.
@
text
@$NetBSD: distinfo,v 1.1 2016/07/14 20:01:06 bsiegert Exp $

SHA1 (check/gocheck-20160125.tar.gz) = 9e9398831e23641805382d78869e34ef25f7ccea
RMD160 (check/gocheck-20160125.tar.gz) = 5a51c89237c36b2bc71d3fa10535b1dab57c3d9e
SHA512 (check/gocheck-20160125.tar.gz) = af0df648c86dab60750e181f7358166fe1e6ed6371e35b5c0c2207bd90e40da16e4a5e5c7fd96d1893ac8c430673b421bf8e2b5b193816f475bd9bc3af4c036e
Size (check/gocheck-20160125.tar.gz) = 30327 bytes
@


1.1
log
@New package, gocheck-20160125.

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.

gocheck works as an extension to the testing package and to the "go
test" runner. That allows keeping all current tests and using
gocheck-based tests right away for new tests without conflicts. The
gocheck API was purposefully made similar to the testing package for a
smooth migration.
@
text
@d1 1
a1 1
$NetBSD$
@