summaryrefslogtreecommitdiff
path: root/billing/test
AgeCommit message (Collapse)Author
2013-09-18working integration testAzul
2013-09-18refactor: stub_customer test helperAzul
2013-09-18failing tests for subscriptionsAzul
functional: test canceling a subscription integration: investigate the issue with creating a subscription
2013-09-17This doesn't actually run any tests, but at least includes what we might ↵jessib
want to test regarding subscriptions.
2013-09-03remove the user after integration testing customer creationAzul
2013-09-03different tests need different namesAzul
2013-09-03do not leave behind users in billing unit and functional testsAzul
2013-08-22Some more billing cleanup.jessib
2013-08-15Some notes on tests that don't work. (Failing tests are skipped though.)jessib
2013-08-12Remove broken test.jessib
2013-08-12more integration tests for billingAzul
2013-08-09fix billing tests to use user id with customer resourcesAzul
I think this is very confusing and should be changed to: resource :users do |user| user.resource :customer end
2013-08-06Some more tweaks to have billing code work, and allow admins to view but not ↵jessib
edit for other users.
2013-07-17billing bring back test for #with_braintree_data!Azul
2013-07-17billing: fix integration testAzul
This actually required three little fixes: * couchrest_session_store updated to 0.1.2 to make sure we store sessions * use BraintreeTestApp to proxy braintree requests that RackTest assumes are local * do not attempt to read status after a capybara request Also refactored the test a bit to set @user and login during setup.
2013-07-17billing: integration test creating customerAzul
2013-07-17billing: functional test for payments controllerAzul
2013-07-17billing: update customer records - do not create new onesAzul
2013-07-17billing: fix issue with customer.braintree_customerAzul
The default CouchRest Model belongs_to does not respect the class option. So we need to write our own getter method.
2013-07-17billing: functional tests reveal issue with customer.braintree_customerAzul
2013-07-17use fake_braintree, fix and test customer with braintree infoAzul
2013-07-17test non braintree parts of customer, validate userAzul
2013-07-17Very rough start to tests, which still doesn't really use FakeBraintree.jessib