SkillFoxx

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

  • 45 ★ on the repository
  • Last commit
  • LGPL-3.0
Plugin

Broad access

Why this level

  • The REST API grants rights to create, change and delete data in the connected base
  • Allows remotely triggering scheduled jobs and running arbitrary queries
All reasons and checks
Russian stack

bia-technologies/ratAuthor:BIA Technologies

Install

Manual install

docker compose up -d

Run the ready service from tools/service with a base and the extension for local tests.

Access and checks

How we review

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

  • The REST API grants rights to create, change and delete data in the connected base
  • Allows remotely triggering scheduled jobs and running arbitrary queries

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

What it does

RAT installs as an extension into the base under test and starts an HTTP service that external code uses to read and change data, run scheduled jobs and execute arbitrary queries. A large set of common modules (metadata, virtual tables, register movements, exchanges, scheduled jobs and more) covers most of the platform's standard data-manipulation functionality over REST. Separately, ready Vanessa Automation steps let a test scenario running in one 1C base find, create, change and delete data in another base over REST, without opening its interface. The repository includes a ready Docker service for running a local base with the extension, plus a config for running through the project's MCP tooling.

Who it is for. For QA engineers and 1C developers who write Vanessa Automation integration tests and need to prepare and verify data in a related 1C base without manual UI steps.

Good fit when

  • A Vanessa Automation test needs to prepare or verify data in another 1C base
  • You need REST access to base data for external scripts or CI with no user interface
  • You need to manage the tested base's scheduled jobs remotely

Not a fit when

  • The extension would go into a production base with no dedicated test environment: the REST API grants broad data-change rights
  • You do not use Vanessa Automation and do not write REST-based integration tests
  • You need the MCP protocol directly, not a REST API

Example request

Use the RAT REST API to create a test counterparty in the related base and verify that a sales document generated postings for it

Limitations

The extension gives REST access for data manipulation, so the README and docs emphasize a testing purpose rather than production use. Part of the project (.agents/skills/issue-workflow) is an internal skill for developing RAT itself, not functionality shipped to users. The GitHub Pages documentation is more detailed than the README and should be the reference for adoption.

How to disable. Remove the rat extension from the base under test via the Configurator and stop the Docker service if it was used.

FAQ

Can RAT be used without Vanessa Automation?

Yes, the REST API is self-sufficient and works with any external code; the Vanessa steps are an extra layer on top of it.

Is there a ready way to run a test base with the extension?

Yes, tools/service has a Dockerfile and docker-compose.yml for a local run.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

PowerShell recipes for headless 1C GUI test runs via Vanessa Automation TestManager, plus a Claude Code skill that solves gotchas absent from the docs

SkillExtended access4
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

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

An MCP server and manager for native 1C TestClient QA automation: BDD scenarios, managed-form checks, without a Vanessa Automation runtime

MCP serverBroad access5

METR

METR (MCP 1C:Enterprise Test Runner)

Russian stack

An MCP server that lets an agent update a 1C infobase, run YaXUnit tests and check syntax

MCP serverBroad access123
Official

Vanessa Automation MCP reads 1C test state from chat, showing results and the manager environment after a scenario fails.

MCP serverBroad access740

README in short

The README briefly describes the purpose: an extension for REST API integration tests that provides a service for manipulating 1C base data and scheduled jobs, and mentions ready exportable steps for Vanessa Automation to work with another 1C base. Details are moved to separate GitHub Pages documentation.

README badge

Report a problem