Eiffel - Software - Eiffel Specification

Maintainer

Jonathan Ostroff and others

Description

ESpec (Eiffel Specification) is a Software Quality Workbench supporting Specification Driven Development by helping developers to write and execute acceptance tests as well as unit tests within the same environment.

ESpec provides support for writing testable requirements and specifications at multiple stages of software development process. Developers can write requirements and specification such as Fit tests, unit tests, contracts as early as possible.

ESpec is a combination of three main components:

ES-Fit: An Acceptance Testing framework for capturing and testing customer requirements in the form of HTML tables used for Validation
ES-Test: A Unit Testing framework for testing specifications. A combination of Unit tests and Contracts are used for lightweight Verification
ES-Verify: A translator from Eiffel to Perfect language used for full Verification

ESpec focuses on Unit Tests and Contracts as testable specifications and Fit Tables as testable requirements.

Versions

(2006-11-14)

Using ES-Test

In order to run the tests:

Write your tests, inheriting from class NET_UNIT_TEST
Compile your project in EiffelStudio
Hit Run Tests in the ES_Test GUI. A dialog box will prompt you to select the executable for your project.

Notes

A filter can be used to display only failed tests
An HTML version of the report is also generated
Unlike JUnit, there is no automatic reflection to discover which tests to run -- you need to add the tests manually using the agent mechanism (for example by using the routine add_boolean_case
The comment routine can be used to generate the comment you would like to see appear when this test is run
Write normal tests (that are expected to run without contract violations) as well as tests that exercise contracts

Example

This class tests the routines sqrt and close_enough of class MATH:

class MATH_TEST inherit NET_UNIT_TEST create make feature make is do make_test add_boolean_case (agent test_sqrt_4) to_html ("tests.htm") end test_sqrt_4: BOOLEAN is local m: MATH do comment("test_sqrt_4") create m Result := m.close_enough (m.sqrt(4),2) end end

The test will not compile until you add a class MATH with the appropriate routines. You can then invoke es_test to run the ES_Test GUI.

ES_Test GUI / » image: ES_Test website