summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-09-20Merge tag '0.2.3'Azul
2013-09-19Merge pull request #84 from azul/test/billing-sessions0.2.3jessib
Test/billing subscriptions
2013-09-19Merge pull request #82 from azul/feature/sessions-expirejessib
Feature/sessions expire
2013-09-19Merge pull request #86 from azul/feature/syslog-default-in-productionjessib
default to syslog in production - #3886
2013-09-19Merge pull request #85 from azul/refactor/user_account_shortcutjessib
user.account shortcut to Account.new(user)
2013-09-19default to syslog in production - #3886Azul
2013-09-18minor: include missing CustomerTestHelperAzul
2013-09-18working integration testAzul
2013-09-18refactor: stub_customer test helperAzul
2013-09-18test subscription owner via credit card not transactionsAzul
There might not have been any transactions. Fixes the functional test
2013-09-18failing tests for subscriptionsAzul
functional: test canceling a subscription integration: investigate the issue with creating a subscription
2013-09-18user.account shortcut to Account.new(user)Azul
2013-09-18Merge pull request #83 from jessib/feature/billing_admin_cancel_subscriptionsazul
Feature/billing admin cancel subscriptions
2013-09-17We don't want billing active in development environment.jessib
2013-09-17This doesn't actually run any tests, but at least includes what we might ↵jessib
want to test regarding subscriptions.
2013-09-17integration tests for session expiryAzul
2013-09-17use new couchrest session store - expire after 30minAzul
2013-09-12Merge pull request #81 from leapcode/masterjessib
Version 0.2.2
2013-09-11Version 0.2.20.2.2Azul
2013-09-09First run at having admins cancel user subscriptions.jessib
2013-09-05Merge pull request #80 from azul/bugfix/fix-tests-broken-by-route-removalazul
use /login instead of /sessions/new and test successful login
2013-09-04switch submodule to use https:// instead of git:// - NOTE: this requires you ↵Micah Anderson
do a git submodule sync
2013-09-04use /login instead of /sessions/new and test successful loginAzul
2013-09-04fix login form - use api session urlAzul
There's no non api sessions resource anymore.
2013-09-03Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properlyjessib
Bugfix/3623 teardown test data properly
2013-09-03Merge pull request #75 from azul/feature/token-expiryjessib
Token expiry
2013-09-03Merge pull request #76 from azul/feature/3600-visual-feedback-on-failed-signupjessib
Ensure json requests get json error response on failure
2013-09-03Merge pull request #79 from azul/cleanup/remove-outdated-controller-actionsjessib
Cleanup/remove outdated controller actions
2013-09-03clearify usage of V1::UsersController#index for autocompleteAzul
[skip ci]
2013-09-03use the login logout named route instead of sessions resourceAzul
The main part of the sessions resource now lives in the API. the two named routes are just fine for what is left.
2013-09-03remove email aliases controller - we don't use it anymoreAzul
2013-09-03Cleanup sessions controller - webapp logs in through the api.Azul
So the #create and #update actions were not needed anymore. Also removed the tests
2013-09-03remove unneccessary user creation and destruction in ticket testAzul
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-09-03Account: Composition to handle User and its identitiesAzul
We have a lot of things that act upon a user record and one or more of it's identities at the same time: * Sing up: Create a user and it's initial identity * Rename: Change the username and create a new identity, turn old into an alias * Cancel Account: Remove user and all their identities. In order to keep the User and Identity behaviour isolated but still have a this logic represented in a sinle place the Account model deals with all these things. We could have overwritten the User#create, User#update and User#destroy methods instead. But then we would always create identities, even if we only need a user (for example in tests).
2013-09-03cleanup records after running user integration testsAzul
2013-09-03simplify users_controller_testAzul
2013-09-03don't leave id records behind when unit testingAzul
2013-09-03expire token according to config setting auth:token_expires_afterAzul
2013-09-03use Token#authenticate for authenticationAzul
This will return the user. But we can add timestamp validations and updates here.
2013-09-03integration test for displaying internal server error during signupAzul
2013-09-03Test the error handling of json and html responsesAzul
2013-09-03Ensure json requests get json error response on failureAzul
Normally rails sends an html page which can't be parsed by the client.
2013-09-02Merge pull request #78 from jessib/finish_removing_email_settings_referencesazul
Remove references to email_settings controller, which has been removed. ...
2013-09-02Remove references to email_settings controller, which has been removed. An ↵jessib
identities controller will replace it.
2013-09-02Merge pull request #77 from azul/feature/3522-configurable-logfilejessib
add config setting for logfile
2013-09-02Merge pull request #74 from azul/refactor/finding-usersjessib
there's no need for User#find_by_param. clean it up
2013-09-02document the logfile option in the defaults.ymlAzul
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 12:02:29 +0000