owpenbot-test

Run unit, CLI, npx, and openwrk tests with Telegram test tokens.

63|8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/different-ai/openwork-enterprise --skill owpenbot-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: owpenbot-test
Source: https://github.com/different-ai/openwork-enterprise/tree/main/.opencode/skills/owpenbot-test
Command: npx skills add https://github.com/different-ai/openwork-enterprise --skill owpenbot-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill streamlines end-to-end integration testing for owpenbot/openwrk by coordinating test tokens and Telegram-based workflows, reducing manual setup effort.

Core Features & Use Cases

  • Test orchestration: Runs unit, CLI, NPX, and OpenWrk tests across configured repos.
  • Token management guidance: Provides guidance on configuring Telegram test tokens locally.
  • Use Case: When validating new integrations, run all tests with minimal configuration to ensure end-to-end stability.

Quick Start

Run the script at .opencode/skills/owpenbot-test/scripts/run-tests.sh to execute all tests.

Frequently Asked Questions about owpenbot-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run integration tests for Telegram bots in local development?

To run integration tests for Telegram bots locally, execute a test script that configures Telegram test tokens as environment variables to automate deterministic end-to-end test runs across your repositories.

Can I automate CLI and unit tests for continuous integration environments?

Yes, you can automate CLI, unit, and NPX tests for CI environments by invoking a shell script that sets the required environment variables for deterministic end-to-end test execution.

What are Telegram test tokens used for in end-to-end testing?

Telegram test tokens are used in end-to-end testing to authenticate workflows and configure environment variables, ensuring automated test runs execute deterministically across local and CI scenarios.

Do I need specific environment variables to run openwrk tests?

Yes, running openwrk tests requires configuring specific environment variables, particularly Telegram test tokens, which are automatically managed and applied when you execute the test orchestration script.

What's the best way to orchestrate deterministic test runs across multiple repositories?

The best way to orchestrate deterministic test runs across multiple repositories is using a centralized script that manages token configurations and invokes unit, CLI, and integration tests with properly set environment variables.