Skip to main content

RoboZap

Documentation for test library RoboZap.

Installing

  • Install RoboZap libraries into the virtualenv with pip install RoboZap

Importing

Arguments: [proxy]

ZAP Library can be imported with one argument

Arguments: - proxy: Proxy is required to initialize the ZAP Proxy at that location. Must include PortSpec - port: Port is required to be set as a global/suite variable for the rest of the suite to access location

Examples:

| = Keyword Definition = | = Description = |

| Library |RoboZap | proxy| port |

Major Keywords

Start Headless Zap

Arguments: [path]

Start OWASP ZAP without a GUI

Examples:

| start headless zap | path |

Start GUI Zap

Arguments: [path]

Start OWASP ZAP without a GUI

Examples:

| start gui zap | path |

Zap Define Context

Arguments: [contextname, url]

Add Target to a context and use the context to perform all scanning/spidering operations

Examples:

| zap define context | contextname | target |

Zap Open Url

Arguments: [url]

Invoke URLOpen with ZAP

Examples:

| zap open url | target |

Zap Scan Status

Arguments: [scan_id]

Fetches the status for the spider id provided by the user

Examples:

| zap scan status | scan_id |

Zap Shutdown

Arguments: []

Shutdown process for ZAP Scanner

Zap Spider Status

Arguments: [spider_id]

Fetches the status for the spider id provided by the user Examples: | zap spider status | spider_id |

Zap Start Ascan

Arguments: [context, url, policy=Default Policy]

Initiates ZAP Active Scan on the target url and context

Examples:

| zap start ascan | context | url |

Zap Start Spider

Arguments: [target, url]

Start ZAP Spider with ZAP's inbuilt spider mode

Examples:

| zap start spider | target | url |

Zap Write To Json File

Arguments: [scan_id]

Fetches all the results from zap.core.alerts() and writes to json file.

Examples:

| zap write to json | scan_id |

Zap Generate Report (Export Report Plugin)

Arguments: [file_path, report_format, report_title, report_author]

Uses the Export Report from ZAP to generate reports in multiple formats.

  • file_path: needs to be an absolute path and include the file name with extension.
  • format: can be json|xml|xhtml|pdf|doc
  • report title: Any title you deem fit for the exported report
  • report auhor: Any name you want for the author of the report

Examples:

| zap export report | file_path | format | report title | report author

Metadata

Release files for RoboZap 1.3.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for RoboZap 1.3.3
File Size Uploaded Provenance
RoboZap-1.3.3.tar.gz 5.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for RoboZap 1.3.3
File Interpreter ABI Platform
RoboZap-1.3.3-py3-none-any.whl Python 3 none any Details

Total release size: 10.8 kB

Release files / RoboZap-1.3.3.tar.gz

Download URL RoboZap-1.3.3.tar.gz
Size 5.2 kB
Tags Source
SHA-256 checksum
How to use checksums
1d3fb6824eccc367ca4d2672fb987c811c8df15dbfde7f7121cb6431ccbc716e
BLAKE2b-256 checksum
How to use checksums
9214e1158ef6183a307fd7dd44dc98267065397ff86461824b8a8e0e152557b9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.4

Release files / RoboZap-1.3.3-py3-none-any.whl

Download URL RoboZap-1.3.3-py3-none-any.whl
Size 5.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6b3290628d1b41431020c1f19f1a80992c31b0ddb0ee8296478db3f26035be57
BLAKE2b-256 checksum
How to use checksums
14441dbdcbe60581bd5243407e9939fa4fd95c2337e42b0c3ce31a5512c76b32
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.4

Security for RoboZap 1.3.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page