Sha256: a59ffa32ecca1bfe9390ea87368f1a371a76140783be5e7788042e344d00ca3d
Contents?: true
Size: 1.85 KB
Versions: 1
Compression:
Stored size: 1.85 KB
Contents
Feature: controller schema scaffolding When you prefer to test controller not in a unit-test fashion, but including `render_views` - you can add `:lurker` metadata to get a json schema for your api-documented endpoint Scenario: scaffold a json schema for a "users/show" in controller spec Given a file named "spec/controllers/api/v1/users_controller_spec.rb" with: """ruby require "spec_helper" describe Api::V1::UsersController, :lurker do render_views let!(:user) do User.where(name: 'razum2um', surname: 'Marley').first_or_create! end it "shows user" do get :show, id: user.id, format: 'json' expect(response).to be_success end end """ When I run `bin/rspec spec/controllers/api/v1/users_controller_spec.rb` Then the example should pass Then a file named "lurker/api/v1/users/__id-GET.json.yml" should exist Then the file "lurker/api/v1/users/__id-GET.json.yml" should contain exactly: """yml --- description: user prefix: users management requestParameters: description: '' type: object additionalProperties: false required: [] properties: {} responseCodes: - status: 200 successful: true description: '' responseParameters: description: '' type: object additionalProperties: false required: [] properties: id: description: '' type: integer example: 1 name: description: '' type: string example: razum2um surname: description: '' type: string example: Marley extensions: method: GET path_info: "/api/v1/users/1.json" path_params: id: '1' controller: api/v1/users action: show suffix: '' """
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
lurker-0.6.1 | features/controller_schema_scaffolding.feature |