summaryrefslogtreecommitdiff
path: root/users/test
AgeCommit message (Collapse)Author
2013-01-17Merge pull request #16 from leapcode/feature/fixing-routes-with-apiazul
Fixing routes with api
2013-01-18minor: smalles fix ever - is_admin? has a questionmarkAzul
2013-01-17Should be able to create a user when not logged in.jessib
This isn't ready to merge, as there is an issue with logging in as an admin in the test.
2013-01-17unit tests passingAzul
2013-01-16incomplete initial changes to make email address just login@domain.tldAzul
This involves a number of other changes like making sure the comparison between aliases and emails still works. Will do that by removing the @domain.tld from aliases as well.
2013-01-16using subdomain for api requests properlyAzul
2013-01-14Merge branch 'master' into feature/show_user. Added new tests.jessib
Conflicts: users/test/functional/users_controller_test.rb
2013-01-14minor: further cleanup - try to leave no record behindAzul
2013-01-14tickets controller tests passingAzul
2013-01-14got users controller test to pass - tickets controller test next.Azul
2013-01-11basic dummy data for usersAzul
2013-01-10Add test for showing user.jessib
2012-12-20fixed tests, testing corner cases, fixed theseAzul
2012-12-18adopted functional tests to new controller designAzul
2012-12-18only destroy user that has been persisted in teardownAzul
2012-12-18refactored email_alias creation and validationAzul
using CouchRests user.email_aliases.build so the casted_by method is set in the alias Used this to move the validations into the alias itself. This is where they belong and allows us to render the errors inline along the email field they belong to.
2012-12-18adjusted tests - we now reload the user so invalid records are clearedAzul
Actually that might not be the best idea. Issue at hand was that invalid email aliases were getting displayed when rendering the edit form again. We probably want to solve this different.
2012-12-17Merge branch 'feature/fixing-signup-and-login-issues'Azul
2012-12-17fixed inclusion of stub record helperAzul
2012-12-17fixed all user functional testsAzul
2012-12-13Merge branch 'master' into developAzul
Conflicts: users/test/unit/user_test.rb
2012-12-13refactor: changed add_email to add_email_aliasAzul
that's what it does. Changed all tests to use it instead of the attributes method
2012-12-13refactor: allow adding email aliases directlyAzul
2012-12-13ensure users do not have duplicate email aliasesAzul
nor aliases that are the same as the original email for that matter
2012-12-13LocalEmail added - will validate uniqueness amongst emails and aliasesAzul
2012-12-12find users by email and aliasesAzul
2012-12-12Merge branch 'master' into developAzul
2012-12-11make sure can login twiceAzul
2012-12-10created generic Email class and use it with EmailAliasesAzul
2012-12-09first steps towards email aliasesAzul
* unit tests draft * controller draft
2012-12-08serve api version 1 in /1/Azul
Just a very simple start for now. Do we want to use the api for the secure remote password auth from js?
2012-12-07Merge branch 'master' into help_developjessib
Conflicts: app/views/layouts/application.html.haml help/app/controllers/tickets_controller.rb help/test/functional/tickets_controller_test.rb users/test/support/stub_record_helper.rb
2012-12-07fixed test to work with edit view that includes email and email forward.Azul
2012-12-03refactored tests with new find_record helperAzul
find_record User will return a stubbed user record and make sure User.find_by_id(user.id) returns the same so it can be used in controllers.
2012-12-03enable users to cancel their accountAzul
2012-12-03enable admin to edit usersAzul
2012-12-03make tests pass on an empty dbAzul
2012-12-01using login :is_admin => true instead of real recordsAzul
Travis CI does not seem to have the admin user records. Let's not depend on them and just stub the admin user.
2012-12-01Merge branch 'develop' into help_developAzul
2012-11-28admins can destroy usersAzul
I changed the permissions a little to be more consistent. Now: * admins can edit users * users can destroy themselves. There's no ui for either of them but theoretically they could. Not sure this is what we want though.
2012-11-26Merge branch 'develop' into help_developjessib
Conflicts: users/app/views/sessions/_nav.html.haml
2012-11-26fixed login error message on wrong usernameAzul
2012-11-26simplified controller and adjusted testsAzul
Also added #assert_json_error to tests.
2012-11-23identify user by id so rerendering the form does not use new invalid loginAzul
2012-11-23refactored creation of record stubsAzul
2012-11-23test editing user settingsAzul
2012-11-22fixed testsAzul
2012-11-20Merge branch 'develop' into help_developjessib
2012-11-19Merge branch 'develop' into help_developjessib
Conflicts: app/assets/javascripts/application.js ui_dependencies.rb
2012-11-19use latest mocha version without monkey patching :)Azul