diff options
| author | Thomas Schwinge <thomas@schwinge.name> | 2011-03-26 00:52:08 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@schwinge.name> | 2011-03-26 00:52:08 +0100 |
| commit | 817df620bedae9c1daa0497f64a901d51e5bd2dd (patch) | |
| tree | f59d1ab04787e8d50eeb2e1449d0967e896662da /open_issues/unit_testing.mdwn | |
| parent | 10288350709d006710bcdfb747ba9d1a1208d69b (diff) | |
Some more IRC discussions.
Diffstat (limited to 'open_issues/unit_testing.mdwn')
| -rw-r--r-- | open_issues/unit_testing.mdwn | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/open_issues/unit_testing.mdwn b/open_issues/unit_testing.mdwn index a5ffe19d..feda3be4 100644 --- a/open_issues/unit_testing.mdwn +++ b/open_issues/unit_testing.mdwn @@ -320,3 +320,23 @@ freenode, #hurd channel, 2011-03-07: this, and just generally though that some sort of automated testing is needed, and thus started collecting ideas. <tschwinge> antrik: You're of course invited to fix that. + +IRC, freenode, #hurd, 2011-03-08 + +(After discussing the [[anatomy_of_a_hurd_system]].) + + <antrik> so that's what your question is actually about? + <foocraft> so what I would imagine is a set of only-this-server tests for + each server, and then we can have fun adding composite tests + <foocraft> thus making debugging the composite scenarios a bit less tricky + <antrik> indeed + <foocraft> and if you were trying to pass a composite test, it would also + help knowing that you still didn't break the server-only test + <antrik> there are so many different things that can be tested... the + summer will only suffice to dip into this really :-) + <foocraft> yeah, I'm designing my proposal to focus on 1) make/use a + testing framework that fits the Hurd case very well 2) write some tests + and docs on how to write good tests + <antrik> well, doesn't have to be *one* framework... unit testing and + regression testing are quite different things, which can be covered by + different frameworks |