Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #27870
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Hayes tester fails |
| Date | 2014-01-13 16:18 +0000 |
| Organization | Institut fuer Computersprachen, Technische Universitaet Wien |
| Message-ID | <2014Jan13.171841@mips.complang.tuwien.ac.at> (permalink) |
| References | <lah624$s2s$2@speranza.aioe.org> <2014Jan8.155803@mips.complang.tuwien.ac.at> <lam1un$vdf$1@speranza.aioe.org> <2014Jan9.135754@mips.complang.tuwien.ac.at> <laqjkl$nqs$1@speranza.aioe.org> |
"Ed" <invalid@invalid.com> writes:
>Anton Ertl wrote:
>> "Ed" <invalid@invalid.com> writes:
>> > Forth 2012 RC2:
>> >
>> > Proposals Process
>> > [..]
>> > Testing:
>> > This should test the feature/words you propose, in particular, it should test
>> > boundary conditions. Where possible test cases should be written to conform
>> > with John Hayes tester.f test harness."
>> >
>> >Clearly the 200x TC believes such testing is meaningful.
>>
>> Yes, testing is meaningful and useful, even if it does not prove the
>> absence of bugs.
>
>What does the 200x TC hope to derive from tests written in Hayes format
The Hayes tester is quite useful for writting tests of Forth words in
many cases. The test cases are easier to read than tests written
without a framework (important for the intended purpose, see below),
and the framework gives useful output when a test fails.
The reason why I wanted test cases in proposals where possible is that
proposals written in natural language (as is done in the Forth200x
process) is not very precise. So test cases in Forth are a way of
formally specifying a part of what is intended. Coding test cases,
especially for boundary cases would help clarify the specification and
maybe also make the proponent write more precise text.
Tests may also help implementors to find bugs in their implementation
of the proposal.
Unfortunately, some proposals came without tests, which required extra
rounds in making the text more precise. Maybe we should have insisted
on the tests.
>which will obviously show a positive outcome?
What do you mean by that?
>The only rationale I can
>imagine is that it wants to add the tests to the Hayes suite. What message
>would that send?
Sounds like a rethorical question. So what's your answer?
- anton
--
M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
New standard: http://www.forth200x.org/forth200x.html
EuroForth 2013: http://www.euroforth.org/ef13/
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-08 02:20 +1100
Re: Hayes tester fails "Alex McDonald" <blog@rivadpm.com> - 2014-01-07 21:15 +0000
Re: Hayes tester fails "Alex McDonald" <blog@rivadpm.com> - 2014-01-07 21:20 +0000
Re: Hayes tester fails anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-01-08 14:58 +0000
Re: Hayes tester fails "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2014-01-08 19:53 -0500
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-09 21:49 +1100
Re: Hayes tester fails anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-01-09 12:57 +0000
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-11 16:06 +1100
Re: Hayes tester fails "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2014-01-11 10:28 -0500
Re: Hayes tester fails anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-01-13 16:18 +0000
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-15 10:29 +1100
Re: Hayes tester fails "Alex McDonald" <blog@rivadpm.com> - 2014-01-15 00:00 +0000
Re: Hayes tester fails AKK <akk@nospam.org> - 2014-01-15 02:06 +0100
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-19 01:33 +1100
Re: Hayes tester fails anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-01-18 16:58 +0000
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-21 00:09 +1100
Re: Hayes tester fails "Alex McDonald" <blog@rivadpm.com> - 2014-01-20 14:36 +0000
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-25 22:53 +1100
Re: Hayes tester fails "Alex McDonald" <blog@rivadpm.com> - 2014-01-25 23:21 +0000
Re: Hayes tester fails anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-01-21 14:50 +0000
Re: Hayes tester fails "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2014-01-15 02:40 -0500
Re: Hayes tester fails "Elizabeth D. Rather" <erather@forth.com> - 2014-01-14 21:52 -1000
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-19 00:10 +1100
Re: Hayes tester fails Andrew Haley <andrew29@littlepinkcloud.invalid> - 2014-01-15 03:28 -0600
Re: Hayes tester fails "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2014-01-11 10:30 -0500
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-13 10:45 +1100
Re: Hayes tester fails Howerd <howerdo@yahoo.co.uk> - 2014-01-09 02:51 -0800
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-09 22:12 +1100
Re: Hayes tester fails Howerd <howerdo@yahoo.co.uk> - 2014-01-09 06:44 -0800
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-11 16:14 +1100
Re: Hayes tester fails Howerd <howerdo@yahoo.co.uk> - 2014-01-11 02:35 -0800
Re: Hayes tester fails Coos Haak <chforth@hccnet.nl> - 2014-01-11 13:46 +0100
Re: Hayes tester fails "Ed" <invalid@invalid.com> - 2014-01-13 11:16 +1100
csiph-web