[yt-svn] commit/yt: 4 new changesets
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Wed Mar 23 13:53:39 PDT 2016
4 new commits in yt:
http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gDx2lD2xxoS9E7MwXb2SMR-2BXcTD42YocdnOFkyGBVHOUuRLxxpJqZwddiNDEdAyBlHQ7CFGIAlYrhBOxoc5nH5g-3D_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B9KrhS0daq6IxayllI-2FIilfBBNAwyswcMx7C7dgYFceBleS9VgY200h2LEDIrPa3CkTJZPZgUub-2BvLD21oOGeVu69ltKXRKJ-2Fp5Ddee-2FK-2Bx3EdBW-2FjvzpU4jtYlgHGMFZIwpxdQ0FfJJfVS4eqO5Xd4-3D
Changeset: 633c068fab48
Branch: yt
User: xarthisius
Date: 2016-03-21 15:27:25+00:00
Summary: Update answer testing docs
Affected #: 1 file
diff -r e870ed5eb0e897bbaf4be9da9c78dbf0e0fcdd42 -r 633c068fab48d25b06f07e8f9c3ccdfc5a08defc doc/source/developing/testing.rst
--- a/doc/source/developing/testing.rst
+++ b/doc/source/developing/testing.rst
@@ -476,3 +476,82 @@
test is more useful if you are finding yourself writing a ton of boilerplate
code to get your image comparison test working. The ``GenericImageTest`` is
more useful if you only need to do a one-off image comparison test.
+
+Enabling Answer Tests on Jenkins
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Before any code is added to or modified in the yt codebase, each incoming
+changeset is run against all available unit and answer tests on our `continuous
+integration server <http://link.bitbucket.org/wf/click?upn=RhcBcfh3o3OexLylRqBSSeffThKl5wGEWpBk35gYMt-2F1i3i7Cdjz-2BA93imiBaXY4_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B5Zkh8ToVvuoB1OTCRZ2Ns6MSttyyt-2BdWgWu9HDlU5vovzZ26nRuAF6JJBTak-2BqrZg7Sf-2FSuJLM0M-2B67sAy5CHzm40rHpyjYtQG97iwuX3jaic0SXiTGzXP4PvmwSeYWU08xjHhiYyn-2F-2Bg4BujITtws-3D>`_. While unit tests are
+autodiscovered by `nose <http://link.bitbucket.org/wf/click?upn=-2F-2B5EjSCIdHksviJD1NH3VT33nG2WRIz72zZynHbnfBV84blL2pz26ULzJCzH4d2r_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B4qhrPY5X1x0AT4PAqwX1sronN25Hi5JgPvsIR6T0TwYXO-2FKKwQF2-2FpeChgh2bhHSQDaZ8R-2F-2F60Lru5vNyhIavDnIqfeJFZpe0yXNzgdLax69cQjn2ZbhW0uzRbxvfut3J97cIJbziTmzS1cB9QeoSE-3D>`_ itself,
+answer tests require definition of which set of tests constitute to a given
+answer. Configuration for the integration server is stored in
+*tests/tests_2.7.yaml* in the main yt repository:
+
+.. code-block:: yaml
+
+ answer_tests:
+ local_artio_270:
+ - yt/frontends/artio/tests/test_outputs.py
+ # ...
+ other_tests:
+ unittests:
+ - '-v'
+ - '-s'
+
+Each element under *answer_tests* defines answer name (*local_artio_270* in above
+snippet) and specifies a list of files/classes/methods that will be validated
+(*yt/frontends/artio/tests/test_outputs.py* in above snippet). On the testing
+server it is translated to:
+
+.. code-block:: bash
+
+ $ nosetests --with-answer-testing --local --local-dir ... --answer-big-data \
+ --answer-name=local_artio_270 \
+ yt/frontends/artio/tests/test_outputs.py
+
+If the answer doesn't exist on the server yet, ``nosetests`` is run twice and
+during first pass ``--answer-store`` is added to the commandline.
+
+Updating Answers
+~~~~~~~~~~~~~~~~
+
+In order to regenerate answers for a particular set of tests it is sufficient to
+change the answer name in *tests/tests_2.7.yaml* e.g.:
+
+.. code-block:: diff
+
+ --- a/tests/tests_2.7.yaml
+ +++ b/tests/tests_2.7.yaml
+ @@ -25,7 +25,7 @@
+ - yt/analysis_modules/halo_finding/tests/test_rockstar.py
+ - yt/frontends/owls_subfind/tests/test_outputs.py
+
+ - local_owls_270:
+ + local_owls_271:
+ - yt/frontends/owls/tests/test_outputs.py
+
+ local_pw_270:
+
+would regenerate answers for OWLS frontend.
+
+Adding New Answer Tests
+~~~~~~~~~~~~~~~~~~~~~~~
+
+In order to add new answer with a set of test it is sufficient to extend
+*answer_tests* list in *tests/tests_2.7.yaml* e.g.:
+
+.. code-block:: diff
+
+ --- a/tests/tests_2.7.yaml
+ +++ b/tests/tests_2.7.yaml
+ @@ -60,6 +60,10 @@
+ - yt/analysis_modules/absorption_spectrum/tests/test_absorption_spectrum.py:test_absorption_spectrum_non_cosmo
+ - yt/analysis_modules/absorption_spectrum/tests/test_absorption_spectrum.py:test_absorption_spectrum_cosmo
+
+ + local_gdf_270:
+ + - yt/frontends/gdf/tests/test_outputs.py
+ +
+ +
+ other_tests:
+ unittests:
+
http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gDx2lD2xxoS9E7MwXb2SMR-2BXcTD42YocdnOFkyGBVHOUZhHyskdphV6bO9dqH4cBhGHQbhCCSKYtdWHsdNDjmqM-3D_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B-2F-2BVu7cNvFUGMEdZt2Fbl9pfUtrkR1foinyXtXTSBLsu131o9x3Ksxjw0c1C9RbJ5JvxNg9et-2Bn-2BDPJqeEf8DQ6tyd-2BrVoxx6ArAIbaPeA1b3yVxG-2Fs33XPUkQeiaQKJQKuPCDuibo3kO-2F8OhpgPEXY-3D
Changeset: e51d92788dd7
Branch: yt
User: xarthisius
Date: 2016-03-23 19:08:54+00:00
Summary: Fix Jenkins address. Thanks to Miguel de Val-Borro for pointing it out
Affected #: 1 file
diff -r 633c068fab48d25b06f07e8f9c3ccdfc5a08defc -r e51d92788dd7853d370d9327a97e4266369f7a9a doc/source/developing/testing.rst
--- a/doc/source/developing/testing.rst
+++ b/doc/source/developing/testing.rst
@@ -19,7 +19,7 @@
checking in any code that breaks existing functionality. To further this goal,
an automatic buildbot runs the test suite after each code commit to confirm
that yt hasn't broken recently. To supplement this effort, we also maintain a
-`continuous integration server <http://link.bitbucket.org/wf/click?upn=RhcBcfh3o3OexLylRqBSSeffThKl5wGEWpBk35gYMt-2F1i3i7Cdjz-2BA93imiBaXY4_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B4PNdwH7bY4rdWHXaHY3fBIUcxkZuxKVTLNXcH-2F4QaGbIiNuIKvolSFFKCcvoC1g9ujcaJ4BpEM-2FPPqnHLLjSApNk-2BufoIRn3VX-2F4Uzzg2xnVIpq-2F8M67Xwi3PID2-2FmQP75ePEa0FAmtghtLI0lqmqA-3D>`_ that runs the
+`continuous integration server <http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gEifL6SlWCUOo2iin058pvnChi95ByN0SZ4ANMKlVDue_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B-2BAhDpWrhZYfbXsdFh8wqg5ckQw5iZOZwmo4U9FQ5-2FsuCNKuytLimSg32dEN5CE5KYUx1gTANIL2zIDn0O3Jcm4hpeGH4jy53P0mJQSP1DLRwQi5NcD3yTa7Bb2J5UimIRPbQm4wO6KXoFJDEvo2nNI-3D>`_ that runs the
tests with each commit to the yt version control repository.
.. _unit_testing:
http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gDx2lD2xxoS9E7MwXb2SMR-2BXcTD42YocdnOFkyGBVHOUa6vKLsojPadNoi89MxtaSYdmbLrlfkDuFyaNWp2jDL4-3D_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B2upYv5uWZccRElbmh9m-2FJ4h0tIzo0vH7VNn93ARqUqeCSdPXxPCynLXF3jiLZyTFsuUTEvc-2BkBYD0H2F0cYVUC2OLJtQajLPldCkEvJMp1kTr0Qq31Wrcxy54ZPCCZR8GxE2n0US-2Bth9ajQo0p4o54-3D
Changeset: 7e31fae35ec2
Branch: yt
User: xarthisius
Date: 2016-03-23 19:10:08+00:00
Summary: Update 'Adding New Answer Tests' per Andrew Myers comment
Affected #: 1 file
diff -r e51d92788dd7853d370d9327a97e4266369f7a9a -r 7e31fae35ec2ba6fd9139175098591acc0b927ca doc/source/developing/testing.rst
--- a/doc/source/developing/testing.rst
+++ b/doc/source/developing/testing.rst
@@ -537,7 +537,7 @@
Adding New Answer Tests
~~~~~~~~~~~~~~~~~~~~~~~
-In order to add new answer with a set of test it is sufficient to extend
+In order to add a new set of answer tests, it is sufficient to extend the
*answer_tests* list in *tests/tests_2.7.yaml* e.g.:
.. code-block:: diff
http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gDx2lD2xxoS9E7MwXb2SMR-2BXcTD42YocdnOFkyGBVHOU6E6PJ1U3Xk7rLdXLrUtxz03bcGaDU9wCLVfXZlT-2F-2BV0-3D_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B4WgoJR-2BcQvglAdJsz9go9GW18yKMV0WtDNrI7jLChtiD4NwGvrzv0nYlZ2-2FvkeuofQQI3UvlvLqc-2Fe8aM-2BiaEXO2mRFBl8c7ublQ9jmPb5MWk8GIsBwS5SUx5jyN-2F5PUk7w9FoWYhj-2BbW-2B0HJWQTJY-3D
Changeset: ee78f27e30fb
Branch: yt
User: ngoldbaum
Date: 2016-03-23 20:53:30+00:00
Summary: Merged in xarthisius/yt (pull request #2058)
Update answer testing docs
Affected #: 1 file
diff -r 7538e9cb964c701a9bef8dcb3a788119997b97a8 -r ee78f27e30fbc234af0d10107fc4022f5d42d1d9 doc/source/developing/testing.rst
--- a/doc/source/developing/testing.rst
+++ b/doc/source/developing/testing.rst
@@ -19,7 +19,7 @@
checking in any code that breaks existing functionality. To further this goal,
an automatic buildbot runs the test suite after each code commit to confirm
that yt hasn't broken recently. To supplement this effort, we also maintain a
-`continuous integration server <http://link.bitbucket.org/wf/click?upn=RhcBcfh3o3OexLylRqBSSeffThKl5wGEWpBk35gYMt-2F1i3i7Cdjz-2BA93imiBaXY4_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B-2BHFDIbcG6aiZmuLcpFG5iAgBORJa2L47K28a3Ovjx7tqfSx-2BEqRhNHUC8mpzc9MnDfwbh8ygWm1RJXQTCBwfwbTvFH-2FH-2BP5RvmERqFGJqsDELFi4Il8GypKPnfrZlWohXWcuTDeTqdZ3O3DVibIlJM-3D>`_ that runs the
+`continuous integration server <http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gEifL6SlWCUOo2iin058pvnChi95ByN0SZ4ANMKlVDue_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B1hQHgqojHDa17L34ixmLaECVGDD8TMymybYeWOaNyLS3wdU0Fqp2kctuXXPTULoTN9n-2FQThsFLMUaUJfunrk2aetui9alTKGYDVkpA6G9cwYDkkNZ0df7K3pV1CpZnYLebwem9VVWTfCdycG4H46rs-3D>`_ that runs the
tests with each commit to the yt version control repository.
.. _unit_testing:
@@ -476,3 +476,82 @@
test is more useful if you are finding yourself writing a ton of boilerplate
code to get your image comparison test working. The ``GenericImageTest`` is
more useful if you only need to do a one-off image comparison test.
+
+Enabling Answer Tests on Jenkins
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Before any code is added to or modified in the yt codebase, each incoming
+changeset is run against all available unit and answer tests on our `continuous
+integration server <http://link.bitbucket.org/wf/click?upn=RhcBcfh3o3OexLylRqBSSeffThKl5wGEWpBk35gYMt-2F1i3i7Cdjz-2BA93imiBaXY4_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B2GXAeaQ3wtCCAWcSCF0-2F-2BJAck5xCP8zlsVMQRVMj3qtcOffksdUNpT76XpmpT0s7ukcoQjPyLtnfWwm3ZZFa9xA1VfOFs7sKMv8suWixdLBgH9n1EYh38x0neClssrPiKAu8Wk5UY3pXciHKOWd0e4-3D>`_. While unit tests are
+autodiscovered by `nose <http://link.bitbucket.org/wf/click?upn=-2F-2B5EjSCIdHksviJD1NH3VT33nG2WRIz72zZynHbnfBV84blL2pz26ULzJCzH4d2r_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B8HNXqYjKrYQDrxhDErIEV24tMINjZQBxrFWN8cDURc4KSER4TrKIGRNE-2F-2FGmtXX5EcHRF9EYckYGLw2nuwK1uyXUfUOXIwkJ56yoq973YM1Mey6ClCH5gPbX-2BK-2BAYd9j5CTmJYx2W62Vcfa8weTUZM-3D>`_ itself,
+answer tests require definition of which set of tests constitute to a given
+answer. Configuration for the integration server is stored in
+*tests/tests_2.7.yaml* in the main yt repository:
+
+.. code-block:: yaml
+
+ answer_tests:
+ local_artio_270:
+ - yt/frontends/artio/tests/test_outputs.py
+ # ...
+ other_tests:
+ unittests:
+ - '-v'
+ - '-s'
+
+Each element under *answer_tests* defines answer name (*local_artio_270* in above
+snippet) and specifies a list of files/classes/methods that will be validated
+(*yt/frontends/artio/tests/test_outputs.py* in above snippet). On the testing
+server it is translated to:
+
+.. code-block:: bash
+
+ $ nosetests --with-answer-testing --local --local-dir ... --answer-big-data \
+ --answer-name=local_artio_270 \
+ yt/frontends/artio/tests/test_outputs.py
+
+If the answer doesn't exist on the server yet, ``nosetests`` is run twice and
+during first pass ``--answer-store`` is added to the commandline.
+
+Updating Answers
+~~~~~~~~~~~~~~~~
+
+In order to regenerate answers for a particular set of tests it is sufficient to
+change the answer name in *tests/tests_2.7.yaml* e.g.:
+
+.. code-block:: diff
+
+ --- a/tests/tests_2.7.yaml
+ +++ b/tests/tests_2.7.yaml
+ @@ -25,7 +25,7 @@
+ - yt/analysis_modules/halo_finding/tests/test_rockstar.py
+ - yt/frontends/owls_subfind/tests/test_outputs.py
+
+ - local_owls_270:
+ + local_owls_271:
+ - yt/frontends/owls/tests/test_outputs.py
+
+ local_pw_270:
+
+would regenerate answers for OWLS frontend.
+
+Adding New Answer Tests
+~~~~~~~~~~~~~~~~~~~~~~~
+
+In order to add a new set of answer tests, it is sufficient to extend the
+*answer_tests* list in *tests/tests_2.7.yaml* e.g.:
+
+.. code-block:: diff
+
+ --- a/tests/tests_2.7.yaml
+ +++ b/tests/tests_2.7.yaml
+ @@ -60,6 +60,10 @@
+ - yt/analysis_modules/absorption_spectrum/tests/test_absorption_spectrum.py:test_absorption_spectrum_non_cosmo
+ - yt/analysis_modules/absorption_spectrum/tests/test_absorption_spectrum.py:test_absorption_spectrum_cosmo
+
+ + local_gdf_270:
+ + - yt/frontends/gdf/tests/test_outputs.py
+ +
+ +
+ other_tests:
+ unittests:
+
Repository URL: http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gDx2lD2xxoS9E7MwXb2SMR-2BI0v8SbQq-2B8-2FZaaHaJT85r_ll4ctv0L-2ByeRZFC1LslHcg6aJmnQ70VruLbmeLQr27ATNzSirptvMMLopshCx7o1z04gaIhTTWVN0eoa-2FO85-2B7NZCvgwJWySO-2BOLJ58MXDszmBHB9Fgv3nHheR7ryNa9tARnuUMZIGQ93sLZAnAmcNWngD3S-2FPi4y-2BL9nF3d12TvjRu6eXL7H8uCOX-2FKEFSWBqGs-2FtrorRR8Mju4FoBxcIhVH5mWCFGZ5C770kH-2Boa8-3D
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-svn-spacepope.org/attachments/20160323/3df41d49/attachment.html>
More information about the yt-svn
mailing list