[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: koffice/kspread/tests
From:       Ariya Hidayat <ariya () kde ! org>
Date:       2004-09-14 16:55:18
Message-ID: 41472276.7080805 () kde ! org
[Download RAW message or body]


> ALL the information for the test should be hardcoded in the test, in order
> to let it be as small of a unit (to test) as possible.
> This also makes coding the actual test a LOT simpler (as no code has to
> be written validating the input) which allows you to write many little
> tests.

So I can't have a test which works with the current document? I find 
that will be handy, e.g. check whether cell storage (i.e. currently in 
cluster system) is proper or not. Or is this not the way a test 
framework should do?

Best regards,

Ariya Hidayat

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]