index
:
leap_web.git
drop/ruby-2.1
feat/drop-signup
master
version/0.6
version/0.6.1
version/0.7
version/0.7.1
version/0.8
version/0.9
[leap_web]
git repository hosting
summary
refs
log
tree
commit
diff
log msg
author
committer
range
path:
root
/
billing
/
test
Age
Commit message (
Expand
)
Author
2013-12-22
locale prefix support:
elijah
2013-12-17
Merge branch 'develop' into feature/billing-no-authenticated-payments
jessib
2013-10-15
Add permissions to subscriptions index, and fix test to stub the subscription...
jessib
2013-10-08
Payments made when authenticated will be donations, and not connected to cust...
jessib
2013-10-08
Minor tweaks.
jessib
2013-10-07
Fix typo in test name.
jessib
2013-09-18
minor: include missing CustomerTestHelper
Azul
2013-09-18
working integration test
Azul
2013-09-18
refactor: stub_customer test helper
Azul
2013-09-18
failing tests for subscriptions
Azul
2013-09-17
This doesn't actually run any tests, but at least includes what we might want...
jessib
2013-09-03
remove the user after integration testing customer creation
Azul
2013-09-03
different tests need different names
Azul
2013-09-03
do not leave behind users in billing unit and functional tests
Azul
2013-08-22
Some more billing cleanup.
jessib
2013-08-15
Some notes on tests that don't work. (Failing tests are skipped though.)
jessib
2013-08-12
Remove broken test.
jessib
2013-08-12
more integration tests for billing
Azul
2013-08-09
fix billing tests to use user id with customer resources
Azul
2013-08-06
Some more tweaks to have billing code work, and allow admins to view but not ...
jessib
2013-07-17
billing bring back test for #with_braintree_data!
Azul
2013-07-17
billing: fix integration test
Azul
2013-07-17
billing: integration test creating customer
Azul
2013-07-17
billing: functional test for payments controller
Azul
2013-07-17
billing: update customer records - do not create new ones
Azul
2013-07-17
billing: fix issue with customer.braintree_customer
Azul
2013-07-17
billing: functional tests reveal issue with customer.braintree_customer
Azul
2013-07-17
use fake_braintree, fix and test customer with braintree info
Azul
2013-07-17
test non braintree parts of customer, validate user
Azul
2013-07-17
Very rough start to tests, which still doesn't really use FakeBraintree.
jessib