SkillFoxx

Tester skill

Тестер

A scenario testing system for 1C:Enterprise with a set of agent skills that let an AI agent operate the application like a regular user

  • 208 ★ on the repository
  • Last commit
  • BSD-2-Clause
Skill

Broad access

Why this level

  • Runner scripts perform real user actions in 1C, including data changes through the interface
  • The agent gets access to the whole application's main menu and commands, not to an isolated sandbox
All reasons and checks
Russian stack

grumagargler/testerAuthor:grumagargler

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/tester

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Runner scripts perform real user actions in 1C, including data changes through the interface
  • The agent gets access to the whole application's main menu and commands, not to an isolated sandbox

This is third-party code. Review the repository files before installing.

What it does

Tester is a 1C configuration in EDT format for recording and running scenario tests of managed forms: recording user actions into code, scheduled runs, reports and result mailing. The kit includes an assistant workspace with skills for an AI agent, duplicated for Claude Code (.claude/skills) and for the generic agent skills format (.agents/skills for Codex and compatible tools): the base runner-core skill teaches the agent to inspect the UI through Runner before every action, and separate skills cover choosing values, searching and sorting in lists. A separate bsl-format skill formats BSL code to the project style. There is also a VS Code extension with snippets and test-run commands.

Who it is for. For 1C developers and testers who need regression tests for forms and an agent that safely drives a test 1C client through scripts.

Good fit when

  • You need scenario regression tests for 1C managed forms
  • You want an AI agent to imitate user actions through Runner scripts instead of reading the database directly
  • You need to record user actions and turn them into test code automatically

Not a fit when

  • You need a one-off lightweight test without installing a configuration and extensions into the infobase
  • You need testing unrelated to 1C:Enterprise

Example request

Run the Tester regression scenario for the item list form and send me the report

Limitations

Building the C++ external components needs CMake and the standard C++ runtime (vcredist on Windows). The configuration is built in 8.3.27 compatibility mode, and older platform versions may reject the cf file without lowering the mode. The README does not give step by step instructions for installing the skill set into a third-party project, only the structure of the assistant directory.

How to disable. Remove the copied .claude/skills or .agents/skills from the project, disable the MCP Runner in the agent's .mcp.json and remove the Tester extension from the 1C infobase.

FAQ

Can Tester be used for routine operations, not just tests?

Yes, the README also describes data export and import, batch 1C runs, generating test data and load testing.

Why are the skills duplicated in .claude/skills and .agents/skills?

So the same Runner skill set works in both Claude Code and other tools that support the open agent skills format, including Codex.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A skill and tester agent for Claude Code that test the 1C interface through the 1c-testpilot MCP server with evidence

SkillExtended access22
Russian stack

An MCP server that drives the 1C test client's interface directly: opens forms, fills fields, records and replays scenarios

MCP serverBroad access84
Russian stack

A 1C development skill collection for Codex and Claude Code: XML sources, forms, data composition, infobases, web publishing and an HTTP test bridge

SkillBroad access62
Russian stack

An MCP tool for interactively driving the 1C:Enterprise UI through the test client: clicks, fields, tables and evidentiary scenario recording

MCP serverBroad access6
Russian stack

The 1c-dev Claude Code plugin: discussing a 1C task in dialogue, a technical spec, dependency-aware steps, and executing one verified step at a time

PluginMinimal access
Russian stack

A Copier project template for 1C with a bundle of SKILL.md files for Claude Code and Codex: dump, load, tests and extension builds via stable scripts

SkillExtended access2

README in short

The README describes the repository layout: C++ external components for the testing client and server, a VS Code extension, the assistant agent workspace, a ready build in dist and configuration sources in EDT format. It lists the features: recording and coding scenarios, role-based access, git webhook integration, reports, result mailing, scheduled and CI testing, and step by step video recording. It separately covers building the external components and the C++ runtime requirement on Windows.

README badge

Original SKILL.md

---
name: bsl-format
description: Format or reformat 1C:Enterprise BSL (.bsl) code to match my style. Use when asked to format BSL files or snippets in this repo, or to normalize indentation/spacing/keyword casing for BSL.
---

# BSL Format

## Overview
Apply the project BSL style to files or snippets while preserving behavior and content.

## Workflow
1. Identify the target style for the file.
   - Default to the project style in references/style.md.
2. Apply formatting rules: indentation, spacing, keyword casing, semicolons, wrapping, and blank lines.
3. Preserve semantics: do not change strings, query text, comments, or logic; only adjust formatting/casing.
4. Re-scan for consistency (tabs, parentheses spacing, keyword casing) and fix any drift.

## Reference
Read references/style.md before formatting to ensure the rules match this repository.

Report a problem