feat: reorganize test files and delete manual test checklist

- Move test workflows to tests/workflows/
- Move GitLab CI fixtures to tests/fixtures/gitlab-ci/
- Move test scripts to tests/scripts/
- Move Podman testing docs to tests/
- Update paths in test scripts and documentation
- Delete MANUAL_TEST_CHECKLIST.md as requested
- Update tests/README.md to reflect new organization

Cargo.lock

@@ -488,7 +488,7 @@ dependencies = [
 
 [[package]]
 name = "evaluator"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "colored",
  "models",
@@ -498,7 +498,7 @@ dependencies = [
 
 [[package]]
 name = "executor"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "async-trait",
  "bollard",
@@ -716,7 +716,7 @@ checksum = "07e28edb80900c19c28f1072f2e8aeca7fa06b23cd4169cefe1af5aa3260783f"
 
 [[package]]
 name = "github"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "lazy_static",
  "models",
@@ -730,7 +730,7 @@ dependencies = [
 
 [[package]]
 name = "gitlab"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "lazy_static",
  "models",
@@ -1217,7 +1217,7 @@ checksum = "13dc2df351e3202783a1fe0d44375f7295ffb4049267b0f3018346dc122a1d94"
 
 [[package]]
 name = "logging"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "chrono",
  "models",
@@ -1228,7 +1228,7 @@ dependencies = [
 
 [[package]]
 name = "matrix"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "indexmap 2.8.0",
  "models",
@@ -1283,7 +1283,7 @@ dependencies = [
 
 [[package]]
 name = "models"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "serde",
  "serde_json",
@@ -1513,7 +1513,7 @@ dependencies = [
 
 [[package]]
 name = "parser"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "jsonschema",
  "matrix",
@@ -1733,7 +1733,7 @@ dependencies = [
 
 [[package]]
 name = "runtime"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "async-trait",
  "futures",
@@ -2245,7 +2245,7 @@ checksum = "e421abadd41a4225275504ea4d6566923418b7f05506fbc9c0fe86ba7396114b"
 
 [[package]]
 name = "ui"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "chrono",
  "crossterm 0.26.1",
@@ -2326,7 +2326,7 @@ checksum = "06abde3611657adf66d383f00b093d7faecc7fa57071cce2578660c9f1010821"
 
 [[package]]
 name = "utils"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "models",
  "nix",
@@ -2345,7 +2345,7 @@ dependencies = [
 
 [[package]]
 name = "validators"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "matrix",
  "models",
@@ -2719,7 +2719,7 @@ checksum = "1e9df38ee2d2c3c5948ea468a8406ff0db0b29ae1ffde1bcf20ef305bcc95c51"
 
 [[package]]
 name = "wrkflw"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "bollard",
  "chrono",

MANUAL_TEST_CHECKLIST.md

@@ -1,207 +0,0 @@
-# Manual Testing Checklist for Podman Support
-
-## Quick Manual Verification Steps
-
-### ✅ **Step 1: CLI Help and Options**
-```bash
-./target/release/wrkflw run --help
-```
-**Verify:**
-- [ ] `--runtime` option is present
-- [ ] Shows `docker`, `podman`, `emulation` as possible values
-- [ ] Default is `docker`
-- [ ] Help text explains each option
-
-### ✅ **Step 2: CLI Runtime Selection**
-```bash
-# Test each runtime option
-./target/release/wrkflw run --runtime docker test-workflows/example.yml --verbose
-./target/release/wrkflw run --runtime podman test-workflows/example.yml --verbose  
-./target/release/wrkflw run --runtime emulation test-workflows/example.yml --verbose
-
-# Test invalid runtime (should fail)
-./target/release/wrkflw run --runtime invalid test-workflows/example.yml
-```
-**Verify:**
-- [ ] All valid runtimes are accepted
-- [ ] Invalid runtime shows clear error message
-- [ ] Podman mode shows "Podman: Running container" in verbose logs
-- [ ] Emulation mode works without containers
-
-### ✅ **Step 3: TUI Runtime Support**
-```bash
-./target/release/wrkflw tui test-workflows/
-```
-**Verify:**
-- [ ] TUI starts successfully
-- [ ] Status bar shows current runtime (bottom of screen)
-- [ ] Press `e` key to cycle through runtimes: Docker → Podman → Emulation → Docker
-- [ ] Runtime changes are reflected in status bar
-- [ ] Podman shows "Connected" or "Not Available" status
-
-### ✅ **Step 4: TUI Runtime Parameter**
-```bash
-./target/release/wrkflw tui --runtime podman test-workflows/
-./target/release/wrkflw tui --runtime emulation test-workflows/
-```
-**Verify:**
-- [ ] TUI starts with specified runtime
-- [ ] Status bar reflects the specified runtime
-
-### ✅ **Step 5: Container Execution Test**
-Create a simple test workflow:
-```yaml
-name: Runtime Test
-on: [workflow_dispatch]
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    container: ubuntu:20.04
-    steps:
-      - run: |
-          echo "Runtime test execution"
-          whoami
-          pwd
-          echo "Test completed"
-```
-
-Test with different runtimes:
-```bash
-./target/release/wrkflw run --runtime podman test-runtime.yml --verbose
-./target/release/wrkflw run --runtime docker test-runtime.yml --verbose
-./target/release/wrkflw run --runtime emulation test-runtime.yml --verbose
-```
-**Verify:**
-- [ ] Podman mode runs in containers (shows container logs)
-- [ ] Docker mode runs in containers (shows container logs)
-- [ ] Emulation mode runs on host system
-- [ ] All modes produce similar output
-
-### ✅ **Step 6: Error Handling**
-```bash
-# Test with Podman unavailable (temporarily rename podman binary)
-sudo mv /usr/local/bin/podman /usr/local/bin/podman.tmp 2>/dev/null || echo "podman not in /usr/local/bin"
-./target/release/wrkflw run --runtime podman test-runtime.yml
-sudo mv /usr/local/bin/podman.tmp /usr/local/bin/podman 2>/dev/null || echo "nothing to restore"
-```
-**Verify:**
-- [ ] Shows "Podman is not available. Using emulation mode instead."
-- [ ] Falls back to emulation gracefully
-- [ ] Workflow still executes successfully
-
-### ✅ **Step 7: Container Preservation**
-```bash
-# Create a failing workflow
-echo 'name: Fail Test
-on: [workflow_dispatch]
-jobs:
-  fail:
-    runs-on: ubuntu-latest
-    container: ubuntu:20.04
-    steps:
-      - run: exit 1' > test-fail.yml
-
-# Test with preservation
-./target/release/wrkflw run --runtime podman --preserve-containers-on-failure test-fail.yml
-
-# Check for preserved containers
-podman ps -a --filter "name=wrkflw-"
-```
-**Verify:**
-- [ ] Failed container is preserved when flag is used
-- [ ] Container can be inspected with `podman exec -it <container> bash`
-- [ ] Without flag, containers are cleaned up
-
-### ✅ **Step 8: Documentation**
-**Verify:**
-- [ ] README.md mentions Podman support
-- [ ] Examples show `--runtime podman` usage
-- [ ] TUI keybind documentation mentions runtime cycling
-- [ ] Installation instructions for Podman are present
-
-## Platform-Specific Tests
-
-### **Linux:**
-- [ ] Podman works rootless
-- [ ] No sudo required for container operations
-- [ ] Network connectivity works in containers
-
-### **macOS:**
-- [ ] Podman machine is initialized and running
-- [ ] Container execution works correctly
-- [ ] Volume mounting works for workspace
-
-### **Windows:**
-- [ ] Podman Desktop or CLI is installed
-- [ ] Basic container operations work
-- [ ] Workspace mounting functions correctly
-
-## Performance and Resource Tests
-
-### **Memory Usage:**
-```bash
-# Monitor memory during execution
-./target/release/wrkflw run --runtime podman test-runtime.yml &
-PID=$!
-while kill -0 $PID 2>/dev/null; do
-    ps -p $PID -o pid,ppid,pgid,sess,cmd,%mem,%cpu
-    sleep 2
-done
-```
-**Verify:**
-- [ ] Memory usage is reasonable
-- [ ] No memory leaks during execution
-
-### **Container Cleanup:**
-```bash
-# Run multiple workflows and check cleanup
-for i in {1..3}; do
-    ./target/release/wrkflw run --runtime podman test-runtime.yml
-done
-podman ps -a --filter "name=wrkflw-"
-```
-**Verify:**
-- [ ] No containers remain after execution
-- [ ] Cleanup is thorough and automatic
-
-## Integration Tests
-
-### **Complex Workflow:**
-Test with a workflow that has:
-- [ ] Multiple jobs
-- [ ] Environment variables
-- [ ] File operations
-- [ ] Network access
-- [ ] Package installation
-
-### **Edge Cases:**
-- [ ] Very long-running containers
-- [ ] Large output logs
-- [ ] Network-intensive operations
-- [ ] File system intensive operations
-
-## Final Verification
-
-**Overall System Check:**
-- [ ] All runtimes work as expected
-- [ ] Error messages are clear and helpful
-- [ ] Performance is acceptable
-- [ ] User experience is smooth
-- [ ] Documentation is accurate and complete
-
-**Sign-off:**
-- [ ] Basic functionality: ✅ PASS / ❌ FAIL
-- [ ] CLI integration: ✅ PASS / ❌ FAIL  
-- [ ] TUI integration: ✅ PASS / ❌ FAIL
-- [ ] Error handling: ✅ PASS / ❌ FAIL
-- [ ] Documentation: ✅ PASS / ❌ FAIL
-
-**Notes:**
-_Add any specific issues, observations, or platform-specific notes here._
-
----
-
-**Testing completed by:** ________________  
-**Date:** ________________  
-**Platform:** ________________  
-**Podman version:** ________________

tests/README.md

@@ -1,6 +1,6 @@
 # Testing Strategy
 
-This directory contains integration tests for the `wrkflw` project. We follow the Rust testing best practices by organizing tests as follows:
+This directory contains all tests and test-related files for the `wrkflw` project. We follow the Rust testing best practices by organizing tests as follows:
 
 ## Test Organization
 
@@ -11,6 +11,17 @@ This directory contains integration tests for the `wrkflw` project. We follow th
 - **End-to-End Tests**: Also located in this `tests/` directory
   - `cleanup_test.rs` - Tests for cleanup functionality with Docker resources
 
+## Test Directory Structure
+
+- **`fixtures/`**: Test data and configuration files
+  - `gitlab-ci/` - GitLab CI configuration files for testing
+- **`workflows/`**: GitHub Actions workflow files for testing
+  - Various YAML files for testing workflow validation and execution
+- **`scripts/`**: Test automation scripts
+  - `test-podman-basic.sh` - Basic Podman integration test script
+  - `test-preserve-containers.sh` - Container preservation testing script
+- **`TESTING_PODMAN.md`**: Comprehensive Podman testing documentation
+
 ## Running Tests
 
 To run all tests:

tests/TESTING_PODMAN.md

@@ -70,21 +70,21 @@ Expected: Should show `--runtime` option with default value `docker`.
 #### 1.2 Test Podman Runtime Selection
 ```bash
 # Should accept podman as runtime
-./target/release/wrkflw run --runtime podman test-workflows/example.yml
+./target/release/wrkflw run --runtime podman tests/workflows/example.yml
 ```
 Expected: Should run without CLI argument errors.
 
 #### 1.3 Test Emulation Runtime Selection
 ```bash
 # Should accept emulation as runtime
-./target/release/wrkflw run --runtime emulation test-workflows/example.yml
+./target/release/wrkflw run --runtime emulation tests/workflows/example.yml
 ```
 Expected: Should run without CLI argument errors.
 
 #### 1.4 Test Invalid Runtime Selection
 ```bash
 # Should reject invalid runtime
-./target/release/wrkflw run --runtime invalid test-workflows/example.yml
+./target/release/wrkflw run --runtime invalid tests/workflows/example.yml
 ```
 Expected: Should show error about invalid runtime choice.
 
@@ -172,7 +172,7 @@ Expected: All three runtimes should produce similar results (emulation may have
 
 #### 4.1 Test TUI Runtime Selection
 ```bash
-./target/release/wrkflw tui test-workflows/
+./target/release/wrkflw tui tests/workflows/
 ```
 
 **Test Steps:**

tests/scripts/test-podman-basic.sh

@@ -59,7 +59,7 @@ fi
 
 # Test 2: Check invalid runtime rejection
 print_status "Test 2: Testing invalid runtime rejection..."
-if ./target/release/wrkflw run --runtime invalid test-workflows/example.yml 2>&1 | grep -q "invalid value"; then
+if ./target/release/wrkflw run --runtime invalid tests/workflows/example.yml 2>&1 | grep -q "invalid value"; then
     print_success "Invalid runtime properly rejected"
 else
     print_error "Invalid runtime not properly rejected"