rspec-rails-api 0.1.5 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a0c5ddec517d805e43305c00f7b7baa19373acb3d8fe55bca724e521e57cc8e3
-  data.tar.gz: 9f1ed792f16c075e140610902f8d7671d13d03483115066e55ca48c43b42f8d7
+  metadata.gz: '0861008371cafa6cab0cda5c165acda54b5a3047f152713bb684ae0c7c7be0ff'
+  data.tar.gz: d3c8877c5ef1e43c902010b68b9e483feefa6e57251d67aba325394a9682aee7
 SHA512:
-  metadata.gz: 501da0c03e7375b0097e95d951b1db831743564abd88dd4d28e719be5ee84701daaa9583160a0610dcd3cde35b143b8199b07e6bf684e0261fd26afca5b67d23
-  data.tar.gz: 5eaf88f5467cb5d5a12ca311e53778507534ff5090e85647581899bc5c4b7ab1f9914aea97f663bc7474faaede720fe66ff3d350ff0ba12982361b0772a00ae2
+  metadata.gz: e1009f40d78187888e546c74e62e88d7557f45a4a3cfed78a27785d63b401f673ed1796928f1d32823a665694b86761653bb87edc68522418d6117c4b576e362
+  data.tar.gz: 10ffebb4902456c4671b39b7dd707ea8ca870b9a27054c3139cae94bb3dcebfc3f88abd41a298ed870f98d7953c1195171cbf8f077db2dcd6530fe761e354a5a

data/.gitignore

@@ -12,5 +12,7 @@
 
 # Ignore lockfile for Gemfile
 Gemfile.lock
+# Keep the dummy one
+!dummy/Gemfile.lock
 
 .byebug_history

data/.gitlab-ci.yml

@@ -34,3 +34,10 @@ rspec:
     - bundle exec rspec
   dependencies:
     - bundle
+
+rspec-dummy:
+  stage: test
+  script:
+    - cd dummy
+    - bundle install --path='vendor/bundle'
+    - bundle exec rspec

data/.rubocop.yml

@@ -2,9 +2,13 @@
 require:
   - rubocop-performance
 
+AllCops:
+  Exclude:
+    - dummy/**/*
+    - vendor/bundle/**/*
+
 Metrics/BlockLength:
   Exclude:
-    - examples/**/*.rb
     - rspec-rails-api.gemspec
     - spec/**/*_spec.rb
 

data/CHANGELOG.md

@@ -1,6 +1,27 @@
 # Change Log
 All notable changes to this project will be documented in this file.
 
+## Not released
+
+## 0.2.0 - 2019-11-02
+
+### Added
+
+- `parameters` method to define path or requests params for the whole file.
+- A simple Rails application now acts as example and is used to generate some
+of the fixtures.
+
+### Changed
+
+- method `path_params` can now use a reference to a previously defined parameters
+  set. The method has a new signature: `path_params(fields: nil, defined: nil)`. Update
+  the existing calls accordingly. To use params defined with `parameters`, use the
+  `defined` option: `path_params defined: :common_path_params`
+- method `request_params` can now use a reference to a previously defined parameters
+  set. The method has a new signature: `request_params(attributes: nil, defined: nil)`. Update
+  the existing calls accordingly. To use params defined with `parameters`, use the
+  `defined` option: `request_params defined: :common_form_params`
+
 ## 0.1.5 - 2019-10-31
 
 ### Fixed

data/README.md

@@ -1,4 +1,4 @@
-# RSpecRailsApiDoc
+# RSpec-rails-api
 
 > An RSpec plugin to test Rails api responses and generate swagger
 > documentation
@@ -13,7 +13,7 @@ in order to test it.
 
 Add this line to your application's Gemfile:
 
-```rb
+```ruby
 gem 'rspec-rails-api'
 ```
 
@@ -29,7 +29,7 @@ Configuration should be made manually for now:
 
 **spec/acceptance_helper.rb**
 
-```rb
+```ruby
 require 'rails_helper'
 require 'rspec_rails_api'
 
@@ -38,13 +38,15 @@ RSpec.configure do |config|
 end
 
 renderer = RSpec::Rails::Api::OpenApiRenderer.new
-renderer.api_servers = [{ url: 'https://example.com' }]
-renderer.api_title = 'A nice API for a nice application'
+# Options here should be customized
+renderer.api_title = 'YourProject API'
 renderer.api_version = '1'
-renderer.api_description = 'Access update data in this project'
-# renderer.api_tos = 'http://example.com/tos.html'
-# renderer.api_contact = { name: 'Admin', email: 'admin@example.com', 'http://example.com/contact' } 
-# renderer.api_license = { name: 'Apache', url: 'https://opensource.org/licenses/Apache-2.0' }
+renderer.api_description = 'Manage data on YourProject'
+# Options below are optional
+renderer.api_servers = [{ url: 'https://example.com' }]
+renderer.api_tos = 'http://example.com/tos.html'
+renderer.api_contact = { name: 'Admin', email: 'admin@example.com', url: 'http://example.com/contact' } 
+renderer.api_license = { name: 'Apache', url: 'https://opensource.org/licenses/Apache-2.0' }
 
 RSpec.configuration.after(:context, type: :acceptance) do |context|
   renderer.merge_context context.class.metadata[:rrad].to_h
@@ -58,14 +60,14 @@ end
 
 **spec/rails_helper.rb**
 
-```rb
+```ruby
 # ...
 
 RSpec::Rails::DIRECTORY_MAPPINGS[:acceptance] = %w[spec acceptance]
 
 RSpec.configure do |config|
   # ...
-  config.include RSpec::Rails::RequestExampleGroup, :type => :acceptance
+  config.include RSpec::Rails::RequestExampleGroup, type: :acceptance
 end
 ```
 
@@ -77,7 +79,7 @@ end
 
 To use `sign_in` and `sign_out` from Devise in the acceptance tests, create a Devise support file:
 
-```rb
+```ruby
 # spec/support/devise.rb
 module DeviseAcceptanceSpecHelpers
   include Warden::Test::Helpers
@@ -97,7 +99,7 @@ end
 
 Load this file in `rails_helper.rb`:
 
-```rb
+```ruby
 #...
 # Add additional requires below this line. Rails is not loaded until this point!
 require 'support/devise'
@@ -106,7 +108,7 @@ require 'support/devise'
 
 Include the helper for acceptance specs:
 
-```rb
+```ruby
 RSpec.configure do |config|
   config.include DeviseAcceptanceSpecHelpers, type: :acceptance
 end
@@ -114,7 +116,7 @@ end
 
 You can now use the methods as usual:
 
-```rb
+```ruby
 # In a before block
 before do
   sign_in #...
@@ -122,9 +124,9 @@ end
 
 # In examples
 #...
-  for_code 200, 'Success' do |example|
+  for_code 200, 'Success' do |url|
     sing_in #...
-    visit example
+    visit url
 
     #...
   end
@@ -142,24 +144,20 @@ If you want to generate the documentation without testing the endpoints
 (and thus, without examples in generated files), use the `DOC_ONLY`
 environment variable:
 
-```rb
+```sh
 DOC_ONLY=true bundle exec rails spec
 ```
 
-For now, files are saved as `tmp/out.json` and `tmp/out.yml`.
-
-There is nothing to customize the file headers (info, license, ...) yet.
-
 ## Writing specs
 
-There is a [commented example](examples/commented.rb) available in
-`doc/`.
+There is a [commented example](dummy/spec/acceptance/posts_spec.rb) available in
+`dummy/spec/acceptance`.
 
 The idea is to have a simple DSL, and declare things like:
 
 **spec/acceptance/users_spec.rb**
 
-```rb
+```ruby
 require 'acceptance_helper'
 
 RSpec.describe 'Users', type: :acceptance do
@@ -174,8 +172,8 @@ RSpec.describe 'Users', type: :acceptance do
          url:        { type: :string, description: 'URL to this category' }
 
   on_get '/api/users/', 'Users list' do
-    for_code 200, 'Success response' do |example|
-      visit example
+    for_code 200, 'Success response' do |url|
+      visit url
       expect(response).to have_many defined :user
     end
   end
@@ -191,8 +189,8 @@ RSpec.describe 'Users', type: :acceptance do
       }
     }
 
-    for_code 200, 'Success response' do |example|
-      visit example
+    for_code 200, 'Success response' do |url|
+      visit url
       expect(response).to have_one defined :user
     end
   end
@@ -203,25 +201,24 @@ end
 
 #### Example groups
 
-##### `resource(name, description)`
+##### `resource(type, description)`
 
 Starts a resource description.
 
 - It must be called before any other documentation calls.
 - It should be in the first `describe block`
 
-##### `entity(name, fields)`
+##### `entity(type, fields)`
 
-Describes an entity for the documentation. The name is not visible, so
-you can put whatever fits (i.e: `:account`, `:user` if the content
-differs)
+Describes an entity for the documentation. The type is only a reference,
+you can put whatever fits (i.e: `:account`, `:user`, ...).
 
-They are ideally in the main `describe` block.
+They should be in the main `describe` block.
 
-- `name` is a symbol
+- `type` is a symbol
 - `description` is a hash of attributes
 
-```rb
+```ruby
 {
   id: { type: :integer, desc: 'The resource identifier' },
   name: { type: :string, desc: 'The resource name' },
@@ -253,7 +250,7 @@ An attribute should have the following form:
 To describe complex structures, use `:object` with `:attributes` and
 `:array` `:of` something:
 
-```rb
+```ruby
 entity :friend,
        name:    { type: :string, required: false, description: 'Friend name' }
 
@@ -277,6 +274,15 @@ inline.
 Both `:of` and `attributes` may be a hash of fields or a symbol. If they
 are omitted, they will be documented, but responses won't be validated.
 
+##### `parameters(type, fields)`
+Describe path or request parameters. The type is only a reference,
+use whatever makes sense. These parameters will be present in
+documentation, only if they are referenced by a `request_params` or
+`path_params` call.
+
+Fields have the structure of the hash you would give to `request_params`
+or `path_params` (see each method later in this documentation).
+
 ##### `on_<xxx>(url, description, &block)`
 
 Defines an URL.
@@ -294,15 +300,16 @@ For now, only these methods are available:
 - `on_patch`
 - `on_delete`
 
-##### `path_params(<hash_of_attributes>)`
+##### `path_params(fields: nil, defined: nil)`
 
 Defines the path parameters that are used in the URL.
 
-```rb
+```ruby
 on_get '/api/users/:id/posts/:post_slug?full=:full_post' do
-  path_params id:        type: :integer, description: 'The user ID',
-              post_slug: type: :string, description: 'The post slug',
-              full_post: type: :boolean, required: false, description: 'Returns the full post if `true`, or only an excerpt'
+  path_params fields: {
+                id:        { type: :integer, description: 'The user ID' },
+                post_slug: { type: :string, description: 'The post slug' },
+                full_post: { type: :boolean, required: false, description: 'Returns the full post if `true`, or only an excerpt' } }
 
   # ...
 end
@@ -313,18 +320,33 @@ end
   [CommonMark](https://commonmark.org/)
 - `required` is optional an defaults to `true`.
 
-##### `request_params(<hash_of_attributes>)`
+Alternative with defined parameters:
+
+```ruby
+parameters :users_post_path_params,
+           id:        { type: :integer, description: 'The user ID' },
+           post_slug: { type: :string, description: 'The post slug' }
+
+on_get '/api/users/:id/posts/:post_slug' do
+  path_params defined: :users_post_path_params
+
+  #...
+end
+```
+
+##### `request_params(attributes: nil, defined: nil)`
 
 Defines the format of the JSON payload. Type `object` is supported, so
 nested elements can be described:
 
-```rb
+```ruby
 on_post '/api/items' do
-  request_params item: { type: :object, required: true, properties: {
-                         name: { type: integer, description: 'The name of the new item', required: true },
-                         notes: { type: string, description: 'Additional notes' }
-                         },
-                       }
+  request_params attributes: {
+                   item: { type: :object, required: true, properties: {
+                     name: { type: integer, description: 'The name of the new item', required: true },
+                     notes: { type: string, description: 'Additional notes' }
+                     } }
+                   }
   #...
 end
 ```
@@ -342,6 +364,23 @@ An attribute should have the following form:
 - `properties` is a hash of params and is only used if `type: :object`
 - `of` is a hash of params and is only used if `type: :array`
 
+Alternative with defined parameters:
+
+```ruby
+parameters :item_form_params,
+           item: { type: :object, required: true, properties: {
+              name: { type: integer, description: 'The name of the new item', required: true },
+              notes: { type: string, description: 'Additional notes' }
+             }
+           }
+
+on_post '/api/items' do
+  request_params defined: :item_form_params
+
+  #...
+end
+```
+
 ##### `for_code(http_status, description, doc_only: false &block)`
 
 Describes the desired output for a precedently defined URL.
@@ -367,10 +406,10 @@ to test.
 Once again, you have to pass an argument to the block if you use
 `visit`.
 
-```rb
+```ruby
 # ...
-  for_code 200 'A successful response' do |example|
-    visit example
+  for_code 200, 'A successful response' do |url|
+    visit url
     # ...
   end
 # ...
@@ -395,9 +434,9 @@ Visits the described URL and:
   requests
 - `headers`: a hash of custom headers.
 
-```rb
-for_code 200, 'Success' do |example|
-  visit example
+```ruby
+for_code 200, 'Success' do |url|
+  visit url
 end
 ```
 
@@ -410,9 +449,9 @@ defined entity.
 
 It should be compared against a hash or a `response` object:
 
-```rb
+```ruby
 #...
-entity user:
+entity :user,
        id:   { type: :integer, desc: 'The id' },
        name: { type: :string, desc: 'The name' }
 
@@ -433,11 +472,11 @@ as a defined entity.
 
 It should be compared against an array or a `response` object:
 
-```rb
+```ruby
 #...
-entity user:
+entity :user,
        id:   { type: :integer, desc: 'The id' },
-       name: { type: :string, desc: 'The name }'
+       name: { type: :string, desc: 'The name' }
 
 #...
 
@@ -456,7 +495,7 @@ expect(response).to have_many defined :user
 Contexts will break the thing. This is due to how the gem builds its
 metadata, relying on the parents metadata. You have to stick to the DSL.
 
-```rb
+```ruby
 RSpec.describe 'Categories', type: :request do
   describe 'Categories'
 
@@ -494,14 +533,38 @@ There is no support for file fields yet.
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies.
-Then, run `rake spec` to run the tests. You can also run `bin/console`
+Then, run `bundle exec rspec` to run the tests. You can also run `bin/console`
 for an interactive prompt that will allow you to experiment.
 
-To install this gem onto your local machine, run `bundle exec rake
-install`. To release a new version, update the version number in
-`version.rb`, and then run `bundle exec rake release`, which will create
-a git tag for the version, push git commits and tags, and push the
-`.gem` file to [rubygems.org](https://rubygems.org).
+### Testing
+
+#### Dummy application
+
+A small Rails application is available as an example, in the `dummy` directory.
+If you write new features in the library, you'll have to update the examples to
+make them pass their tests:
+
+```shell
+cd dummy
+bundle exec rspec
+```
+
+Doing so will also update the fixtures used by some of the library tests.
+
+Please don't commit the fixtures unless the changes in them are directly related
+to the changes in the library.
+
+#### Code linting
+
+We use Rubocop here, with a releset for the library, and another for the dummy
+application:
+
+```shell
+bundle exec rubocop
+
+cd dummy
+bundle exec rubocop
+```
 
 ## Contributing
 

data/bin/setup

@@ -6,3 +6,5 @@ set -vx
 bundle install
 
 # Do any other automated setup that you need to do here
+cd dummy
+bundle install

data/lib/rspec/rails/api/dsl/example_group.rb

@@ -21,13 +21,30 @@ module RSpec
             metadata[:rrad].add_entity type, fields
           end
 
+          # Used to describe a request or path param which will be available as reference
+          def parameters(type, fields)
+            metadata[:rrad].add_parameter type, fields
+          end
+
           # Used to describe query parameters
-          def path_params(fields)
+          def path_params(fields: nil, defined: nil)
+            if defined && !metadata[:rrad].parameters[defined]
+              raise "Parameter #{defined} was not defined with the 'parameters' method"
+            end
+
+            fields ||= metadata[:rrad].parameters[defined]
+
             metadata[:rrad].add_path_params fields
           end
 
-          def request_params(fields)
-            metadata[:rrad].add_request_params fields
+          def request_params(attributes: nil, defined: nil)
+            if defined && !metadata[:rrad].parameters[defined]
+              raise "Parameter #{defined} was not defined with the 'parameters' method"
+            end
+
+            attributes ||= metadata[:rrad].parameters[defined]
+
+            metadata[:rrad].add_request_params attributes
           end
 
           def on_get(url, description = nil, &block)

data/lib/rspec/rails/api/metadata.rb

@@ -9,11 +9,12 @@ module RSpec
     module Api
       # Handles contexts and examples metadatas.
       class Metadata # rubocop:disable Metrics/ClassLength
-        attr_reader :entities, :resources, :current_resource
+        attr_reader :entities, :resources, :current_resource, :parameters
 
         def initialize
-          @resources = {}
-          @entities  = {}
+          @resources  = {}
+          @entities   = {}
+          @parameters = {}
           # Only used when building metadata during RSpec boot
           @current_resource = nil
           @current_method   = nil
@@ -32,6 +33,12 @@ module RSpec
                          EntityConfig.new(fields))
         end
 
+        def add_parameter(type, fields)
+          raise "Parameter #{type} is already defined" if @parameters[type]
+
+          @parameters[type] = fields
+        end
+
         def add_path_params(fields) # rubocop:disable Metrics/MethodLength
           check_current_context :resource, :url
 
@@ -138,7 +145,7 @@ module RSpec
         # rubocop:enable Metrics/CyclomaticComplexity, Metrics/PerceivedComplexity, Metrics/MethodLength, Style/GuardClause
 
         def path_param_scope(url_chunks, name)
-          if /:#{name}/ =~ url_chunks[0]
+          if /:#{name}/.match?(url_chunks[0])
             :path
           elsif url_chunks[1] && /:#{name}/ =~ url_chunks[1]
             :query

data/lib/rspec/rails/api/open_api_renderer.rb

@@ -19,7 +19,7 @@ module RSpec
         def initialize
           @metadata = { resources: {}, entities: {} }
           @api_infos = {}
-          @api_servers = {}
+          @api_servers = []
           @api_paths = {}
           @api_components = {}
           @api_tags       = []
@@ -27,11 +27,12 @@ module RSpec
           @api_license    = {}
         end
 
-        def merge_context(context)
+        def merge_context(context, dump_metadata: false)
           @metadata[:resources].deep_merge! context[:resources]
           @metadata[:entities].deep_merge! context[:entities]
-          # Save context to make the fixture (will be saved in the reference project)
-          # File.write ::Rails.root.join('tmp', 'meta.yaml'), context.to_yaml
+
+          # Save context for debug and fixtures
+          File.write ::Rails.root.join('tmp', 'rra_metadata.yaml'), context.to_yaml if dump_metadata
         end
 
         def write_files(path = nil, only: %i[yaml json])

data/lib/rspec/rails/api/version.rb

@@ -3,7 +3,7 @@
 module RSpec
   module Rails
     module Api
-      VERSION = '0.1.5'
+      VERSION = '0.2.0'
     end
   end
 end

data/rspec-rails-api.gemspec

@@ -26,7 +26,7 @@ Gem::Specification.new do |spec|
   # Specify which files should be added to the gem when it is released.
   # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
   spec.files = Dir.chdir(File.expand_path(__dir__)) do
-    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features|dummy)/}) }
   end
   spec.bindir        = 'exe'
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rspec-rails-api
 version: !ruby/object:Gem::Version
-  version: 0.1.5
+  version: 0.2.0
 platform: ruby
 authors:
 - Manuel Tancoigne
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-10-30 00:00:00.000000000 Z
+date: 2019-11-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -144,7 +144,6 @@ files:
 - Rakefile
 - bin/console
 - bin/setup
-- examples/commented.rb
 - lib/rspec/rails/api/dsl/example.rb
 - lib/rspec/rails/api/dsl/example_group.rb
 - lib/rspec/rails/api/entity_config.rb

data/examples/commented.rb

@@ -1,167 +0,0 @@
-# frozen_string_literal: true
-
-require 'acceptance_helper'
-
-RSpec.describe 'Categories', type: :acceptance do
-  # Needed to initialize documentation for this type of request.
-  # It should come before all the other calls (it will let the metadata
-  # class know which resource we're dealing with)
-  resource 'Categories', 'Manage categories in a group'
-
-  # Define an entity that can be returned by an URL.
-  entity :category,
-         id:         { type: :integer, description: 'The id' },
-         name:       { type: :string, description: 'The name' },
-         group_id:   { type: :number, description: 'Concerned group' },
-         created_at: { type: :datetime, description: 'Creation date' },
-         updated_at: { type: :datetime, description: 'Modification date' },
-         url:        { type: :string, description: 'URL to this category' }
-
-  entity :error,
-         error: { type: :string, description: 'The error' }
-
-  entity :form_error,
-         errors: {
-           type: :object, description: 'Form errors', attributes: {
-             name:  { type: :array, description: 'Name errors' },
-             group: { type: :array, description: 'Group errors' },
-           }
-         }
-
-  # Some vars to use in the tests
-  let(:current_user) { FactoryBot.create :user_active }
-
-  let(:group) { current_user.groups.first }
-  let(:group_id) { group.id }
-  let(:category) { FactoryBot.create :category, user: current_user, group: group }
-
-  # Declare a path accessed with a given method
-  # Their values can be declared with a  "let(:var){ value }" statement,
-  # or passed to "visit" method (see "for_code 404")
-  on_get '/api/groups/:group_id/categories', 'Categories defined in the given group' do
-    # Declare path parameters for documentation
-    path_params group_id: { type: :integer, description: 'Target group identifier' }
-
-    # Expectations for the given HTTP status
-    for_code 200, 'Success' do |example|
-      FactoryBot.create_list :category, 2, user: current_user, group: group
-
-      # This method is not built-in; check: ../README.md
-      sign_in current_user
-
-      # Actually visit the path. It will expect the given code and a
-      # content of type "application/JSON" (except for 204: no content
-      # statuses)
-      visit example
-
-      # Custom matcher: have_many will expect a body with an array of
-      # the given entity. All entries in the response will have its keys
-      # checked (not the content type).
-      # The `defined` method will get the correct entity for comparison
-      expect(response).to have_many defined :category
-
-      # Other expectations
-      expect(JSON.parse(response.body).count).to eq 2
-    end
-
-    for_code 404, 'Not found (not owned)' do |example|
-      sign_in current_user
-
-      group_id = FactoryBot.create(:user_active).groups.first.id
-
-      visit example, path_params: { group_id: group_id }
-      expect(response).to have_one defined :error
-    end
-
-    for_code 401, 'Not authorized' do |example|
-      visit example
-      expect(response).to have_one defined :error
-    end
-  end
-
-  on_get '/api/groups/:group_id/categories/:id', 'Get category' do
-    path_params group_id: { type: :integer, description: 'Target group identifier' },
-                id:       { type: :integer, description: 'Category id' }
-
-    let(:id) { category.id }
-
-    for_code 200, 'Success' do |example|
-      sign_in current_user
-
-      visit example
-      expect(response).to have_one defined :category
-    end
-
-    for_code 401, 'Not authorized' do |example|
-      visit example
-      expect(response).to have_one defined :error
-    end
-
-    for_code 404, 'Not found' do |example|
-      sign_in current_user
-
-      visit example, path_params: { id: 0 }
-      expect(response).to have_one defined :error
-    end
-  end
-
-  on_post '/api/groups/:group_id/categories', 'Creates a category' do
-    path_params group_id: { type: :integer, description: 'Target group identifier' }
-
-    request_params category: {
-      type: :object, required: true, attributes: {
-        name: { type: :string, required: true, description: 'The name' },
-      }
-    }
-
-    let(:id) { category.id }
-
-    for_code 201, 'Success' do |example|
-      sign_in current_user
-
-      visit example, payload: { category: { name: 'New category' } }
-      expect(response).to have_one defined :category
-    end
-
-    for_code 422, 'Form error' do |example|
-      sign_in current_user
-
-      visit example, payload: { category: {} }
-      expect(response).to have_one defined :form_error
-    end
-  end
-
-  on_put '/api/groups/:group_id/categories/:id', 'Updates a category' do
-    path_params group_id: { type: :integer, description: 'Target group identifier' },
-                id:       { type: :integer, description: 'Category id' }
-
-    let(:id) { category.id }
-
-    request_params category: {
-      type: :object, required: true, description: 'New category attributes', attributes: {
-        name: { type: :string, required: false, description: 'The new name' },
-      }
-    }
-
-    for_code 200, 'Success' do |example|
-      sign_in current_user
-
-      visit example, payload: { category: { name: 'New name' } }
-      expect(response).to have_one defined :category
-    end
-  end
-
-  on_delete '/api/groups/:group_id/categories/:id', 'Deletes a category' do
-    path_params group_id: { type: :integer, description: 'Target group identifier' },
-                id:       { type: :integer, description: 'Category id' }
-
-    let(:id) { category.id }
-
-    for_code 204, 'Success' do |example|
-      sign_in current_user
-
-      visit example
-      # Not checking content for 204 responses
-    end
-  end
-end