pickleib

Unify Cucumber/Gherkin test automation across web, mobile, desktop, API, and database platforms.

12|13|Updated Sep 3, 2021
One-click install
npx skills add https://github.com/Umutayb/pickleib --skill pickleib
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pickleib
Source: https://github.com/Umutayb/pickleib/tree/main/skills/pickleib
Command: npx skills add https://github.com/Umutayb/pickleib --skill pickleib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone work of writing platform-specific test automation code for web, mobile, desktop, API and database testing, removing boilerplate and ensuring consistent, maintainable test suites.

Core Features & Use Cases

  • Unified Cross-Platform Testing: Write a single set of Cucumber/Gherkin steps that run across web, mobile and desktop environments using Pickleib's polymorphic interface, no need to rewrite interaction logic for each platform.
  • Flexible Element Definition: Support for both low-code JSON page repositories for quick, no-code element management and classic Java Page Object Model with @FindBy annotations for more complex implementations.
  • Built-In Test Utilities: Pre-built Cucumber steps for clicks, form fills, verifications, waits, and context management, plus automated driver lifecycle handling, self-healing element interactions, and thread-safe parallel execution support.
  • Use Case: A QA engineer can write a single login test scenario that works for both a web application and a mobile app, using the same step syntax and only updating element selectors for each platform.

Quick Start

Use the pickleib skill to generate a compliant Gherkin test scenario for your application's user flow, including approved element definitions and step syntax that matches the Pickleib Step Library.

Frequently Asked Questions about pickleib

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write cross-platform Cucumber tests that run on web, mobile, and desktop without duplicating interaction logic?

Cross-platform Cucumber tests use a polymorphic interaction interface to execute Gherkin steps across web, mobile, and desktop environments. This approach eliminates platform-specific test automation code by providing a unified interaction layer that requires only element selector updates per platform.

Can I use a low-code JSON element repository instead of Java Page Object Model for test automation?

Low-code JSON element repositories are supported for quick, no-code element management alongside classic Java Page Object Model implementations using @FindBy annotations. This flexible element definition allows QA engineers to choose between rapid low-code configurations and complex Java structures.

Does Selenium support self-healing element interactions and automated driver lifecycle management for Gherkin step execution?

Selenium-based test automation can support self-healing element interactions and automated driver lifecycle management through built-in test utilities. These features handle driver setup and teardown automatically while maintaining thread-safe parallel execution for Cucumber test suites.

What is the best way to manage API and database testing within a Cucumber test suite?

Managing API and database testing within a Cucumber suite is best handled through a unified testing interface that provides pre-built Gherkin steps for verifications and context management. This removes the need to write separate platform-specific automation code for API and database validations.

Do I need Appium to run mobile test automation steps using the same Gherkin syntax as web tests?

Appium is required for mobile test automation when executing cross-platform Gherkin steps that target mobile environments. The unified polymorphic interface leverages Appium alongside Selenium to ensure the same Cucumber step syntax works across both web and mobile applications.