home *** CD-ROM | disk | FTP | other *** search
Text File | 1995-09-28 | 1.3 KB | 60 lines | [TEXT/ttxt] |
- OOFILE test coverage issues
-
- With and without blobs detects
- - dependency on non-blob data
- - failure to propagate blob info, update blobs file
- - unable to cope with no blobs present (eg: mBlobFields==null)
-
-
- NOTFORCE vs FPUTFGET
- - detects dependency on writing to disk
- - tests locking
-
- OOF_Debug does lots of internal validation of parameters.
-
- Linking with a SmartHeap debugging library, and defining OOF_SmartHeap does a
- LOT of heap validation, for example after every low-level memcpy or strcpy.
-
-
- Specific test plan:
- (Symantec/Win32 and Mac are coming)
-
- Run all ooftst programs:
- 1) CodeWarrior (Mac)
- - single-user
- 1.1 - with OOF_Debug & SmartHeap debugging
- 1.2 - without OOF_Debug
-
- - multi-user filesharing
- 1.3 - with OOF_Debug & SmartHeap debugging
- 1.4 - without OOF_Debug
-
-
- 2) Borland (Windows 16-bit)
- - single-user
- 2.1 - with OOF_Debug & SmartHeap debugging
- 2.2 - without OOF_Debug
-
- - multi-user filesharing
- 2.3 - with OOF_Debug & SmartHeap debugging
- 2.4 - without OOF_Debug
-
-
- 3) g++ (SunOS)
- - single-user
- 3.1 - with OOF_Debug
- 3.2 - without OOF_Debug
-
- - multi-user filesharing
- 3.3 - with OOF_Debug
- 3.4 - without OOF_Debug
-
-
-
- 4) Portability
- copy files from Win16 to Mac to Unix to test endian portability
- (tests 1, 2, 6, 7 & 12)
-
- copy same files from Unix to Mac to Win16 as a verification
- (more likely to break the other way around)
-