agentsclimarketplace

Gavel appium

Skill dsolisp/gavel/skills/gavel-appium

Appium mobile-native framework profile for gavel (C# / .NET client). AppiumBy locator priority, native waits, fixture DI, POM composition, and dotnet test run commands. Activated by gavel-detect when Appium.WebDriver appears in *.csproj.From its SKILL.md

Install
npx -y skills add dsolisp/gavel --skill gavel-appium

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

7.4 KB, as published. Nobody here has run it

Gavel Appium Profile

Appium-specific bindings for the .NET client. Universal POM/workflow rules: gavel + gavel-e2e.

Java/Kotlin: see gavel-appium-java.

Current release (as of 2026-07-01): Appium.WebDriver 8.3.2

Appium.WebDriver depends on Selenium.WebDriver, so it is a superset of the Selenium C# client. When both packages appear in *.csproj, gavel-detect selects gavel-appium (Appium wins the precedence check). Mobile-native tests target physical/emulated devices — there are no URLs to navigate, so selector strategy and waits carry the whole reliability burden.

Locator Priority

Prefer stable, platform-agnostic accessibility strategies. XPath is the last resort (slow, brittle against layout churn).

// 1st — cross-platform accessibility id (maps to content-desc / a11y label)
driver.FindElement(AppiumBy.AccessibilityId("submit-button"));

// 2nd — platform-native engine when no accessibility id exists
driver.FindElement(AppiumBy.AndroidUIAutomator(
    "new UiSelector().resourceId(\"com.app:id/submit\")"));
driver.FindElement(AppiumBy.IosNsPredicate("label == 'Submit'"));
driver.FindElement(AppiumBy.IosClassChain("**/XCUIElementTypeButton[`label == 'Submit'`]"));

// last resort — XPath (avoid; recompute on every layout change)
driver.FindElement(AppiumBy.XPath("//android.widget.Button[@text='Submit']"));

Legacy MobileBy.* is deprecated — prefer AppiumBy.*.

Selector Boundary

Only locator classes call FindElement / AppiumBy.*. Actions and specs call named locator properties or methods. Inline AppiumBy / FindElement chains in actions or tests are a selector-leak.

// GOOD — locator layer owns the strategy
public sealed class LoginLocators
{
    private readonly AppiumDriver _driver;
    public LoginLocators(AppiumDriver driver) => _driver = driver;
    public IWebElement SubmitButton => _driver.FindElement(AppiumBy.AccessibilityId("submit-button"));
    public IWebElement ErrorBanner => _driver.FindElement(AppiumBy.AccessibilityId("error-banner"));
}

Waits and Assertions

Native WebDriverWait only. No Thread.Sleep / Task.Delay with a fixed duration (manual-wait).

var wait = new WebDriverWait(driver, TimeSpan.FromSeconds(10));
var banner = wait.Until(d => d.FindElement(AppiumBy.AccessibilityId("error-banner")));
Assert.That(banner.Text, Is.EqualTo("Invalid credentials"));

Signal-driven sync (ManualResetEventSlim / TaskCompletionSource) is allowed only when a readiness owner calls Set() — an unset gate is a renamed sleep, not remediation. Mirror the Playwright.NET wait policy.

DI via Fixtures

Inject the driver and page objects through NUnit [SetUp], xUnit IClassFixture<T> / constructor injection, or MSTest [TestInitialize] — do not new LoginPage(driver) inside a test body (no-di).

// xUnit — constructor injection via IClassFixture
public class LoginTests : IClassFixture<AppiumFixture>
{
    private readonly LoginPage _login;
    public LoginTests(AppiumFixture fixture) => _login = fixture.LoginPage;

    [Fact]
    public void RejectsBadCredentials() => _login.SubmitInvalid();
}

POM: Class-Based Composition

public sealed class LoginPage
{
    public LoginPage(AppiumDriver driver)
    {
        Locators = new LoginLocators(driver);
        Actions = new LoginActions(Locators);
    }
    public LoginLocators Locators { get; }
    public LoginActions Actions { get; }
}

Run Commands

dotnet build
dotnet test
dotnet test --filter "FullyQualifiedName~LoginTests"
# Appium server must be running (appium) with a device/emulator attached.
appium --address 127.0.0.1 --port 4723

Release Highlights (Appium.WebDriver 8.3.x)

AreaChange
Selenium baseTracks Selenium.WebDriver 4.x — shares WebDriverWait, By, BiDi plumbing
LocatorsAppiumBy is the canonical builder; MobileBy deprecated
W3CActions API for gestures (OpenQA.Selenium.Interactions) over legacy TouchAction
DriversUiAutomator2 (Android) / XCUITest (iOS) are the supported first-party drivers
SessionsServer-side plugin model; client stays thin over the W3C protocol

Gestures

Use the W3C Actions API, not the deprecated TouchAction/MultiTouch:

var finger = new PointerInputDevice(PointerKind.Touch, "finger");
var swipe = new ActionSequence(finger);
swipe.AddAction(finger.CreatePointerMove(CoordinateOrigin.Viewport, 200, 800, TimeSpan.Zero));
swipe.AddAction(finger.CreatePointerDown(MouseButton.Left));
swipe.AddAction(finger.CreatePointerMove(CoordinateOrigin.Viewport, 200, 200, TimeSpan.FromMilliseconds(300)));
swipe.AddAction(finger.CreatePointerUp(MouseButton.Left));
driver.PerformActions(new List<ActionSequence> { swipe });

Wrap gestures behind action methods — never inline coordinates in a spec.

Hybrid Web Context

Hybrid apps embed a webview inside the native shell. Switch context to interact with web content, then switch back:

// Native → webview
driver.Context = "WEBVIEW_com.example";
// interact with web elements via named locators (same selector boundary)
driver.Context = "NATIVE_APP";

After switching to a webview context the selector-leak rule still applies: FindElement, CSS selectors, and XPath in actions or specs are leaks. Locators live in locator classes regardless of context. Do not inline FindElement(By.CssSelector(...)) in an action just because the context changed — expose it as a named locator property.

Reference: AGENTS.md — Selector Boundary Rule, Page Object Discipline.

Skip / Ignore Markers

[Ignore("PROJ-123: emulator unavailable in CI")]   // NUnit — reason + ticket
Assert.Ignore("PROJ-456: known iOS regression");     // same policy
[Fact(Skip = "PROJ-789: flaky on UiAutomator2")]      // xUnit — reason required

Bare [Ignore], Assert.Ignore() without reason, or [Fact(Skip = "")] → skip-marker / ignore-no-reason.

Anti-Patterns

Manual Waits

Wrong: Fixed sleep to "let the screen settle".

// BAD
Thread.Sleep(3000);
Assert.That(locators.ErrorBanner.Text, Is.EqualTo("Invalid credentials"));

Right: Explicit WebDriverWait on the observable condition.

// GOOD
var wait = new WebDriverWait(driver, TimeSpan.FromSeconds(10));
var banner = wait.Until(d => locators.ErrorBanner);
Assert.That(banner.Text, Is.EqualTo("Invalid credentials"));

Reference: AGENTS.md — Test Constitution (WON'T DO) #2: no fixed sleeps.

Selector Leaks

Wrong: AppiumBy / FindElement in a spec or action.

// BAD — strategy in the test
driver.FindElement(AppiumBy.AccessibilityId("submit-button")).Click();

Right: Locator class owns the strategy; specs call named members.

// GOOD
locators.SubmitButton.Click();

Reference: AGENTS.md — Selector Boundary Rule, Page Object Discipline.

Gesture Leaks

Wrong: Raw coordinate math and PerformActions inside a test body.

Right: Expose actions.SwipeToRefresh() — the spec states intent, the action owns the coordinates.

Reference: AGENTS.md — QA Ladder rung 3 (native waits), Page Object Discipline.

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.