---

name: run-tests description: Guides users on running Robot Framework tests in the SnapLogic project. Use when the user wants to run tests, needs to know which make command to use, or wants to understand test tags and execution options. user-invocable: true

SnapLogic Test Execution Skill

Usage Examples

---

Claude Instructions

IMPORTANT: When user asks a simple question like "How do I run Oracle tests?", provide a concise answer first with just the command(s), then offer to explain more if needed. Do NOT dump all documentation.

Response format for simple questions:

1. Give the direct command(s) first
2. Add a brief note if relevant
3. Offer "Want me to explain more?" only if appropriate

---

Quick Command Reference

Note: Use PROJECT_SPACE_SETUP=True for first run, omit for subsequent runs.

Related slash command: /run-tests

---

Agentic Workflow (Claude: Follow these steps in order)

This is the complete guide. Proceed with the steps below.

Step 1: Understand the User's Request

Parse what the user wants:

• Run tests for a specific system? (Oracle, Snowflake, Kafka, etc.)
• First time setup or subsequent run?
• With or without Groundplex management?
• View results or troubleshoot?

Step 2: Provide Quick Answer First

For simple questions, give the command immediately from the Quick Command Reference table above.

Step 3: Offer More Details If Needed

Only provide additional context if the user asks for explanation or if the question is complex.

---

Why Make Commands Instead of Robot Command?

Important: In a standard Robot Framework setup, you would run tests directly using:

Copyrobot --include oracle test/suite/

However, this project uses a dockerized environment. This means:

1. Tests run inside Docker containers - Not on your local machine
2. Services (databases, Kafka, etc.) run in containers - They communicate via Docker networks
3. Environment variables are managed - Loaded from .env files into containers
4. Groundplex runs in a container - For SnapLogic pipeline execution

The make commands handle all this complexity for you.

---

Understanding the Make Targets

1. robot-run-all-tests - Full Workflow with Groundplex

Use this when: First time setup, CI/CD pipelines, or you need Groundplex managed automatically.

Copymake robot-run-all-tests TAGS="your_tags" PROJECT_SPACE_SETUP=True|False

Execution Flow:

CopyPhase 1: Project Space Setup → Phase 2: Launch Groundplex → Phase 3: Run Tests

2. robot-run-tests-no-gp - Without Groundplex Launch

Use this when: Groundplex is already running, or tests don't need Groundplex.

Copymake robot-run-tests-no-gp TAGS="your_tags" PROJECT_SPACE_SETUP=True|False

---

When to Use Which Target

---

Understanding Robot Framework Tags

Tags are labels attached to test cases that allow you to selectively run tests.

Using Tags with Make Commands

Copy# Run only tests with 'snowflake_demo' tag
make robot-run-all-tests TAGS="snowflake_demo"

# Run tests with multiple tags (OR logic)
make robot-run-all-tests TAGS="snowflake_demo OR postgres_demo"

# Run tests with multiple tags (AND logic)
make robot-run-all-tests TAGS="snowflake_demo AND task_creation"

# Exclude tests with specific tag
make robot-run-all-tests TAGS="NOT cleanup"

---

Available Test Tags by System

---

Test Results

Location

Copytest/robot_output/
├── output-YYYYMMDD-HHMMSS.xml   # Raw results (for CI/CD)
├── log-YYYYMMDD-HHMMSS.html     # Detailed execution log
└── report-YYYYMMDD-HHMMSS.html  # Summary report (open this)

Viewing Results

Copy# Open the latest report (macOS)
open test/robot_output/report-*.html

# Find the latest report
ls -lt test/robot_output/report-*.html | head -1

---

Troubleshooting

Common Issues

Debug Steps

1. Check environment: make check-env
2. Check services: make status
3. View test logs: open test/robot_output/log-*.html
4. Re-run with fresh setup: Add PROJECT_SPACE_SETUP=True