gitlab-org--gitlab-foss/spec/support/shared_examples/requests/graphql_shared_examples.rb

require 'spec_helper'

shared_examples 'a working graphql query' do
  include GraphqlHelpers

  it 'returns a successful response', :aggregate_failures do
    expect(response).to have_gitlab_http_status(:success)
    expect(graphql_errors).to be_nil
    expect(json_response.keys).to include('data')
  end
end
Add `present_using` to types By specifying a presenter for the object type, we can keep the logic out of `GitlabSchema`. The presenter gets initialized using the object being presented, and the context (including the `current_user`). 2018-05-21 07:52:24 +00:00			`require 'spec_helper'`

			`shared_examples 'a working graphql query' do`
			`include GraphqlHelpers`

Expose permissions on types in GraphQL This adds a reusable way to expose permissions for a user to types in GraphQL. 2018-06-25 08:59:00 +00:00			`it 'returns a successful response', :aggregate_failures do`
			`expect(response).to have_gitlab_http_status(:success)`
Add mutation toggling WIP state of merge requests This is mainly the setup of mutations for GraphQL. Including authorization and basic return type-structure. 2018-07-10 14:19:45 +00:00			`expect(graphql_errors).to be_nil`
Initial setup GraphQL using graphql-ruby 1.8 - All definitions have been replaced by classes: http://graphql-ruby.org/schema/class_based_api.html - Authorization & Presentation have been refactored to work in the class based system - Loaders have been replaced by resolvers - Times are now coersed as ISO 8601 2018-05-23 07:55:14 +00:00			`expect(json_response.keys).to include('data')`
Add `present_using` to types By specifying a presenter for the object type, we can keep the logic out of `GitlabSchema`. The presenter gets initialized using the object being presented, and the context (including the `current_user`). 2018-05-21 07:52:24 +00:00			`end`
			`end`