@browserstack/mcp-server 2.2.6-beta.2 → 2.2.6

package/dist/tools/accessiblity-utils/paginate.d.ts

@@ -1,27 +0,0 @@
-/**
- * How a report's issues are handed out: most severe first, in pages measured by the length
- * of their JSON, so that a page fits a client's context whatever the rows contain. The
- * cursor an agent passes back is the character offset the next page starts at.
- */
-/** Most severe first; an unknown severity sorts last. */
-export declare function sortBySeverity<T extends {
-    severity: string;
-}>(rows: T[]): T[];
-/**
- * How many characters of issue JSON one call hands out by default: about 2,500 tokens, so
- * a page stays small next to a client's own limit on tool output while a large report
- * still takes few calls.
- */
-export declare const PAGE_CHARACTERS = 10000;
-export interface Page<T> {
-    records: T[];
-    page_length: number;
-    /** Character offset of the next page, or null when this was the last. */
-    next_page: number | null;
-    /** How many rows the pages after this one hold. */
-    remaining: number;
-}
-export declare function pageOf<T>(all: T[], { maxCharacterLength, nextPage }?: {
-    maxCharacterLength?: number | undefined;
-    nextPage?: number | undefined;
-}): Page<T>;

package/dist/tools/accessiblity-utils/paginate.js

@@ -1,50 +0,0 @@
-/**
- * How a report's issues are handed out: most severe first, in pages measured by the length
- * of their JSON, so that a page fits a client's context whatever the rows contain. The
- * cursor an agent passes back is the character offset the next page starts at.
- */
-const SEVERITY_ORDER = {
-    critical: 0,
-    serious: 1,
-    moderate: 2,
-    minor: 3,
-};
-/** Most severe first; an unknown severity sorts last. */
-export function sortBySeverity(rows) {
-    return rows.sort((a, b) => (SEVERITY_ORDER[a.severity] ?? 99) - (SEVERITY_ORDER[b.severity] ?? 99));
-}
-/**
- * How many characters of issue JSON one call hands out by default: about 2,500 tokens, so
- * a page stays small next to a client's own limit on tool output while a large report
- * still takes few calls.
- */
-export const PAGE_CHARACTERS = 10_000;
-export function pageOf(all, { maxCharacterLength = PAGE_CHARACTERS, nextPage = 0 } = {}) {
-    // Walk to the starting offset
-    let charCursor = 0;
-    let idx = 0;
-    for (; idx < all.length; idx++) {
-        const len = JSON.stringify(all[idx]).length;
-        if (charCursor + len > nextPage)
-            break;
-        charCursor += len;
-    }
-    // Collect up to maxCharacterLength; a row larger than that still makes a page of its
-    // own, or the cursor would never move past it
-    const page = [];
-    for (let i = idx; i < all.length; i++) {
-        const recStr = JSON.stringify(all[i]);
-        const fits = charCursor - nextPage + recStr.length <= maxCharacterLength;
-        if (!fits && page.length > 0)
-            break;
-        page.push(all[i]);
-        charCursor += recStr.length;
-    }
-    const remaining = all.length - idx - page.length;
-    return {
-        records: page,
-        page_length: page.length,
-        next_page: remaining > 0 ? charCursor : null,
-        remaining,
-    };
-}

package/dist/tools/appautomate-utils/appium-sdk/languages/accessibility.d.ts

@@ -1,4 +0,0 @@
-import { AppSDKSupportedLanguage, AppSDKSupportedTestingFramework } from "../index.js";
-/** Says the checks were asked for but not set up, for a framework this setup leaves them off. */
-export declare function getAppAccessibilityNotSetUpInstructions(testingFramework: AppSDKSupportedTestingFramework): string | undefined;
-export declare function getAppAccessibilityChecksInstructions(language: AppSDKSupportedLanguage, testingFramework: AppSDKSupportedTestingFramework): string;

package/dist/tools/appautomate-utils/appium-sdk/languages/accessibility.js

@@ -1,47 +0,0 @@
-// What an App Automate run needs for App Accessibility checks to happen, and how the
-// issues are read afterwards. Each point here cost a run that finished green with no
-// scans and no warning; the SDK says nothing when it decides not to scan.
-import { AppSDKSupportedTestingFrameworkEnum, createStep, } from "../index.js";
-const PYTEST_FIXTURE = `For pytest, create the driver in a fixture (\`conftest.py\`):
-\`\`\`python
-import pytest
-from appium import webdriver
-from appium.options.android import UiAutomator2Options  # XCUITestOptions for iOS
-
-
-@pytest.fixture
-def driver():
-    options = UiAutomator2Options()
-    drv = webdriver.Remote("https://hub.browserstack.com/wd/hub", options=options)
-    yield drv
-    drv.quit()
-\`\`\``;
-/**
- * The frameworks set up without a browserstack.yml whose setup here does not turn App
- * Accessibility on; guidance for a config that was never written would only mislead.
- */
-const NOT_SET_UP = {
-    [AppSDKSupportedTestingFrameworkEnum.nightwatch]: "Nightwatch",
-    [AppSDKSupportedTestingFrameworkEnum.cucumberRuby]: "Cucumber (Ruby)",
-};
-/** Says the checks were asked for but not set up, for a framework this setup leaves them off. */
-export function getAppAccessibilityNotSetUpInstructions(testingFramework) {
-    const label = NOT_SET_UP[testingFramework];
-    if (!label)
-        return undefined;
-    return createStep("App Accessibility checks", `App Accessibility checks are not set up for ${label}: this setup does not turn them on for it, so these tests run without them. To check the app, set the tests up in another framework this tool supports, such as WebdriverIO, pytest, TestNG or JUnit, with accessibility: true.`);
-}
-function driverAdvice(language, testingFramework) {
-    if (language === "python" &&
-        testingFramework === AppSDKSupportedTestingFrameworkEnum.pytest) {
-        return PYTEST_FIXTURE;
-    }
-    return "Create the driver in your framework's setup hook (a fixture, `@BeforeMethod`, `@BeforeEach`, `SetUp`, `before`), not inside the test body.";
-}
-export function getAppAccessibilityChecksInstructions(language, testingFramework) {
-    return createStep("App Accessibility checks: what makes a scan happen, and how to read the issues", `- The SDK decides per test, at the test's start, whether to scan, from the drivers that exist at that moment. A driver created inside the test body is never scanned. ${driverAdvice(language, testingFramework)}
-- Scans run on interaction commands: click/tap, send keys, actions and navigation (such as back). Reads like \`find_elements\` or \`page_source\` do not scan. Interact with every screen state you want scanned.
-- Android 11 or newer, or iOS 14 or newer, is required; older devices are skipped without an error.
-- Under \`platforms\` write the OS version as \`osVersion\`, unquoted (\`osVersion: 14.0\`; not \`platformVersion\`, not \`"14.0"\`): with any other spelling the SDK still runs the tests but App Accessibility records no scans, without a message.
-- When the run ends, the SDK prints the build id as \`testhub id: <id>\` (also the id in its automation.browserstack.com/builds/<id> link). Read the issues with \`fetchAccessibilityIssues\`, \`buildId: <id>\`; it waits while the report is still processing and links the report on the App Accessibility dashboard (https://app-accessibility.browserstack.com/automated-tests). If it reports no scans, it lists the likely causes.`);
-}