JarCasting
JarCasting JarCasting

io.github.multicatch:cucumber-audit-scenarios

Easy automated auditing with preconfigured step definitions.

License

License
Categories

Categories

Cucumber Application Testing & Monitoring
GroupId

GroupId

io.github.multicatch
ArtifactId

ArtifactId

cucumber-audit-scenarios
Last Version

Last Version

1.0.3
Release Date

Release Date
Type

Type

jar
Description

Description

Easy automated auditing with preconfigured step definitions.

Download cucumber-audit-scenarios

Filename Size
cucumber-audit-scenarios-1.0.3.pom
cucumber-audit-scenarios-1.0.3.jar 5 KB
cucumber-audit-scenarios-1.0.3-sources.jar 5 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/io.github.multicatch/cucumber-audit-scenarios/ -->
<dependency>
    <groupId>io.github.multicatch</groupId>
    <artifactId>cucumber-audit-scenarios</artifactId>
    <version>1.0.3</version>
</dependency>
// https://jarcasting.com/artifacts/io.github.multicatch/cucumber-audit-scenarios/
implementation 'io.github.multicatch:cucumber-audit-scenarios:1.0.3'
// https://jarcasting.com/artifacts/io.github.multicatch/cucumber-audit-scenarios/
implementation ("io.github.multicatch:cucumber-audit-scenarios:1.0.3")
'io.github.multicatch:cucumber-audit-scenarios:jar:1.0.3'
<dependency org="io.github.multicatch" name="cucumber-audit-scenarios" rev="1.0.3">
  <artifact name="cucumber-audit-scenarios" type="jar" />
</dependency>
@Grapes(
@Grab(group='io.github.multicatch', module='cucumber-audit-scenarios', version='1.0.3')
)
libraryDependencies += "io.github.multicatch" % "cucumber-audit-scenarios" % "1.0.3"
[io.github.multicatch/cucumber-audit-scenarios "1.0.3"]

Dependencies

compile (3)

Group / Artifact Type Version
io.github.multicatch : cucumber-audit-variables jar 1.0.3
com.fasterxml.jackson.core : jackson-annotations jar 2.12.1
org.jetbrains.kotlin : kotlin-stdlib-jdk8 jar 1.4.30

test (10)

Group / Artifact Type Version
io.github.multicatch : cucumber-audit-junit jar 1.0.3
io.github.multicatch : cucumber-audit-stepdefs jar 1.0.3
org.junit.jupiter : junit-jupiter jar 5.6.0
org.junit.vintage : junit-vintage-engine jar 5.6.0
com.google.inject : guice jar 4.2.2
io.cucumber : cucumber-guice jar 5.5.0
com.google.guava : guava jar 29.0-jre
ch.qos.logback : logback-classic jar 1.2.3
de.monochromata.cucumber : reporting-plugin jar 4.0.42
org.jetbrains.kotlin : kotlin-test jar 1.4.30

Project Modules

There are no modules declared in this project.

cucumber-audit

Quality Gate Status SonarCloud Coverage

Easy automated auditing with preconfigured step definitions.

This project aims to provide an easy way for configuring an automated audit or web application test using Selenium and Cucumber.

Features

  • write audit scenarios using natural language (Gherkin) thanks to Cucumber
  • explore your application and inspect responses thanks to Selenium
  • use prepared step definitions for writing scenarios without Java/Kotlin knowledge
  • use variable substitution in feature files
  • manipulate or inspect HTTP requests and responses thanks to browsermob-proxy

Full Documentation

Available here

Sample Scenario

By using predefined steps from this project, you can build a feature like the following:

Feature: Example Feature

  Scenario: An Expected Response
    Given app running on "https://httpbin.org" has already started
    And the response content is under inspection
    When I go to "https://httpbin.org"
    Then the response should contain "A simple HTTP Request &amp; Response Service."

Feel free to extend it with more steps, comments or annotations:

  @InformationDisclosure
  Scenario: Exploitation of System Software Information In Headers
  The disclosure of software information may be used to provide knowledge about known vulnerabilities of
  a particular version. The "Server" and "X-Powered-By" headers provide information about technology that
  is used on the server side. Disabling them makes it more difficult to exploit the server software.

    Given the response headers are under inspection
    When I go to "$auth_application_url"
    Then the "Server" response header should not contain numbers
    And the "X-Powered-By" response header should not contain numbers

Running Sample Scenarios

The scenarios are available here.

Download a Selenium Gecko driver and run the following command in the project directory:

mvn test -DfailIfNoTests=false -Dtest=CucumberTest -Dwebdriver.gecko.driver=/path/to/geckodriver

Running It Standalone

You can run it standalone using jar build in cucumber-audit-standalone module.

Example:

java -jar cucumber-audit-standalone.jar path/to/features \
  --glue io.github.multicatch.cucumber.audit \
  --plugin pretty \
  --webdriver.type GECKO \
  --webdriver.gecko.driver path/to/geckodriver \
  --webdriver.headless true

Instead of path/to/features provide a path to your *.feature files.

Other options:

  • webdriver.type - specify type of the webdriver used (GECKO/CHROME)
  • webdriver.gecko.driver - specify location of the geckodriver binary
  • webdriver.chrome.driver - specify location of the chromedriver binary
  • webdriver.headless - specify whether to start browser in the headless or not (true/false)

You can also use options available in cucumber standalone. To see them use --help.

To use variable substitution plugin, use --plugin io.github.multicatch.cucumber.audit.variables.VariableResolvingRedactor option. Variables will be read from the environment.

Pretty reports

This project uses de.monochromata.cucumber:reporting-plugin to generate pretty reports.

By default, pretty html reports are generated into cucumber-audit-scenarios/target/cucumber/cucumber-html-reports directory.

Reports are automatically deployed and available here:

Versions

Version
1.0.3
1.0.2
1.0.1
1.0.0