vanessa-1c-cookbook skill
PowerShell recipes for headless 1C GUI test runs via Vanessa Automation TestManager, plus a Claude Code skill that solves gotchas absent from the docs
- 4 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Restarts the 1C client process and a scheduler task on the test stand
- Clicks the real TestManager GUI and can activate the wrong window on failure
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/vanessa-1c-cookbookDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Restarts the 1C client process and a scheduler task on the test stand
- Clicks the real TestManager GUI and can activate the wrong window on failure
This is third-party code. Review the repository files before installing.
What it does
The project collects field-tested fixes for driving 1C thick-client GUI tests via Vanessa Automation with no human at the keyboard: reliable activation of the right window when TestManager and TestClient share the same title, using AttachThreadInput plus a mandatory GetForegroundWindow check before clicking; catching the case where the log says no errors but the receipt did not actually post; fixing the client hang on first launch after UpdateDBCfg; and explaining where a window's title actually comes from for different form types. The fixes are packaged as PowerShell scripts Invoke-VanessaButton, Read-VanessaResult and Restart-VanessaStand, plus a SKILL.md for Claude Code with a full run runbook.
Who it is for. For QA engineers and 1C developers running Vanessa Automation GUI tests from a script or CI on the thin client, who have already hit these specific pitfalls.
Good fit when
- You need to reliably click TestManager from a script, not a mouse
- You need to catch the case where the log says no errors but the operation actually failed
- You need a ready Vanessa run runbook as a Claude Code skill
Not a fit when
- Tests are run manually by a person and headless automation is not needed
- The stand is not PowerShell and Windows Server: the fixes rely on .NET Framework's UI Automation
Example request
Run the card-sale scenario and figure out why it failed on the payment formLimitations
Verified on 1C platform 8.3.23, Vanessa Automation 1.2.043 and one managed-forms configuration; behavior may differ on other versions. The recipes need PowerShell 5.1+ and Windows Server. Button names in the examples are specific to the verified retail configuration.
How to disable. Delete the ~/.claude/skills/vanessa-1c directory, or simply do not wire the PowerShell scripts into your run.
FAQ
Why doesn't plain SetForegroundWindow work?
Because Manager and TestClient share the same title and BoundingRectangle, and Windows silently clicks the wrong window without the AttachThreadInput chain and a GetForegroundWindow check.
How do you tell payment actually failed when the log is clean?
Check the result with a database query, not just the log: on a stand without a fiscal register, a receipt can stay unposted even with a clean Vanessa log.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsRules, two skills and a standard step catalog for writing Vanessa Automation Turbo Gherkin scenarios with an agent
Vanessa Automation MCP reads 1C test state from chat, showing results and the manager environment after a scenario fails.
An MCP tool for interactively driving the 1C:Enterprise UI through the test client: clicks, fields, tables and evidentiary scenario recording
An MCP server and manager for native 1C TestClient QA automation: BDD scenarios, managed-form checks, without a Vanessa Automation runtime
RAT: Remote API for Testing
Remote API for Testing (RAT)
A 1C extension with a REST API for integration tests: reading and changing another base's data from outside, plus ready Vanessa Automation steps
A skill and tester agent for Claude Code that test the 1C interface through the 1c-testpilot MCP server with evidence
README in short
The README lists numbered findings: the two-identical-title-window problem, a false «no errors» result, Manager's layout breaking from SW_RESTORE, the client hang after UpdateDBCfg, and where a window's title actually comes from for different forms; it gives a PowerShell-only quick start and a section on using it as a Claude Code skill via the /vanessa-1c command.