summaryrefslogtreecommitdiff
path: root/test/unit
AgeCommit message (Collapse)Author
2016-05-02tests: Validator.new has optional options hashAzul
but you may not hand it a nil
2016-05-02upgrade: unique test namesAzul
Rails 4.2 runs all tests mixed together. So unit tests and integration tests may not have conflicting names.
2016-04-11allow monitor auth to create users even if invites are normally required.elijah
2016-03-28api tokens - clarify terms: "monitors" are admins that authenticated via api ↵elijah
token, "tmp" users are users that exist only in tmp db, "test" users are either tmp users or users named "test_user_x"
2016-03-28api tokens: allow for special api tokens that work like session tokens but ↵elijah
are configured in the static config, to be used for infrastructure monitoring.
2016-02-10allow user accounts to be re-enabled, and for associated identities to also ↵elijah
get re-enabled.
2016-01-31remove cert fingerprints for disabled users, so that they cannot send email ↵elijah
anymore. closes #7690
2015-10-06Integrated feedback on multi-invite codesankonym
Removing some superfluous code, mostly, and structuring tests better.
2015-10-02Update rake task to allow generation of multi-use invitesankonym
The rake task now takes a second (optional) argument that sets the number of uses per invite code. If this is omitted, the default number of uses is 1. (This commit also contains some minor code cleanup that removes some stuff that I'd commented out but not removed.)
2015-10-02Allow multi-use invite codesankonym
Introduce a invite_max_uses property to invite codes to allow admins to set a maximum number of uses for invite codes.
2015-09-28Make invite code configurableankonym
Through the config param 'invite_required', providers can decide whether users need to provide an invite code upon signup. The default setting is false.
2015-09-28Removed the view_by__id from invite code testankonym
2015-09-28Fixed the signup bug that wrongly consumes the invite code.Aya Jaff
2015-09-28Fix three unit tests by passing Factory Girl a valid invite codeankonym
The tests were failing because of a hardcoded "testcode" string so during test setup we generate a valid code and pass it to Factory Girl
2015-09-28Fix several test failures by stubbing invite code validationankonym
2015-09-28Separate user and invite code validator testsankonym
2015-09-28Fixes for the invite code validatorankonym
Validation should only happen for new records User invite code was nil for invalid invite codes Adding missing tests
2015-09-28Make sure codes can only be used once, fix validationsankonym
We introduced a count on invite codes to make sure that (at the moment) codes can only be used once. (The code will also allow multi-use codes in the future.) Also, some of our validations weren't validating against the correct data, which is now fixed.
2015-09-28assign random invite code when creating new invite codesankonym
2015-09-28Fix test based on actual invite code validationankonym
2015-09-28Added an 'invite code' to all the tests for the sign-up form so we have a ↵Aya Jaff
valid user for the tests again
2015-09-28Adding invite code field to signup with validation for hardcoded invite codeankonym
2015-09-10couchrest_model 2.0.1 fixes find_by_sth(nil)Azul
This used to return the first record! :scream: This [commit](https://github.com/couchrest/couchrest_model/commit/2c5b76823e94caed4d8cbfbf18cb9e0d58789789) is essential for say User.find_by_login(nil) to NOT return the first record in the database.
2015-08-07do not include random cruft in the common name of smtp client certificateselijah
2015-03-17add support for rotating tokens and sessions databases, and for a special ↵elijah
tmp db for test users.
2014-07-14minor: remove @s added by search and replaceAzul
meant to move id -> @id, also turned identity in the test titles into @identity.
2014-07-14minor: fix identity test for storing certsAzul
we compare the cert that expires last to the one we just saved. So we need to make sure the one we saved is the one that expires last.
2014-07-12allow querying for the expiry of a particular fingerprintAzul
2014-07-12Identity view cert_fingerprints_by_expiryAzul
Also move complex identity views into js designs. Includes test. Here's how you would query it from outside rails: ``` $ curl 'localhost:5984/identities/_design/Identity/_view/cert_fingerprints_by_expiry?startkey="2014-07-05"' {"total_rows":4,"offset":1,"rows":[ {"id":"6c9091d4f13eaeaa6062c9d0528fd34d","key":"2014-07-05","value":"fingerprint"}, {"id":"6f3aa93828b4f6978d551f2623b9d103","key":"2014-07-05","value":"fingerprint"}, {"id":"b6cafacfa65042679691cd5065fb19e3","key":"2014-07-07","value":"fp"} ]} ``` Note that the expiry will be used as the key. So you should use the current data (or yesterday) as the startkey to get all fingerprints that have not expired yet. The fingerprint itself is in the value. No need to include docs.
2014-05-29clearify identity validationsAzul
Identity.new.valid? should not crash. So validate presence where needed and skip the other validations if the value is absent.
2014-05-29hand on errors from Email to Identity to UserAzul
errors.each iterates through all errors for all attrbibutes nicely.
2014-05-28adopt tests to new error messages for identitiesAzul
2014-05-26Merge pull request #163 from azul/feature/3398-save-hashed-tokenazul
hash token with sha512 against timing attacs #3398
2014-05-26hash token with sha512 against timing attacs #3398Azul
2014-05-19fix Email so User.new.valid? does not crashAzul
Email.new(nil) now returns an invalid email rather than crashing.
2014-05-13destinguish user.email from user.email_addressAzul
use the former if you want a working email account or nil, the latter if you want the email address associated with a given user no matter if the user actually has an email account or not.
2014-04-18change service level configuration strategyAzul
The changes to the configuration required some non minor changes to the platform and also added some flexibility we don't require yet - and thus some new possibilities for errors. So instead we still use the allow_..._certs and ..._cert_prefix options. They basically provide the framework in which service levels can operate. The service level configuration will not include the cert prefix anymore. It only states if the service level is rate limited or not. This avoids conflicts between the two configuration options. I also removed the anonymous service level entirely. It was also turning a boolean decision (do we provide anonymous eip or not) into something way more complex. Instead I added the AnonymousServiceLevel class to handle the corner cases for people who are not logged in. Furthermore i renamed the UnauthenticatedUser to AnonymousUser so it matches the Anonymous Service Level nicely. It's also shorter and more intuitive.
2014-04-10move certs into toplevelAzul
cleaned up all the engine stuff that was never really used. Afterwards there is not that much left that makes it into the toplevel.
2014-04-08moving users: app and test filesAzul
2013-07-24validations of email format and local domain moved overAzul
2012-09-27Adding in what used to be leap webapp demoAzul
we're merging repositories into one