Download the PHP package instaclick/gherkincs without Composer
On this page you can find all versions of the php package instaclick/gherkincs. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download instaclick/gherkincs
More information about instaclick/gherkincs
Files in instaclick/gherkincs
Package gherkincs
Short Description Code Sniffer and Semantic Analyzer for Gherkin
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package gherkincs
Gherkin Code Sniffer
By Juti Noppornpitak
Dependencies
- twig (dev-master, required for HTML report)
Installation
Standalone
At the root directory where Gherkin CS's composer.json is,
Installation (Normal): run composer.phar install
Installation (DEV): run composer.phar install --dev
Executable: cuke-standalone.
Composer with Packagist
Installation: Add "instaclick/gherkincs": "dev-master" in the require or require-dev section of the
project's composer.json.
Executable: vendor/bin/cuke.
Usage
Define cuke as either cuke-standalone or vendor/bin/cuke.
where --html is to produce a set of reports in HTML and --jcs is to produce a checkstyle-format report for Jenkins/Hudson CI.
Please note that:
- by default, the report will be displayed on the standard output,
--htmlwill be used if both--jcsand--htmlare given.
For example,
Available Analyzers
Semantic Analyzer
Context Flow
This analyzer first checks for the given-when-then context flow (precondition-action-assertion) in the following patterns:
Precondition
-> Continuation (as precondition)
-> Action
-> Assertion
Action
-> Continuation (as action)
-> Assertion
Assertion
-> Continuation (as assertion)
-> Precondition
-> ActionSemantic Quality
It also asserts one of the conditions:
- any contexts containing "click", "fill", "follow", or "select" is an action,
- any contexts containing "should" or "must" is an assertion.
When a context does not satisfy two or more conditions, the analyzer will consider it an exception (and emit no warnings).
Coding Style Checker
This analyzer checks if:
- tab characters are not used,
- the width of indentation is consistent where the default width is 4 spaces,
- there exists no trailing spaces,
- features have no leading spaces (no indentation),
- backgrounds, scenarios, and scenario outlines have exactly one level of indentation,
- preconditions, actions, assertions and continuations have exactly two levels of indentation,
- tabular data has exactly three levels of indentation,
- tag lines have at most one level of indentation,
- extra spaces (two or more whitespaces) occur in non-tabular-data contexts.
Instaclick's Coding Style Checker
This analyzer checks if any tags' name must:
- start with @,
- start and end with alphanumeric characters,
- only use hyphens ("-"),
- be in lowercase.
Write a Custom Analyzer
All analyzers must implement IC\Gherkinics\Analyzer\AnalyzerInterface.
