requirements_for_test.txt

-r requirements.txt
pep8==1.5.7
pytest==2.8.3
pytest-mock==0.8.1
pytest-cov==2.2.0
coveralls==1.1
mock==1.0.1
moto==0.4.19
flex==5.6.0
freezegun==0.3.6
requests-mock==0.7.0
Initial version of the notify-notifications-api 2015-11-18 17:02:25 +00:00			`-r requirements.txt`
			`pep8==1.5.7`
Updated the Provider stats and rates DAO objects to query based on the identifier in the ProviderDetails object. - updated all tests - changed teardown to leave provider details rows on end of individual tests 2016-05-06 09:09:47 +01:00			`pytest==2.8.3`
Implement a JWT header into base client - adds a base client - adds a notifications client These do not proxy onto genuine methods. This pull request is the basic implication of the API Client. Still needs a few things before is ready, notably proper logging and actual API endpoints to hook into. Basic premise is to deliver the JWT tokens required for Notify API authentication so we can discuss the implementation/premise. 2015-12-11 16:57:00 +00:00			`pytest-mock==0.8.1`
			`pytest-cov==2.2.0`
Add code coverage 2016-06-17 17:09:46 +01:00			`coveralls==1.1`
Add sms notifications from a service to a queue. 2016-01-27 17:42:05 +00:00			`mock==1.0.1`
Add sender name to the notification - also ensure that the created time is handled properly 2016-02-25 11:23:04 +00:00			`moto==0.4.19`
Publish a Swagger specification Adds a new endpoint (`/spec`) which returns a the specification of the API in Swagger-formatted JSON. This means we will have something to point frontends at, so we can evaluate which ones we like. Right now it’s all hand-defined. If we were consistent about our use of Marshmallow we could generated the spec from the Marshmallow schemas. 2016-06-22 13:48:59 +01:00			`flex==5.6.0`
Add sender name to the notification - also ensure that the created time is handled properly 2016-02-25 11:23:04 +00:00			`freezegun==0.3.6`
tests for send_sms through mmg/firetext 2016-06-01 15:59:44 +01:00			`requests-mock==0.7.0`