gitlabhq/spec/requests
Sebastian Ziebell f978a71f41 Creating MR comment without a note returns status code 400 (Bad request)
Creating a comment to an existing merge request via API without providing a note
returns a status code 400 now, suggesting a bad request. The reason for this
is the resource itself (MR) exists but the required property is not set.
2013-02-06 17:02:30 +01:00
..
admin Add optional signup. 2013-01-18 11:57:31 +01:00
api Creating MR comment without a note returns status code 400 (Bad request) 2013-02-06 17:02:30 +01:00
atom Fixed dashboard show specs 2013-01-27 13:20:23 +02:00
security Fix security spec 2013-01-05 00:49:43 +02:00
gitlab_flavored_markdown_spec.rb should be green build now :) 2013-01-15 19:18:52 +02:00
issues_spec.rb Continue refactoring. Use repostory and team 2013-01-04 08:43:25 +02:00
notes_on_merge_requests_spec.rb Fix spec/requests/notes_on_merge_requests_spec.r 2013-01-15 18:20:58 +02:00
notes_on_wall_spec.rb fix notes_on_wall specs 2013-01-15 15:04:22 +02:00
projects_deploy_keys_spec.rb Rspec fixes 2013-01-04 18:50:31 +02:00
projects_spec.rb A bit of spinach tests 2013-01-09 08:14:05 +03:00
search_spec.rb Rspec fixes 2013-01-04 18:50:31 +02:00
snippets_spec.rb Rspec fixes 2013-01-04 18:50:31 +02:00