Skip to content

Simplify how a new keyword gets registered across entry points #484

Description

@chinmayajha

Adding a keyword today touches several places before it is usable everywhere:

  • method on the API class (ActionKeyword / AppManagement / Verifier / FlowControl)
  • @with_self_healing decorator if it locates an element
  • wrapper on optics.py:Optics with @keyword(...)
  • TestFrameworkGenerator.keyword_registry dict in helper/generate.py
  • keyword_registry set inside YAMLDataReader.read_modules
  • docs

That surface area is easy to get wrong (SDK/runner drift has happened before). This issue tracks ideas to make registration simpler, e.g. deriving the generate.py registries from the API classes automatically, or generating the optics.py wrapper from a single source of truth.

Raised during review of #483.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions