| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
With hat: portmgr
Notes:
svn path=/head/; revision=559531
|
| |
|
|
|
|
|
| |
Changes: https://github.com/hamcrest/PyHamcrest/blob/master/CHANGES.txt
Notes:
svn path=/head/; revision=531810
|
| |
|
|
|
|
|
| |
Changes: https://github.com/hamcrest/PyHamcrest/blob/V1.10.1/CHANGES.txt
Notes:
svn path=/head/; revision=523280
|
| |
|
|
|
|
|
|
|
|
| |
* Changed MASTER_SITES to GitHub, GitHub includes test suite
* Added test target and depends, added for testing newer versions of python
PR: 235585
Notes:
svn path=/head/; revision=492931
|
| |
|
|
|
|
|
|
|
|
| |
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight
Notes:
svn path=/head/; revision=472884
|
|
|
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
Notes:
svn path=/head/; revision=463464
|
