TST: move test_utils and adds test fixture classes

Renames zipline.utils.test_utils to zipline.testing

Adds zipline.testing.fixtures.ZiplineTestCase to manage setup and
teardown and adds mixins to define fixtures like an asset finder or
trading calendar.
This commit is contained in:
Joe Jevnik
2016-03-10 15:39:52 -05:00
parent 328d449e60
commit 721dd36116
34 changed files with 727 additions and 146 deletions
+12 -8
View File
@@ -16,20 +16,20 @@ None
Enhancements
~~~~~~~~~~~~
* Added new datasets
:class:`~zipline.pipeline.data.buyback_auth.CashBuybackAuthorizations`
* Added new datasets
:class:`~zipline.pipeline.data.buyback_auth.CashBuybackAuthorizations`
and :class:`~zipline.pipeline.data.buyback_auth.ShareBuybackAuthorizations`
for use in the Pipeline API. These datasets provide an abstract interface for
adding cash and share buyback authorizations data, respectively, to a new
algorithm. pandas-based reference implementations for these datasets can be found in
:mod:`zipline.pipeline.loaders.buyback_auth`, and experimental blaze-based
implementations can be found in
adding cash and share buyback authorizations data, respectively, to a new
algorithm. pandas-based reference implementations for these datasets can be
found in :mod:`zipline.pipeline.loaders.buyback_auth`, and experimental
blaze-based implementations can be found in
:mod:`zipline.pipeline.loaders.blaze.buyback_auth`. (:issue:`1022`).
* Added new built-in factors,
:class:`zipline.pipeline.factors.BusinessDaysSinceCashBuybackAuth` and
:class:`zipline.pipeline.factors.BusinessDaysSinceShareBuybackAuth`. These
factors use the new ``CashBuybackAuthorizations`` and
factors use the new ``CashBuybackAuthorizations`` and
``ShareBuybackAuthorizations`` datasets, respectively. (:issue:`1022`).
@@ -70,4 +70,8 @@ None
Miscellaneous
~~~~~~~~~~~~~
None
* Adds :class:`~zipline.testing.fixtures.ZiplineTestCase` which provides hooks
to consume test fixtures. Fixtures are things like:
:class:`~zipline.testing.fixtures.WithAssetFinder` which will make
``self.asset_finder`` available to your test with some mock data
(:issue:`1042`).