Test suite does not track optional features
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Siesta |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm currently carrying out a testing campaign on various builds of the trunk of SIESTA (revno 646). I want to automate everything as much as possible, in order to avoid human mistakes and schedule the tests when the computer is most available.
Regarding optional SIESTA features, it is possible in many cases to guess whether a test requires one based on its name, but this does not work all the time. In particular, there is no information about whether the optional feature is purely internal to SIESTA or depends on an external library.
The main road block in automating the execution and analysis of the tests is that one cannot determine the relevance of running an individual test since it is not possible to establish the link between the compilation parameters and the actual features enabled in the program.
I would like to discuss what could be done to make such data available to the test suite.
