x-execute-socket-smoke-tests

Run black-box smoke tests against a TCP socket server using a Java client.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-execute-socket-smoke-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-execute-socket-smoke-tests
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-execute-socket-smoke-tests
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-execute-socket-smoke-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates black-box smoke tests against the application's TCP socket server using a standalone Java client that speaks the real wire protocol with proper message framing (length-prefix header). Tests verify connectivity, message exchange, error handling for malformed messages, and persistent connection behavior.

Core Features & Use Cases

  • Automated end-to-end smoke testing of TCP socket interfaces across environments
  • Supports Kubernetes port-forwarding for orchestrated environments (the --k8s flow) and multiple scenarios (echo, request-approved, request-denied, malformed, persistent, all)
  • Validates framing, payload processing, error handling, and connection lifecycle
  • Configurable host/port and scenarios via command line

Quick Start

Run the command /x-execute-socket-smoke-tests to run all configured test scenarios against the target server, optionally using --host and --port to target a different host.

Frequently Asked Questions about x-execute-socket-smoke-tests

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

FAQPage Schema
How do I automate TCP socket smoke tests with a Java client?

Automate TCP socket smoke tests by orchestrating a standalone Java client that speaks the real wire protocol with length-prefix message framing to verify connectivity, message exchange, and error handling against a running TCP server.

What scenarios are supported for TCP socket smoke testing?

Supported TCP socket smoke testing scenarios include echo, request-approved, request-denied, malformed, persistent, and all, validating framing, payload processing, error handling, and connection lifecycle behavior.

Do I need Java 21 to run TCP socket smoke tests?

Yes, Java 21+ is required to run the standalone client JAR for TCP socket smoke tests, along with a built client JAR under smoke-tests/socket and a running server accessible via TCP on the configured port.

Can I run TCP socket smoke tests against a Kubernetes port-forwarded service?

Yes, TCP socket smoke tests support Kubernetes port-forwarding for orchestrated environments using the --k8s flow, allowing you to target services running inside a cluster from your local machine.

How do I configure the host and port for TCP socket smoke tests?

Configure the host and port for TCP socket smoke tests by passing the --host and --port command line arguments when running the test command, targeting a different server or environment as needed.

What problems do black-box smoke tests solve for TCP socket servers?

Black-box smoke tests for TCP socket servers verify end-to-end connectivity, proper message framing, payload processing, malformed message error handling, and persistent connection behavior across different environments without needing internal server access.