You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by "Andrew Black (JIRA)" <ji...@apache.org> on 2006/07/18 00:41:13 UTC
[jira] Created: (STDCXX-261) runall should parse tests and examples
in the same manner
runall should parse tests and examples in the same manner
---------------------------------------------------------
Key: STDCXX-261
URL: http://issues.apache.org/jira/browse/STDCXX-261
Project: C++ Standard Library
Issue Type: Improvement
Components: Build
Reporter: Andrew Black
Priority: Minor
At this time, several of the self tests (0.cmdopts.out, 0.printf.out, 0.strncmp.out, 0.valcmp.out) produce output that lacks a summary section.
The runall.sh (or runall.c) utility should be able to compare the output of these tests against a reference file in the same manner that the output is compared for examples.
An extension of this concept is that it might make sense to unify the logic used to check the test and example results, so that the same process would be used for both tests and examples.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (STDCXX-261) runall should parse tests and examples
in the same manner
Posted by "Andrew Black (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Black updated STDCXX-261:
--------------------------------
Fix Version/s: 4.2.1
Scheduling for 4.2.1, though it may be deferred again.
> runall should parse tests and examples in the same manner
> ---------------------------------------------------------
>
> Key: STDCXX-261
> URL: https://issues.apache.org/jira/browse/STDCXX-261
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Build
> Reporter: Andrew Black
> Priority: Minor
> Fix For: 4.2.1
>
>
> At this time, several of the self tests (0.cmdopts.out, 0.printf.out, 0.strncmp.out, 0.valcmp.out) produce output that lacks a summary section.
> The runall.sh (or runall.c) utility should be able to compare the output of these tests against a reference file in the same manner that the output is compared for examples.
> An extension of this concept is that it might make sense to unify the logic used to check the test and example results, so that the same process would be used for both tests and examples.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (STDCXX-261) runall should parse tests and
examples in the same manner
Posted by "Andrew Black (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/STDCXX-261?page=comments#action_12425565 ]
Andrew Black commented on STDCXX-261:
-------------------------------------
The main drawback I can see with using RCS comments is that we would need to reimplement the ident utility in some manner to retrieve the RCS comments strings. ident isn't a part of the POSIX spec, and even if it were, it would be necessary to provide an implementation for windows.
A couple minor concerns would be ensuring that the RCS comment strings aren't optimized away and that RCS comments are inserted into the shell script (locale) targets.
To me, useful information that could be embedded would be the location of the reference input file (if one exists) and the reference output file. This would eliminate the search logic used at this time to locate said files. This would also allow tests to have such files. Another piece of useful information could be the format of the output file generated, allowing us to distinguish test suite driver output from compatibility layer output (eliminating the compat global and the --compat/--nocompat switches).
In an off-line discussion with Martin, he noted that another useful piece of information that could be embedded in a test would be platform-specific control over which tests are enabled/disabled. I wonder whether it would make more sense for such enable/disable logic to reside in the test suite/test driver, rather than the exec utility.
> runall should parse tests and examples in the same manner
> ---------------------------------------------------------
>
> Key: STDCXX-261
> URL: http://issues.apache.org/jira/browse/STDCXX-261
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Build
> Reporter: Andrew Black
> Priority: Minor
>
> At this time, several of the self tests (0.cmdopts.out, 0.printf.out, 0.strncmp.out, 0.valcmp.out) produce output that lacks a summary section.
> The runall.sh (or runall.c) utility should be able to compare the output of these tests against a reference file in the same manner that the output is compared for examples.
> An extension of this concept is that it might make sense to unify the logic used to check the test and example results, so that the same process would be used for both tests and examples.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (STDCXX-261) runall should parse tests and
examples in the same manner
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/STDCXX-261?page=comments#action_12425542 ]
Martin Sebor commented on STDCXX-261:
-------------------------------------
It would be nice if the runall aka exec utility could somehow figure out from the executable itself what kind of output to expect and adjust automatically. This would let it distinguish not only the tests designed to produce different output but also examples from tests, and it might open a whole bunch of other possibilities as well. One approach might be to embed some sort of a special string (e.g., in the form of an RCS comment) in the executable itself and having the utility read it (see http://www.delorie.com/gnu/docs/rcs/ident.1.html).
> runall should parse tests and examples in the same manner
> ---------------------------------------------------------
>
> Key: STDCXX-261
> URL: http://issues.apache.org/jira/browse/STDCXX-261
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Build
> Reporter: Andrew Black
> Priority: Minor
>
> At this time, several of the self tests (0.cmdopts.out, 0.printf.out, 0.strncmp.out, 0.valcmp.out) produce output that lacks a summary section.
> The runall.sh (or runall.c) utility should be able to compare the output of these tests against a reference file in the same manner that the output is compared for examples.
> An extension of this concept is that it might make sense to unify the logic used to check the test and example results, so that the same process would be used for both tests and examples.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira