DemaConsulting.FileAssert 0.1.0

DemaConsulting.FileAssert

FileAssert is a .NET CLI tool for asserting file properties using YAML-defined test suites. It validates files against acceptance criteria such as size constraints, content requirements, and pattern matching, making it ideal for CI/CD pipelines and compliance workflows.

Features

• File Assertion Testing: YAML-defined test suites that validate file properties against acceptance criteria
• Glob Pattern Matching: Select files using glob patterns via Microsoft.Extensions.FileSystemGlobbing
• Multiple Acceptance Criteria: Validate size (min-size, max-size), content (contains, does-not-contain), regex patterns (matches, does-not-contain-regex), and file counts (count, min, max)
• Tag-Based Test Filtering: Run a targeted subset of tests by filtering on tags
• TRX and JUnit Output: Write test results to TRX or JUnit format via DemaConsulting.TestResults
• Self-Validation: Built-in validation tests confirm the tool is functioning correctly
• Multi-Platform Support: Builds and runs on Windows, Linux, and macOS
• Multi-Runtime Support: Targets .NET 8, 9, and 10
• Comprehensive CI/CD: GitHub Actions workflows with quality checks, builds, and integration tests
• Continuous Compliance: Compliance evidence generated automatically on every CI run, following the Continuous Compliance methodology
• SonarCloud Integration: Quality gate and security analysis on every build
• Documentation Generation: Automated build notes, user guide, code quality reports, requirements, justifications, and trace matrix
• Requirements Traceability: Requirements linked to passing tests with auto-generated trace matrix

Installation

Install the tool globally using the .NET CLI:

dotnet tool install -g DemaConsulting.FileAssert

Usage

# Display version
fileassert --version

# Display help
fileassert --help

# Run tests from the default .fileassert.yaml file
fileassert

# Run tests from a specific file
fileassert --config tests.yaml

# Run only tests matching specific names or tags
fileassert smoke release

# Write results to a TRX file
fileassert --results results.trx

# Write results to a JUnit XML file
fileassert --results results.xml

# Run self-validation
fileassert --validate

# Silent mode with logging
fileassert --silent --log output.log

Command-Line Options

FileAssert YAML Format

The tests file (.fileassert.yaml by default) defines one or more named tests. Each test specifies a set of files using a glob pattern, optional tags for filtering, and one or more acceptance criteria.

# .fileassert.yaml
tests:
  - name: TestProject_BinariesExist
    description: "Application binaries exist"
    tags: [smoke, release]
    files:
      - pattern: "bin/**/*.exe"
        count: 1
      - pattern: "bin/**/*.dll"
        min: 1

  - name: TestProject_ConfigValid
    description: "Config file size is reasonable"
    tags: [config]
    files:
      - pattern: "config/settings.json"
        min-size: 10
        max-size: 1048576
        rules:
          - contains: '"ConnectionStrings"'
          - does-not-contain: "password123"

  - name: TestProject_LogsValid
    description: "Log files match expected pattern"
    tags: [logs]
    files:
      - pattern: "logs/*.log"
        rules:
          - matches: "\\d{4}-\\d{2}-\\d{2}"
          - does-not-contain-regex: "FATAL|CRITICAL"

Acceptance Criteria Reference

Self Validation

Running self-validation produces a report demonstrating that FileAssert is functioning correctly:

# DEMA Consulting FileAssert

| Information         | Value                                              |
| :------------------ | :------------------------------------------------- |
| Tool Version        | <version>                                          |
| Machine Name        | <machine-name>                                     |
| OS Version          | <os-version>                                       |
| DotNet Runtime      | <dotnet-runtime-version>                           |
| Time Stamp          | <timestamp> UTC                                    |

✓ FileAssert_VersionDisplay - Passed
✓ FileAssert_HelpDisplay - Passed

Total Tests: 2
Passed: 2
Failed: 0

Each test in the report proves:

• FileAssert_VersionDisplay - --version outputs a valid version string.
• FileAssert_HelpDisplay - --help outputs usage and options information.

See the User Guide for more details on the self-validation tests.

On validation failure the tool will exit with a non-zero exit code.

Documentation

Generated documentation includes:

• Build Notes: Release information and changes
• User Guide: Comprehensive usage documentation
• Code Quality Report: CodeQL and SonarCloud analysis results
• Requirements: Functional and non-functional requirements
• Requirements Justifications: Detailed requirement rationale
• Trace Matrix: Requirements to test traceability

License

Copyright (c) DEMA Consulting. Licensed under the MIT License. See LICENSE for details.

By contributing to this project, you agree that your contributions will be licensed under the MIT License.