tftsr-devops_investigation/node_modules/webdriverio/build/commands/browser/addCommand.d.ts
Shaun Arman 8839075805 feat: initial implementation of TFTSR IT Triage & RCA application
Implements Phases 1-8 of the TFTSR implementation plan.

Rust backend (Tauri 2.x, src-tauri/):
- Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama
- PII detection engine: 11 regex patterns with overlap resolution
- SQLCipher AES-256 encrypted database with 10 versioned migrations
- 28 Tauri IPC commands for triage, analysis, document, and system ops
- Ollama: hardware probe, model recommendations, pull/delete with events
- RCA and blameless post-mortem Markdown document generators
- PDF export via printpdf
- Audit log: SHA-256 hash of every external data send
- Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2)

Frontend (React 18 + TypeScript + Vite, src/):
- 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings
- 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives
- 3 Zustand stores: session, settings (persisted), history
- Type-safe tauriCommands.ts matching Rust backend types exactly
- 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs)

DevOps:
- .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push
- .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload

Verified:
- cargo check: zero errors
- tsc --noEmit: zero errors
- vitest run: 13/13 unit tests passing

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
2026-03-14 22:36:25 -05:00

63 lines
2.3 KiB
TypeScript

export {};
/**
* The browser method `addCommand` helps you to write your own set of commands.
*
* :::info
*
* You can find more information on adding custom commands in the [custom command](/docs/customcommands#adding-custom-commands) guide.
*
* :::
*
* <example>
:execute.js
// Basic usage with browser scope
await browser.addCommand('getUrlAndTitle', async function (customParam) {
// `this` refers to the `browser` scope
return {
url: await this.getUrl(),
title: await this.getTitle(),
customParam: customParam
}
})
// Element scope using options object (RECOMMENDED)
await browser.addCommand('waitAndClick', async function () {
// `this` refers to the `element` scope
await this.waitForClickable()
await this.click()
}, { attachToElement: true })
// Advanced usage with options
await browser.addCommand('fastClick', async function () {
// `this` refers to the `element` scope
await this.click()
}, {
attachToElement: true,
disableElementImplicitWait: true // Skip implicit wait for faster execution
})
//usage
it('should use my add command', async () => {
await browser.url('https://webdriver.io')
const result = await browser.getUrlAndTitle('foobar')
assert.strictEqual(result.url, 'https://webdriver.io')
assert.strictEqual(result.title, 'WebdriverIO · Next-gen browser and mobile automation test framework for Node.js | WebdriverIO')
assert.strictEqual(result.customParam, 'foobar')
// Using element commands
const element = await $('button')
await element.waitAndClick()
await element.fastClick()
})
* </example>
* @alias browser.addCommand
* @param {string} name name of the custom command
* @param {Function} callback function to be called
* @param {Boolean|Object=} options **DEPRECATED when Boolean (elementScope)**. Options object with the following properties:
* @param {Boolean=} options.attachToElement extend the Element object instead of the Browser object
* @param {Boolean=} options.disableElementImplicitWait disable implicit wait for element commands
* @type utility
*
*/
//# sourceMappingURL=addCommand.d.ts.map