From owner-svn-ports-head@freebsd.org Sat Mar 3 07:16:14 2018 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8DFEF4606E; Sat, 3 Mar 2018 07:16:14 +0000 (UTC) (envelope-from ultima@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6839572243; Sat, 3 Mar 2018 07:16:14 +0000 (UTC) (envelope-from ultima@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 617A023191; Sat, 3 Mar 2018 07:16:14 +0000 (UTC) (envelope-from ultima@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w237GE7r029180; Sat, 3 Mar 2018 07:16:14 GMT (envelope-from ultima@FreeBSD.org) Received: (from ultima@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w237GDCf029176; Sat, 3 Mar 2018 07:16:13 GMT (envelope-from ultima@FreeBSD.org) Message-Id: <201803030716.w237GDCf029176@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ultima set sender to ultima@FreeBSD.org using -f From: Richard Gallamore Date: Sat, 3 Mar 2018 07:16:13 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r463464 - in head/textproc: . py-pyhamcrest X-SVN-Group: ports-head X-SVN-Commit-Author: ultima X-SVN-Commit-Paths: in head/textproc: . py-pyhamcrest X-SVN-Commit-Revision: 463464 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 07:16:15 -0000 Author: ultima Date: Sat Mar 3 07:16:13 2018 New Revision: 463464 URL: https://svnweb.freebsd.org/changeset/ports/463464 Log: PyHamcrest is a framework for writing matcher objects, allowing you to declaratively define "match" rules. There are a number of situations where matchers are invaluable, such as UI validation, or data filtering, but it is in the area of writing flexible tests that matchers are most commonly used. This tutorial shows you how to use PyHamcrest for unit testing. When writing tests it is sometimes difficult to get the balance right between overspecifying the test (and making it brittle to changes), and not specifying enough (making the test less valuable since it continues to pass even when the thing being tested is broken). Having a tool that allows you to pick out precisely the aspect under test and describe the values it should have, to a controlled level of precision, helps greatly in writing tests that are "just right." Such tests fail when the behavior of the aspect under test deviates from the expected behavior, yet continue to pass when minor, unrelated changes to the behaviour are made. WWW: https://github.com/hamcrest/PyHamcrest Differential Revision: https://reviews.freebsd.org/D13520 Added: head/textproc/py-pyhamcrest/ head/textproc/py-pyhamcrest/Makefile (contents, props changed) head/textproc/py-pyhamcrest/distinfo (contents, props changed) head/textproc/py-pyhamcrest/pkg-descr (contents, props changed) Modified: head/textproc/Makefile Modified: head/textproc/Makefile ============================================================================== --- head/textproc/Makefile Sat Mar 3 06:50:15 2018 (r463463) +++ head/textproc/Makefile Sat Mar 3 07:16:13 2018 (r463464) @@ -1338,6 +1338,7 @@ SUBDIR += py-pyes SUBDIR += py-pygments SUBDIR += py-pygtail + SUBDIR += py-pyhamcrest SUBDIR += py-pyhwp SUBDIR += py-pyphen SUBDIR += py-pyscss Added: head/textproc/py-pyhamcrest/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/textproc/py-pyhamcrest/Makefile Sat Mar 3 07:16:13 2018 (r463464) @@ -0,0 +1,23 @@ +# Created by: Richard Gallamore +# $FreeBSD$ + +PORTNAME= PyHamcrest +DISTVERSION= 1.9.0 +CATEGORIES= textproc python +MASTER_SITES= CHEESESHOP +PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} + +MAINTAINER= ultima@FreeBSD.org +COMMENT= Hamcrest matchers for Python + +LICENSE= BSD3CLAUSE +LICENSE_FILE= ${WRKSRC}/LICENSE.txt + +RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>=1.4:devel/py-six@${FLAVOR} + +USES= python:2.7-3.4 +USE_PYTHON= autoplist distutils + +NO_ARCH= yes + +.include Added: head/textproc/py-pyhamcrest/distinfo ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/textproc/py-pyhamcrest/distinfo Sat Mar 3 07:16:13 2018 (r463464) @@ -0,0 +1,3 @@ +TIMESTAMP = 1513497017 +SHA256 (PyHamcrest-1.9.0.tar.gz) = 8ffaa0a53da57e89de14ced7185ac746227a8894dbd5a3c718bf05ddbd1d56cd +SIZE (PyHamcrest-1.9.0.tar.gz) = 376623 Added: head/textproc/py-pyhamcrest/pkg-descr ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/textproc/py-pyhamcrest/pkg-descr Sat Mar 3 07:16:13 2018 (r463464) @@ -0,0 +1,19 @@ +PyHamcrest is a framework for writing matcher objects, allowing you +to declaratively define "match" rules. There are a number of +situations where matchers are invaluable, such as UI validation, or +data filtering, but it is in the area of writing flexible tests that +matchers are most commonly used. This tutorial shows you how to use +PyHamcrest for unit testing. + +When writing tests it is sometimes difficult to get the balance right +between overspecifying the test (and making it brittle to changes), +and not specifying enough (making the test less valuable since it +continues to pass even when the thing being tested is broken). Having +a tool that allows you to pick out precisely the aspect under test +and describe the values it should have, to a controlled level of +precision, helps greatly in writing tests that are "just right." Such +tests fail when the behavior of the aspect under test deviates from +the expected behavior, yet continue to pass when minor, unrelated +changes to the behaviour are made. + +WWW: https://github.com/hamcrest/PyHamcrest