travis-api/spec/integration
Piotr Sarnacki 6e5f225a1c Don't reset the value if a new value is provided
If a value is provided with a request to update the record, we should
not nullify it. We don't send decrypted private values to the client, so
if client provides it, it's probably pasted by the user.
2014-09-10 11:02:24 +02:00
..
v1 Revert "removed the branches endpoint" 2014-06-17 14:44:13 +02:00
v2 Don't reset the value if a new value is provided 2014-09-10 11:02:24 +02:00
formats_handling_spec.rb Respond with 406 if we can't return requested formats 2013-02-25 17:27:56 +01:00
responders_spec.rb Allow to specify more than one scope for an endpoint 2013-05-08 14:11:02 +02:00
routes.backup.rb adapt services changes from travis-core 2012-10-05 13:06:50 +02:00
scopes_spec.rb Fix scoping spec 2013-11-12 22:16:47 +01:00
settings_endpoint_spec.rb Update code and specs for newest travis-core changes 2014-07-15 16:25:55 +02:00
singleton_settings_endpoint_spec.rb Treat repository_id as id for singleton settings 2014-07-23 13:34:30 +02:00
uptime_spec.rb Add tests for /uptime. 2013-08-26 17:29:10 +02:00
v1_spec.backup.rb backup routing specs from travis-ci 2012-10-03 14:57:58 +02:00
v2_spec.backup.rb backup routing specs from travis-ci 2012-10-03 14:57:58 +02:00
version_spec.rb Use version from each of the accept headers, not only first one 2013-02-25 17:28:24 +01:00