This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Idea for testing
- From: Charles Turner <chturne at gmail dot com>
- To: kawa at sources dot redhat dot com
- Date: Mon, 16 Jul 2012 16:51:25 +0100
- Subject: Idea for testing
After the RunTestScript patches the other day, the following occurred to me:
---
After I've written or modified some code, my first testing strategy is
typically to sit down and hit the code will all kinds of
input. I then use the result of these interactions as a start for
writing test cases. What if you had a program that watched the
terminal as you were typing. It would generate RunTestScript-esqe code
automatically for you. I'd like it to work along these lines
> (some expression)
; ouput1
> (testscript:log) ; the above assume wasn't horrid error output, and
; instead expected behaviour I'd like to test in
; the future, so log it.
> (some expression)
; horrid error output
> (some other expression) ; must explicity log the previous I/O if you
; want to generate the test
Lots of details to be worked out, but what do think of it as a possibility?