gentleman-e2e

Automate end-to-end installer testing in Docker-based environments.

1.9k|282|Updated Nov 19, 2023
One-click install
npx skills add https://github.com/Gentleman-Programming/Gentleman.Dots --skill gentleman-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gentleman-e2e
Source: https://github.com/Gentleman-Programming/Gentleman.Dots/tree/main/skills/gentleman-e2e
Command: npx skills add https://github.com/Gentleman-Programming/Gentleman.Dots --skill gentleman-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a Docker-driven framework for end-to-end validation of the Gentleman.Dots installer, ensuring reliable platform coverage and repeatable test results.

Core Features & Use Cases

  • Standardized test scripts: Reusable e2e_test.sh patterns for consistent testing across platforms.
  • Docker-based environments: Platform-specific Dockerfiles and containers to validate installation on multiple stacks.
  • Non-interactive automation: Tests run with non-interactive flags for CI friendliness and automated validation.

Quick Start

  • Run all platform tests: cd installer/e2e && ./docker-test.sh
  • Validate a single platform: docker run --rm -e RUN_FULL_E2E=1 gentleman-e2e-ubuntu
  • See test patterns in installer/e2e/e2e_test.sh

Frequently Asked Questions about gentleman-e2e

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

FAQPage Schema
How do I run Docker-based end-to-end tests for an installer script?

Run Docker-based end-to-end tests by executing platform-specific Dockerfiles with a standardized e2e_test.sh script. Use non-interactive execution flags to validate installer behavior automatically across multiple shells and window managers.

Can I validate installer backup and restore scenarios across different platforms in CI?

Yes, you can validate backup and restore scenarios using Docker containers with non-interactive test scripts. Platform-specific Dockerfiles validate installation across multiple stacks, ensuring deterministic results in CI or local workflows.

What's the best way to automate E2E testing for dotfiles installation on multiple Linux environments?

Automate E2E testing by running platform-specific Docker containers with a standardized e2e_test.sh script. Docker-based environments validate installer behavior across multiple shells and window managers, ensuring reliable platform coverage.

Do I need Docker to run end-to-end tests for shell installer scripts?

Yes, Docker is required to run end-to-end tests for the installer. Docker-based environments provide platform-specific containers and Dockerfiles needed to validate installation behavior across different stacks deterministically.

How do I ensure deterministic test results when running E2E installer tests in automated pipelines?

Ensure deterministic E2E test results by using standardized test scripts with non-interactive execution flags and cleanup routines. Docker-based environments provide isolated containers that prevent state leakage between test runs.

Why does my E2E test hang when running installer validation in a Docker container?

E2E tests hang when installer scripts require interactive input. Use standardized e2e_test.sh patterns with non-interactive execution flags to prevent prompts from blocking automated validation in Docker-based environments.