Unified workflow engine: step-machine (sequential) + event-graph (stateless DAG) with pluggable storage
The declarative YAML flow execution engine for automating terminal sequences within `mcp-tuikit`. It parses predefined execution scripts, allowing AI agents or CI environments to orchestrate complex multi-step interactions (e.g., sending keys, waiting for
Convert Gherkin .feature files into Maestro YAML flow files for mobile testing
JavaScript parser and stringifier for YAML
YAML 1.2 parser and serializer
Prettier is an opinionated code formatter
YAML 1.2 parser and serializer
A JavaScript parser built from the Hermes engine
Read and parse a YAML file
TypeScript definitions for js-yaml
Allow parsing of the flow syntax
Strip flow type annotations from your output code.
Use Environment Variables in String
A YAML parser that produces output compatible with ESLint
Extract YAML front matter from a string
Useful functions when working with YAML.
JavaScript parser written in OCaml. Produces ESTree AST
Babel transform for Flow Enums.
Babel preset for all Flow plugins.
Flow types for the Flow-ESTree spec produced by the hermes parser
YAML language support for the CodeMirror code editor
YAML language server
Read and parse a YAML file.
Runtime to be use with the Flow Enums transform.
Flow CI CLI, used to build yaml, run ci yaml locally.
Easily style YAML files using Psych, like Sequence/Mapping Flow style.
QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved? * Elements, such as links, buttons, and other html objects are defined in one location. This ensures over time the user won't have definitions spread out throughout different layers of code requiring time consuming updates if the application under test is modified. * Well defined flows allows the user to have a common means for navigating and controlling interactions with the application under test. This takes all logic out of test classes and yields in higher more modular code re-use. * When an application requiring testing has the elements and flows implemented less code savy resources can easily add new test cases once trained on how to access the flows and elements. * When ever a link or button is clicked a screen shot is taken * Results are available under site/results directory in html format. Report includes the rdoc on a per test class method along with any screen shots taken. Example report: https://cyberconnect.biz/opensource/demo_results.html * Transparent remote Unix command execution leading to well defined interfaces for common task. For example, one may have a class defined specifically for RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown, etc. This class then would be able to perform these task on any remote Unix machine. * Executes the same on Windows or Linux/Unix environments. Developers have the freedom to develop on the platform of choice. * Mechanize extension: Allows the user to define a web application's page elements in a YAML format and provide navigation paths accessing the YAML structure to interact with the web application. Users can also perform direct http.post or any other mechanize functionality when defining state-full interfaces to hit a web application without going through a browser.
swagger23 converts Swagger 2.0 (OAS 2) API specifications into OpenAPI 3.0.3 (OAS 3) specifications. Accepts JSON or YAML input, produces JSON or YAML output. Works as a Ruby library (Swagger23.convert) or a standalone CLI tool (swagger23). Handles paths, parameters, requestBody, components/schemas, securitySchemes, servers, $ref rewriting, collectionFormat, x-nullable, discriminator, OAuth2 flows, and file uploads. No external runtime dependencies. Safe for large specs.
No description provided.
No description provided.
No description provided.
No description provided.