summaryrefslogtreecommitdiff
path: root/test
AgeCommit message (Collapse)Author
2014-05-19fix Email so User.new.valid? does not crashAzul
Email.new(nil) now returns an invalid email rather than crashing.
2014-05-19basic integration test for cert APIAzul
2014-05-13adjust tests to new config and method implementationAzul
Ticket.is_creator_vlidated? now actually fetches the user from the db and returns false if it does not exist.
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-05-13minor: use %Q for interpolated string with "Azul
2014-05-13keep empty email field if user removed prefillAzul
We should respect the users choice. We can still get their email from the user id if we really need to.
2014-05-13allow for usernames with dotsAzul
preparing for #5664 with some test improvements i ran into this issue This commit includes a fix and the test improvements. In particular it adds BrowserIntegrationTest#login - so there is no need to go through the signup procedure everytime you want a user to be logged in.
2014-05-06hide srp forms when no js is availableAzul
Hiding them using two mechanisms in case one fails: .hidden class - bootstrap hides them then style='display:none' - so they are hidden even if css load fails
2014-04-30remove outdated os detection testAzul
2014-04-25basic password validation without client side gemAzul
The client_side_validations gem is not maintained anymore and the validations were not working lately. So instead of trying to fix it I started working on independent validations for the password as it can't be validated on the server due to SRP. So far these validations are very primitive. They require 8 characters length and a matching confirmation.
2014-04-25make test independent of button tagAzul
input or button can be used
2014-04-25Merge pull request #148 from azul/feature/api-quota-supportazul
Feature/api quota support + current_user null pattern
2014-04-18adopt service_level config to platform settingsAzul
cost -> rate quota -> storage
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-17adjust test to service list in configAzul
2014-04-17make use of the UnauthorizedUserAzul
Null Pattern for current_user - use it to get rid of some conditionals
2014-04-17initial commit for the service level apiAzul
:api/service will return a hash of the current users service level This is failiing if the user is not logged in. Instead it should return the service description for an anonymous user.
2014-04-17add a try/except for older versions of requestsAzul
they have response.json as a dict instead of response.json()
2014-04-17nagios test: also test registering new usersAzul
2014-04-17nagios test: use support classes in soledad syncAzul
2014-04-17remove unneeded importsAzul
2014-04-17move support classes into their own packageAzul
now the webapp_login test looks nice and clean. soledad next.
2014-04-17nagios test: refactor webapp_login with classesAzul
2014-04-17refactor: move nagios specifs to nagios_testAzul
nagios_test.run takes a function and executes it. If it returns nothing or 0 and OK nagios message is printed. If it returns sth. else this will be printed a a warning If it raises an exception that will result in a CRITICAL report. This way we can keep the nagios things outside the test cases and just write simple functions that either return 0, a warnign or raise a meaningful exception
2014-04-17refactor reporting in webapp login nagios testAzul
2014-04-17refactor nagios tests, remove parseAzul
2014-04-11move include AssertResponses into test itselfAzul
it may not have been required before the RackTest support class.
2014-04-11move engines into engines directoryAzul
Also renamed help to support so it's harder to confuse it with documentation
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-08only load */test/factories from test/factoriesAzul
prevent recursive loadign of test/factories.rb ** can be empty.
2014-04-08moving users: app and test filesAzul
2014-04-08fix requiring core extensions - most tests passAzul
some message tests are failing for me right now.
2014-04-08moving all of core into toplevel, tests fail.Azul
2014-04-02Fix soledad sync nagios plugin returned check_name (#5430).db
2014-03-07Add script to check if soledad is working (#5239).db
2014-03-02including chiiphs commentsAzul
2014-03-02autopep8 nagios webapp login testAzul
2014-02-27nagios test for logging into webappAzul
2014-02-10refactor tests to ease the testing of token only authAzul
2014-02-07log failing integration tests with screenshotAzul
* store the last screenshot in tmp * store the html and the end of the server log in tmp Filenames are build from the test class name and the tests name.
2014-02-06integration test with en-EN languageAzul
Tests fail on machines that default to other available languages. Also move setting capybara driver to be javascript driver into the BrowserIntegrationTest.
2013-12-29Return 'provider.json' via a controller, to better be able to control the ↵elijah
response headers (in particular, 'X-Minimum-Client-Version'). It must now be placed in config/provider/provider.json
2013-12-22locale prefix support:elijah
* set locale based on request header * enforce locale path prefix when current locale is not the default * note: don't use root_path anymore, instead use home_path
2013-12-13minor: rename testAzul
2013-10-15detect os in browser and show proper download linkAzul
We add a class to the html element based on the detected os and use that to pick which download link should be visible. If we detect an os that is not supported we display a deactivated download link instead with all alternatives.
2013-09-17integration tests for session expiryAzul
2013-09-03integration test for displaying internal server error during signupAzul
2013-09-03Test the error handling of json and html responsesAzul
2013-07-24validations of email format and local domain moved overAzul
2013-07-16ensure the page has been reloaded before testing current_pathAzul
This test would fail sometimes on assert_equal '/', current_path I believe it was a timing issue. page.has_content? will wait for the content to show up. So afterwards the current_path should always be correct.