Vérification et Génération de Tests Eiffel

VérifiéSûr

Génère une suite de tests à partir des contrats Eiffel et les exécute. Aide à vérifier les postconditions et les cas limites en traduisant automatiquement les contrats en tests exécutables. Inclut une analyse des lacunes de couverture par IA pour identifier les contrats non testés.

Spar Skills Guide Bot
TestingIntermédiaire
4002/06/2026
Claude Code
#eiffel#contract-testing#test-generation#coverage#verification

Recommandé pour

Notre avis

Génère une suite de tests à partir des contrats Eiffel et exécute les tests, avec une analyse des lacunes de couverture par chaîne d'IA.

Points forts

  • Automatisation complète de la génération de tests basée sur les contrats
  • Vérification obligatoire zéro avertissement garantissant la qualité du code
  • Analyse de couverture intégrée pour identifier les lacunes
  • Sauvegarde des preuves de test pour traçabilité

Limites

  • Nécessite que la phase 4 soit terminée (implémentation compilable)
  • Dépend de la qualité des contrats écrits pour générer des tests pertinents
  • Ne gère pas les tests d'intégration ou de bout en bout
Quand l'utiliser

Utilisez cette compétence après avoir implémenté les contrats pour automatiser la vérification et la couverture des tests.

Quand l'éviter

Évitez de l'utiliser si le projet n'utilise pas les contrats Eiffel ou si vous préférez une approche de test manuelle.

Analyse de sécurité

Sûr
Score qualité95/100

The skill runs a specific project build and test command using Bash, which is a legitimate use within a controlled build environment. It does not contain destructive, exfiltrating, or obfuscated instructions, and it does not disable safety features. The risk is limited to user-provided project code, which is inherent to any build system.

Aucun point d'attention détecté

Exemples

Run verification on project
/eiffel.verify /path/to/eiffel-project
Complete verification after implementation
/eiffel.verify ./my-eiffel-app

name: eiffel-verify description: Phase 5 of Eiffel Spec Kit. Generates test suite derived from contracts and runs tests. Includes AI chain coverage gap analysis. Use with /eiffel.verify command. allowed-tools: Read, Grep, Glob, Edit, Write, Bash, Task

/eiffel.verify - Phase 5: Test Generation and Verification

Purpose: Flesh out skeletal tests, generate contract-derived tests, verify all tests pass.

Usage

/eiffel.verify <project-path>

Project Scoping

<project-path>/
├── .eiffel-workflow/
│   ├── prompts/
│   │   └── phase5-coverage-review.md
│   └── evidence/
│       ├── phase5-tests.txt
│       └── phase5-coverage.txt
├── test/*.e (tests fleshed out here)

Prerequisites

  • Phase 4 complete: implementation compiles

Workflow

Step 1: Flesh Out Skeletal Tests

Complete tests created in Phase 1.

Step 2: Generate Contract-Derived Tests

For each postcondition, ensure a test verifies it.

Step 3: Generate Coverage Review Prompt

Create <project-path>/.eiffel-workflow/prompts/phase5-coverage-review.md:

# Test Coverage Review

## Contracts
[PASTE src/*.e]

## Tests
[PASTE test/*.e]

## Check For:
- Postconditions without corresponding tests
- Edge cases not tested
- Precondition boundary tests missing

Step 4: Compile and Run Tests (MANDATORY GATE)

CRITICAL: You MUST cd to the project directory before compiling. The EIFGENs folder is created in the current working directory, not where the ECF file is located. Compiling from the wrong directory pollutes other folders with build artifacts.

cd <project-path> && /d/prod/ec.sh -batch -config <project>.ecf -target <project>_tests -c_compile
./EIFGENs/<project>_tests/W_code/<project>.exe

ZERO WARNINGS POLICY: If the compiler reports obsolete call warnings or any other warnings, FIX THEM IMMEDIATELY. Do not note them and move on. Do not defer them. Fix them right now before proceeding.

ALL TESTS MUST PASS.

Step 5: Save Evidence

Save to <project-path>/.eiffel-workflow/evidence/phase5-tests.txt:

# Phase 5 Test Evidence
# Project: <project-path>
# Date: [timestamp]

[Paste test output]

Tests run: [count]
Tests passed: [count]
# Status: PASS / FAIL

Context Management (RLM Pattern)

This skill focuses ONLY on: <project-path>

DO NOT:

  • Read files outside this project directory
  • Load entire ecosystem or multiple libraries into context
  • Keep large file contents in working memory

DO:

  • Use Task tool with Explore agent for ecosystem questions
  • Ask targeted questions when tests need to understand external library behavior
  • Release context after getting answers

Example - Ecosystem Query:

Need to understand how simple_testing assertions work? Don't read all its files.
Instead: Task(subagent_type=Explore) → "What assertions does EQA_TEST_SET provide?"

The sub-agent searches, summarizes, and returns ONLY what you need. Your context stays focused on this project.

Completion

Phase 5 COMPLETE: Verification passed.
Project: <project-path>

Tests: [N] passed

Next: Run /eiffel.harden <project-path> for adversarial testing.
Skills similaires