Decoding f(x,y)=z: Understanding the Architecture of FoXYiZs

At the heart of the FoXYiZs framework lies a simple yet powerful formula: f(x,y) = z. To effectively participate in the bug bounty program, it is essential to understand how these components work together to create a seamless automation workflow.

The Four Pillars of FoXYiZs:

F (Engine): This is the core backend, including the engine.py and actions.py files that execute the automation.

X (Capabilities): These are the pre-built functions—such as clicking, navigating, or API calls—that the engine can perform. Currently, the framework supports dozens of actions across UI, API, and even SAP.

Y (Tasks/Wipads): This is where you define your test logic using a 'Wipad' structure consisting of Plans, Actions, and Designs.

• Plans outline the test cases.
• Actions are the specific steps linked to capabilities.
• Designs represent the data layer, allowing you to run the same tests across different environments or user scenarios.

Z (Results): Every execution generates 'Z' results—detailed logs, CSV error reports, and HTML dashboards that provide visual analytics of what passed or failed.

Execution Flexibility

FoXYiZs is designed to be versatile. You can run tests locally using a Command Line Interface (CLI) or a Graphic User Interface (GUI), or you can use the Cloud version hosted on AWS EC2 for headless execution. This structure removes the coding barrier, making high-level automation accessible to everyone.