Skip to content

Latest commit

 

History

History
79 lines (45 loc) · 4.13 KB

File metadata and controls

79 lines (45 loc) · 4.13 KB
graph LR
    Test_Definition_API["Test Definition API"]
    Optics["Optics"]
    ActionKeyword["ActionKeyword"]
    Verifier["Verifier"]
    SessionManager["SessionManager"]
    StrategyManager["StrategyManager"]
    Test_Definition_API -- "encompasses" --> Optics
    Test_Definition_API -- "encompasses" --> ActionKeyword
    Test_Definition_API -- "encompasses" --> Verifier
    Optics -- "delegates to" --> ActionKeyword
    Optics -- "delegates to" --> Verifier
    Optics -- "interacts with" --> SessionManager
    ActionKeyword -- "interacts with" --> StrategyManager
    Verifier -- "interacts with" --> StrategyManager
    click Test_Definition_API href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/optics-framework/Test_Definition_API.md" "Details"
Loading

CodeBoardingDemoContact

Details

One paragraph explaining the functionality which is represented by this graph. What the main flow is and what is its purpose.

Test Definition API [Expand]

The overarching subsystem responsible for defining and structuring automated tests. It provides the core interfaces and components for users to create test steps, actions, and verifications, acting as the primary entry point for test script development within the optics_framework.

Related Classes/Methods: None

Optics

The central facade of the Test Definition API. It provides a simplified, unified interface for users to define test steps, orchestrating calls to ActionKeyword and Verifier components. It acts as the primary entry point for test script creation.

Related Classes/Methods:

ActionKeyword

Represents atomic, user-defined actions that interact with the application under test (e.g., click, type, swipe). It encapsulates the logic for performing specific operations.

Related Classes/Methods:

Verifier

Represents user-defined verification steps used to assert expected outcomes or states within the application under test (e.g., assert text present, assert image visible). It encapsulates the logic for validating test results.

Related Classes/Methods:

SessionManager

Manages the lifecycle of test sessions, including initialization, teardown, and state management. It provides the necessary context for Optics to interact with the underlying execution environment.

Related Classes/Methods:

StrategyManager

Responsible for performing the actual element location, content detection, or other interaction strategies required by ActionKeyword and Verifier components. It abstracts the complexities of vision, AI, and driver interactions.

Related Classes/Methods: