
|
[openbeosstorage]
||
[Date Prev]
[04-2002 Date Index]
[Date Next]
||
[Thread Prev]
[04-2002 Thread Index]
[Thread Next]
[openbeosstorage] Re: BNode:set_fd and other things
- From: Tyler Dauwalder <tyler@xxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Fri, 19 Apr 2002 23:11:13 -0700
I never answered this, did I?
> > Yes, I know what you mean. I haven't done any tests to figure out
> > whether or not it's necessary.
> That leads to the general question of integration tests. Some tests of
> this kind are already included in the unit tests, but e.g. in the case of
> BFile or BDirectory I don't test any inherited functionality. Perhaps some
> of the base class (BNode, BEntryList,...) tests can be made reusable for
> derived classes? E.g. providing a function that takes a pointer to a base
> class instance and performs tests on it.
My plan has been to leave this until we're done implementing.
I wouldn't mind having the unit tests set up to allow inherited functionality
to be tested though. I just haven't planned ahead for any such thing. I'll be
polishing up the BNode and BEntry tests shortly, and will address that for
those classes at that time.
-Tyler
|

|