fitting 2.12.1 → 2.15.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 1415f580792a267f0db27df63a8ef8334d0cd0cc
-  data.tar.gz: 4e5868e53b370121ab7cfad0e1762d014b4f310d
+SHA256:
+  metadata.gz: d604ca859d26a71406a404ad3fd2ea7d232fa670ee1f930ada129df6fe55f15a
+  data.tar.gz: 919ece6a20bdf078459ef5b42351687ddbabb01296364ba52cf4f5e669e36d7d
 SHA512:
-  metadata.gz: f93db3c0f9c83d2ec34b84ab4d3e91e8b5d06ba988bc5f4d40eb9c2e63664a30589857909c054e4d19b3099ca223403df2cd8026856a25360dae4ab050cf4dce
-  data.tar.gz: 81ce958a9daed16da84fea079964caf4b7e396bb473a5d89f856f6ff9a453e398b742aedd667a1dbaebb56a71347b3056d3b61f4b188b32615e1050dfb75e3c3
+  metadata.gz: '0810933b01cb101b7cee10d06e522a29e746139181ccd7c948f6af3b6aa0dcf082856db941c371b1e1945839b5a7ddff537fc2656025bf905485d06ed61685bd'
+  data.tar.gz: c08f43a84f31a7d029c0c72f4667e95c9e9769a92a3bb243a4a6de7af8da2e493bd63716794ee24f04eb7bd31dff43a71bb2ebf67ec9078685fb08dffd885195

data/.github/workflows/ruby.yml

@@ -0,0 +1,33 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+# This workflow will download a prebuilt Ruby version, install dependencies and run tests with Rake
+# For more information see: https://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
+
+name: Ruby
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  test:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Ruby
+    # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
+    # change this to (see https://github.com/ruby/setup-ruby#versioning):
+    # uses: ruby/setup-ruby@v1
+      uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0
+      with:
+        ruby-version: 2.6
+    - name: Install dependencies
+      run: bundle install
+    - name: Run tests
+      run: bundle exec rake

data/.rubocop.yml

@@ -1,5 +1,5 @@
 AllCops:
-  TargetRubyVersion: 2.2
+  TargetRubyVersion: 2.3
 
 Metrics/LineLength:
   Max: 120

data/.ruby-version

@@ -1 +1 @@
-2.2.0
+2.6.1

data/.tool-versions

@@ -1 +1 @@
-ruby 2.2.0
+ruby 2.6.1

data/CHANGELOG.md

@@ -1,5 +1,59 @@
 # Change log
 
+### 2.15.0 - 2020-10-12
+
+* features
+  * color for bad response [#79](https://github.com/funbox/fitting/issues/79)
+  * show test details [#81](https://github.com/funbox/fitting/issues/81)
+* patch
+  * update ruby [#83](https://github.com/funbox/fitting/issues/83)
+  * update bundler [#84](https://github.com/funbox/fitting/issues/84)
+  * update tomograph [#85](https://github.com/funbox/fitting/issues/85)
+  * use github actions for CI instead of Travis [#30](https://github.com/funbox/fitting/issues/30)
+
+### 2.14.1 - 2020-09-23
+
+* fixes
+  * fix directory error [#75](https://github.com/funbox/fitting/issues/75)
+  * upgrade node-forge [#77](https://github.com/funbox/fitting/issues/77)
+
+### 2.14.0 - 2020-09-18
+
+* features
+  * save tests for all prefixes [#35](https://github.com/funbox/fitting/issues/35)
+  * prefix checking [#37](https://github.com/funbox/fitting/issues/37)
+  * html view for prefix checking [#39](https://github.com/funbox/fitting/issues/39)
+  * add actions join in new html report [#41](https://github.com/funbox/fitting/issues/41)
+  * add responses join in new report [#43](https://github.com/funbox/fitting/issues/43)
+  * add combinations join in new report [#47](https://github.com/funbox/fitting/issues/47)
+  * add action page [#49](https://github.com/funbox/fitting/issues/49)
+  * show more information in new report [#51](https://github.com/funbox/fitting/issues/51)
+  * add accordion for prefixes [#55](https://github.com/funbox/fitting/issues/55)
+  * move json-schemas to separate files [#57](https://github.com/funbox/fitting/issues/57)
+  * add method for tests without actions [#61](https://github.com/funbox/fitting/issues/61)
+  * show tests without responses [#63](https://github.com/funbox/fitting/issues/63)
+  * add console output for new report [#69](https://github.com/funbox/fitting/issues/69)
+  * check test in new console [#71](https://github.com/funbox/fitting/issues/71)
+* fixes
+  * fix vulnerability CVE-2020-7660 [#53](https://github.com/funbox/fitting/issues/53)
+  * fix cover if response without combinations [#59](https://github.com/funbox/fitting/issues/59)
+  * fix cover if combinations without tests [#66](https://github.com/funbox/fitting/issues/66)
+  * do not check tests without combinations [#73](https://github.com/funbox/fitting/issues/73)
+
+### 2.13.1 - 2020-04-17
+
+* fixes
+  * combinations
+
+### 2.13.0 - 2020-02-26
+
+* features
+  * use request tests
+
+* patch
+  * improve combination name for enum cover
+  * improve combination name for required cover
+
 ### 2.12.1 - 2020-02-07
 
 * fixes

data/README.md

@@ -1,42 +1,41 @@
 # Fitting
 
-<a href="https://funbox.ru">
-  <img src="https://funbox.ru/badges/sponsored_by_funbox_compact.svg" alt="Sponsored by FunBox" width=250 />
-</a>
-
 [![Gem Version](https://badge.fury.io/rb/fitting.svg)](https://badge.fury.io/rb/fitting)
-[![Build Status](https://travis-ci.org/funbox/fitting.svg?branch=master)](https://travis-ci.org/funbox/fitting)
 
 This gem will help you implement your API in strict accordance to the documentation in [API Blueprint](https://apiblueprint.org/) format.
-To do this, when you run your RSpec tests on controllers, it automatically searches for the corresponding json-schemas in the documentation and then validates responses with them.
+To do this, when you run your RSpec tests on controllers, it automatically searches for the corresponding JSON-schemas in the documentation and then validates responses with them.
 
 ## Installation
 
 First you need to install [drafter](https://github.com/apiaryio/drafter).
 
-Second add this line to your application's Gemfile:
+Then add this line to your application's Gemfile:
 
 ```ruby
 gem 'fitting'
 ```
 
-And then execute:
+After that execute:
 
-    $ bundle
+```bash
+$ bundle
+```
 
-Or install it yourself as:
+Or install the gem by yourself:
 
-    $ gem install fitting
+```bash
+$ gem install fitting
+```
 
 ## Usage
 
-In your `.fitting.yml`:
+Add this to your `.fitting.yml`:
 
 ```yaml
 apib_path: /path/to/doc.apib
 ```
 
-In your `spec_helper.rb`:
+And this to your `spec_helper.rb`:
 
 ```ruby
 require 'fitting'
@@ -44,11 +43,11 @@ require 'fitting'
 Fitting.save_test_data
 ```
 
-The files will be created in ./fitting_tests/ path
+The result files will be created in `./fitting_tests/` folder.
 
-Example:
+Output example:
 
-```
+```json
 [
   {
     "method": "GET",
@@ -75,30 +74,45 @@ Example:
     },
     "title": "/spec/controllers/api/v1/books_controller_spec.rb:22",
     "group": "/spec/controllers/api/v1/books_controller_spec.rb"
-  },
-  ...
+  }
+]
 ```
 
+## Documentation coverage
+
+To match routes and validate JSON-schemas run:
 
-## Check documentation cover
+```bash
+rake fitting:documentation_responses[report_size]
+```
 
-### xs size
+There are four types (or `report_size`) of reports available: 
+  
+- `xs` — the smallest report;
+- `s` — includes coverage for `required` fields;
+- `m` — includes coverage for `required` and `enum` fields;
+- `l` — includes coverage for `required`, `enum` and `oneOf` fields.
 
-For match routes and valid json-schemas run
+E.g. for `xs` size:
 
-for bash
-```
+```bash
 rake fitting:documentation_responses[xs]
 ```
 
-for zsh
-```
+**Note**: In zsh you should add quotes around the task:
+
+```bash
 rake 'fitting:documentation_responses[xs]'
 ```
 
-You will get statistics:
+Also you can use `documentation_responses_error` to get more detailed errors description.
+Check the examples below. 
 
-```
+### Examples
+
+`xs` size:
+
+```text
 Fully conforming requests:
 DELETE  /api/v1/book                 ✔ 200 ✔ 201 ✔ 404
 DELETE  /api/v1/book/{id}            ✔ 200 ✔ 201 ✔ 404
@@ -122,11 +136,9 @@ API responses conforming to the blueprint: 16 (64.00% of 25).
 API responses with validation errors or untested: 9 (36.00% of 25).
 ```
 
-### s size
-
-In addition to the previous comand, you will learn the coverage(required) json-schemas with task `rake fitting:documentation_responses[s]`
+`s` size:
 
-```
+```text
 Fully conforming requests:
 DELETE  /api/v1/book                 100% 200 100% 201 100% 404
 DELETE  /api/v1/book/{id}            100% 200 100% 201 100% 404
@@ -150,7 +162,7 @@ API responses conforming to the blueprint: 16 (64.00% of 25).
 API responses with validation errors or untested: 9 (36.00% of 25).
 ```
 
-For details `rake fitting:documentation_responses_error[s]`
+`documentation_responses_error[s]` example:
 
 ```
 request method: GET
@@ -161,68 +173,79 @@ combination: ["required", "pages"]
 new json-schema: {"$schema"=>"http://json-schema.org/draft-04/schema#", "type"=>"object", ...}
 ```
 
-### m size
+### Experimental report
 
-In addition to the previous comand, you will learn the coverage(enum) json-schemas with task `rake fitting:documentation_responses[m]`
-For details `rake fitting:documentation_responses_error[m]`
+This report will be available and properly documented in the next major update, but you already can try it by running:   
 
-### l size
+```bash
+bundle e rake fitting:report
+```
 
-In addition to the previous comand, you will learn the coverage(oneOf) json-schemas with task `rake fitting:documentation_responses[l]`
-For details `rake fitting:documentation_responses_error[l]`
+Using this you can document API prefixes. 
+The task will create JSON (`fitting/report.json`) and HTML (`fitting/index.html`) reports.
 
-## Check tests cover
+## Tests coverage
 
-### xs size
+Only `xs` size is available for tests coverage:
 
-`rake fitting:tests_responses[xs]`
+```bash
+rake fitting:tests_responses[xs]
+```
 
 ## Config
 
-You can specify the settings either in a yaml file `.fitting.yml` or in config.
-If your project uses several prefixes, for each one you need to create a separate yaml file in the folder `fitting` (`fitting/*.yml`).
+You can specify the settings either in a YAML file `.fitting.yml` or in a config.
+If your project uses several prefixes, for each one you should create a separate YAML file in the folder `fitting` (`fitting/*.yml`).
+
+All the available config options are described below.
 
-### apib_path
+### `apib_path`
 
-Path to API Blueprint v3 documentation. There must be an installed [drafter](https://github.com/apiaryio/drafter) to parse it.
+Path to API Blueprint v3 documentation. 
+There must be an installed [drafter](https://github.com/apiaryio/drafter) to parse it.
 
-### drafter_yaml_path
+### `drafter_yaml_path`
 
-Path to API Blueprint v3 documentation pre-parsed with `drafter` and saved to a YAML file.
+Path to API Blueprint v3 documentation, pre-parsed with `drafter` and saved to a YAML file.
 
-### drafter_4_apib_path
+### `drafter_4_apib_path`
 
-Path to API Blueprint v4 documentation. There must be an installed [drafter](https://github.com/apiaryio/drafter) to parse it.
+Path to API Blueprint v4 documentation. 
+There must be an installed [drafter](https://github.com/apiaryio/drafter) to parse it.
 
-### drafter_4_yaml_path
+### `drafter_4_yaml_path`
 
-Path to API Blueprint v4 documentation pre-parsed with `drafter` and saved to a YAML file.
+Path to API Blueprint v4 documentation, pre-parsed with `drafter` and saved to a YAML file.
 
-### crafter_apib_path
+### `crafter_apib_path`
 
 Path to API Blueprint v4 documentation.
 
-### crafter_yaml_path
+### `crafter_yaml_path`
 
-Path to API Blueprint v4 documentation pre-parsed with `crafter` and saved to a YAML file.
+Path to API Blueprint v4 documentation, pre-parsed with `crafter` and saved to a YAML file.
 
-### tomogram_json_path
+### `tomogram_json_path`
 
-Path to Tomogram documentation pre-parsed with [tomograph](https://github.com/funbox/tomograph) and saved to a JSON file.
+Path to Tomogram documentation, pre-parsed with [tomograph](https://github.com/funbox/tomograph) and saved to a JSON file.
 
-### strict
+### `strict`
 
-Default `false`. If `true` then all properties are condisidered to have `"required": true` and all objects `"additionalProperties": false`.
+Default: `false`
 
-### prefix
+When `true` all properties are considered to have `"required": true` and all objects are considered to have `"additionalProperties": false`.
 
-Prefix of API requests. Example: `'/api'`. Validation will not be performed if the request path does not start with a prefix.
+### `prefix`
 
-### white_list
+Prefix for API requests. E.g. `'/api'`. Validation will not be performed if the request path does not start with a prefix.
 
-Default: all paths. This is an array of paths that are mandatory for implementation.
-This list does not affect the work of the matcher.
-This list is only for the report in the console.
+### `white_list`
+
+Default: all paths
+ 
+This is an array of paths that are mandatory for implementation.
+The list does not affect the work of the matcher.
+It's used for the CLI report only.
 
 ```yaml
 white_list:
@@ -237,13 +260,15 @@ white_list:
   /sessions: []
 ```
 
-Empty array `[]` means all methods.
+Empty array (`[]`) means all methods.
 
-### resource_white_list
+### `resource_white_list`
 
-Default: all resources. This is an array of resources that are mandatory for implementation.
-This list does not affect the work of the matcher.
-This list is only for the report in the console.
+Default: all resources
+
+This is an array of resources that are mandatory for implementation.
+The list does not affect the work of the matcher.
+It's used for the CLI report only.
 
 ```yaml
 resource_white_list:
@@ -257,31 +282,35 @@ resource_white_list:
   /sessions: []
 ```
 
-Empty array `[]` means all methods.
+Empty array (`[]`) means all methods.
+
+### `json_schema_cover`
+
+Default: false
 
-### json_schema_cover
+JSON-schema covering becomes mandatory.
+However, if you don't use `Fitting.statistics` you can call `responses.statistics.cover_save`.
 
-Default: false. Json-schema covering becomes mandatory.
-Or you can call `responses.statistics.cover_save` if you don't use call `Fitting.statistics`.
+### `include_resources`
 
-### include_resources
+Default: all resources (but only when `include_resources` and `include_actions` are not defined)
 
-Default: all resources if  `include_resources` and `include_actions` is not used.
 This is an array of resources that are mandatory for implementation.
-This list does not affect the work of the matcher.
-This list is only for the report in the console.
+The list does not affect the work of the matcher.
+It's used for the CLI report only.
 
 ```yaml
 include_resources:
   - /sessions
 ```
 
-### include_actions
+### `include_actions`
+
+Default: all paths (but only when `include_resources` and `include_actions` are not defined)
 
-Default: all paths if `include_resources` and `include_actions` is not used.
 This is an array of paths that are mandatory for implementation.
-This list does not affect the work of the matcher.
-This list is only for the report in the console.
+The list does not affect the work of the matcher.
+It's used for the CLI report only.
 
 ```yaml
 include_actions:
@@ -292,9 +321,9 @@ include_actions:
   - GET /users/{id}/employees
 ```
 
-### ignore_list
+### `ignore_list`
 
-You can use ignore list for omit checks with matchers.
+You can use ignore list to omit checks with matchers.
 
 ```yaml
 ignore_list:
@@ -302,12 +331,25 @@ ignore_list:
   - %r{/api/v1/comments}
 ```
 
-It works only for match_schema (NOT FOR strictly_match_schema)
+It works only for `match_schema` and **not** for `strictly_match_schema`.
+
+### `prefixes`
+
+Example:
+
+```yaml
+prefixes:
+  - name: /api/v1
+  - name: /api/v2
+```
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/funbox/fitting. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+Bug reports and pull requests are welcome on GitHub at [github.com/funbox/fitting](https://github.com/funbox/fitting).
+This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
 
 ## License
 
 The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
+
+[![Sponsored by FunBox](https://funbox.ru/badges/sponsored_by_funbox_centered.svg)](https://funbox.ru)