TDD-First Installer Framework

The bashrs installer framework provides a declarative, TDD-first approach to building reliable installers. Every installer starts with tests, ensuring your deployment is verifiable from day one.

Philosophy

The installer framework applies:

• Karl Popper's Falsificationism: Every claim about your installer can be empirically tested
• Toyota Production System: Stop-the-line quality, with checkpointing and rollback
• EXTREME TDD: Tests exist before implementation

Key Features

Quick Start

 Initialize a new installer project
bashrs installer init my-app-installer

 Validate the specification
bashrs installer validate my-app-installer

 Preview changes (dry-run)
bashrs installer run my-app-installer --dry-run --diff

 Execute the installer
bashrs installer run my-app-installer

Project Structure

When you run bashrs installer init, the following structure is created:

my-app-installer/
├── installer.toml          # Declarative specification
├── tests/
│   ├── mod.rs              # Test module
│   └── falsification.rs    # Popper-style tests
└── templates/              # Template files

installer.toml Format

The installer.toml file defines your installer declaratively:

[installer]
name = "my-app"
version = "1.0.0"
description = "My application installer"

[installer.requirements]
os = ["ubuntu >= 20.04", "debian >= 11"]
arch = ["x86_64", "aarch64"]
privileges = "user"

[[step]]
id = "install-deps"
name = "Install Dependencies"
action = "script"

[step.script]
interpreter = "sh"
content = '''
apt-get update
apt-get install -y curl git
'''

[[step]]
id = "download-app"
name = "Download Application"
action = "script"
depends_on = ["install-deps"]

[step.script]
content = '''
curl -L https://example.com/app.tar.gz -o app.tar.gz
'''

Commands Reference

Next Steps

• Getting Started - Create your first installer
• Step Types - Available action types
• Checkpointing - Resume from failures
• Testing - Container-based testing