skills.rest
SnapLogic
SnapLogicOFFICIAL
Explore all skills by this author →
WebsiteGitHub

debug-logs

Diagnose Robot Framework test failures by inspecting logs and environment checks.

5|Updated Jun 3, 2025
Search Tags:#Docker#logs#debug#containers#tests#Robot Framework#SnapLogic
One-click install
npx skills add https://github.com/SnapLogic/snaplogic-robotframework-examples --skill debug-logs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-logs
Source: https://github.com/SnapLogic/snaplogic-robotframework-examples/tree/main/%7B%7Bcookiecutter.primary_pipeline_name%7D%7D/.claude/skills/debug-logs
Command: npx skills add https://github.com/SnapLogic/snaplogic-robotframework-examples --skill debug-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers quickly diagnose Robot Framework test failures by surfacing logs and practical debugging steps, reducing time spent chasing flaky tests.

Core Features & Use Cases

  • View the latest Robot Framework test results and reports from test/robot_output.
  • Inspect container status and service logs to pinpoint failures.
  • Run quick environment checks (env vars, network, and dependencies) to diagnose issues in SnapLogic deployments.

Quick Start

  • View the most recent test log: ls -lt test/robot_output/log-*.html | head -1
  • Check overall container and service status: make status
  • Tail and inspect service logs for a given component: docker compose logs -f tools
  • Run environment diagnostics: make check-env
  • Validate network connectivity between services: make docker-networks

Frequently Asked Questions about debug-logs

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

FAQPage Schema
How do I debug Robot Framework test failures and view logs in Docker containers?▼

To debug Robot Framework test failures, inspect the latest test reports in test/robot_output, check container status with make status, and tail service logs using docker compose logs to pinpoint failures.

How do I check Docker container status and service logs for failing tests?▼

Check Docker container status for failing tests by running make status, then inspect specific service logs using docker compose logs -f <service> to identify the root cause of the failure.

How do I run environment diagnostics to troubleshoot SnapLogic deployment issues?▼

Run environment diagnostics for SnapLogic deployment issues using make check-env to validate environment variables, and make docker-networks to verify network connectivity between services.

Where can I find Robot Framework test results and reports after a test run?▼

Robot Framework test results and reports are generated as HTML files in the test/robot_output directory, which you can list by running ls -lt test/robot_output/log-*.html to find the most recent log.

Do I need specific Make targets and Docker setup to diagnose test failures in SnapLogic deployments?▼

Yes, diagnosing test failures in SnapLogic deployments requires access to test artifacts under test/robot_output and standard Docker/Make targets for status, logs, and environment checks.

What is the best way to trace flaky Robot Framework tests in containerized environments?▼

The best way to trace flaky Robot Framework tests in containerized environments is to cross-reference the latest HTML test logs with container service logs and environment diagnostics.

Related Skills

Explore More Software Engineering Skills→
sumik5sumik5
2

mcp-docker

Manage Docker containers, images, and Compose environments.

Community
Advanced
akirschke15-cmdakirschke15-cmd

fix-loop

Automate test-driven debugging cycles to fix failing unit tests.

Community
Intermediate
wientjeswientjes

setup

Automate NanoClaw setup with Docker or Apple Container, WhatsApp authentication, and service startup.

Community
Advanced
alangebalangeb

docker

Manage Docker container lifecycles and service orchestration via compose operations.

Community
Intermediate