2 Made by Timothy Manning <timothy@yaffs.net> on 04/11/2010
7 test_yaffs_chmod_ENOENT
8 test_yaffs_chmod_ENOTDIR
11 test_yaffs_fchmod_EBADF
12 test_yaffs_fchmod_EINVAL
15 test_yaffs_mount_ENODEV
16 test_yaffs_mount_ENAMETOOLONG
17 test_yaffs_mount_EBUSY //caused by trying to mount a new mount point with a mount point already mounted.
20 test_yaffs_access_ENIVAL
21 test_yaffs_access_ENOTDIR
22 test_yaffs_access_ENOENT
24 test_yaffs_close_EBADF
27 test_yaffs_fdatasync_EBADF
30 test_yaffs_fsync_EBADF
33 test_yaffs_ftruncate_EBADF
34 test_yaffs_ftruncate_ENIVAL
35 test_yaffs_ftruncate_EFBIG
38 test_yaffs_lseek_EBADF
39 test_yaffs_lseek_EINVAL
40 test_yaffs_lseek_EFBIG
43 test_yaffs_open_EEXIST
44 test_yaffs_open_EISDIR
45 test_yaffs_open_ENAMETOOLONG
46 test_yaffs_open_ENOENT
47 test_yaffs_open_ENOTDIR
48 test_yaffs_open_EINVAL
49 test_yaffs_open_EINVAL2 //the function open has two modes which can be set, so two tests are needed.
53 test_yaffs_read_EINVAL
57 test_yaffs_stat_ENOENT
58 test_yaffs_stat_ENOTDIR
61 test_yaffs_fstat_EBADF
64 test_yaffs_truncate_ENOTDIR
65 test_yaffs_truncate_EISDIR
66 test_yaffs_truncate_ENOENT
67 test_yaffs_truncate_ENIVAL
68 test_yaffs_truncate_EFBIG
71 test_yaffs_unlink_EISDIR
72 test_yaffs_unlink_ENAMETOOLONG
73 test_yaffs_unlink_ENOENT
74 test_yaffs_unlink_ENOTDIR
77 test_yaffs_unmount_ENODEV
78 test_yaffs_unmount_ENAMETOOLONG
79 test_yaffs_umount_EBUSY //cause by having a file handle open and then trying to unmount yaffs.
82 test_yaffs_write_EBADF
87 test_yaffs_fchmod_EACCES
89 test_yaffs_chmod_EACCES
90 test_yaffs_chmod_ELOOP
91 test_yaffs_chmod_ENAMETOOLONG
94 test_yaffs_lstat_EACCES
95 test_yaffs_lstat_ENOTDIR
96 test_yaffs_lstat_ENAMETOOLONG
97 test_yaffs_lstat_ENOENT
98 test_yaffs_lstat_ELOOP
101 test_yaffs_readlink_ENOENT
102 test_yaffs_readlink_ENOTDIR
103 test_yaffs_readlink_ELOOP
104 test_yaffs_readlink_ENAMETOOLONG
107 test_yaffs_mkdir_EACCES
108 test_yaffs_mkdir_EEXISTS
109 test_yaffs_mkdir_ELOOP
110 test_yaffs_mkdir_ENAMETOOLONG
111 test_yaffs_mkdir_ENOENT
112 test_yaffs_mkdir_ENOTDIR
113 test_yaffs_mkdir_EROFS
116 test_yaffs_symlink_EACCES
117 test_yaffs_symlink_EEXISTS
118 test_yaffs_symlink_ELOOP
119 test_yaffs_symlink_ENAMETOOLONG
120 test_yaffs_symlink_ENOENT
121 test_yaffs_symlink_ENOTDIR
122 test_yaffs_symlink_EROFS
125 test_yaffs_mknod_EACCES
126 test_yaffs_mknod_EEXIST
127 test_yaffs_mknod_EINVAL
128 test_yaffs_mknod_ELOOP
129 test_yaffs_mknod_ENAMETOOLONG
130 test_yaffs_mknod_ENOENT
131 test_yaffs_mknod_ENOTDIR
132 test_yaffs_mknod_EROFS
135 test_yaffs_mount2_EINVAL
136 test_yaffs_mount2_ENOTDIR
137 test_yaffs_mount2_ENOENT
138 test_yaffs_mount2_ENODEV
139 test_yaffs_mount2_ENAMETOOLONG
142 test_yaffs_unmount2_ENOENT
143 test_yaffs_unmount2_ENOTDIR
144 test_yaffs_unmount2_ENODEV
145 test_yaffs_unmount2_EINVAL
148 test_yaffs_remount2_ENOENT
149 test_yaffs_remount2_ENOTDIR
150 test_yaffs_remount2_ENODEV
151 test_yaffs_remount2_EINVAL
154 test_yaffs_sync_ENOENT
155 test_yaffs_sync_ENOTDIR
158 test_yaffs_freespace_ENOENT
159 test_yaffs_freespace_ENOTDIR
161 test_yaffs_totalspace
162 test_yaffs_totalspace_ENOTDIR
163 test_yaffs_totalspace_ENOENT
165 test_yaffs_inodecount
166 test_yaffs_inodecount_ENOTDIR
167 test_yaffs_inodecount_ENOENT
178 test_yaffs_link_EACCES
179 test_yaffs_link_EEXISTS
180 test_yaffs_link_ELOOP
181 test_yaffs_link_EMLINK //should not happen on yaffs
182 test_yaffs_link_ENAMETOOLONG
183 test_yaffs_link_ENOENT
184 test_yaffs_link_ENOTDIR
185 test_yaffs_link_EPERM
186 test_yaffs_link_EROFS
189 test_yaffs_rmdir_EACCES
190 test_yaffs_rmdir_EBUSY
191 test_yaffs_rmdir_ENVAL
192 test_yaffs_rmdir_ENOENT
193 test_yaffs_rmdir_ENOTDIR
194 test_yaffs_rmdir_ENOTEMPTY
195 test_yaffs_rmdir_EROFS
198 test_yaffs_rename_EACCES
199 test_yaffs_rename_EINVAL
200 test_yaffs_rename_ELOOP
201 test_yaffs_rename_EMLINK
202 test_yaffs_rename_ENOENT
203 test_yaffs_rename_ENOTDIR
204 test_yaffs_rename_EEXISTS or EPERM
205 test_yaffs_rename_EROFS
213 test_yaffs_flush_EBADF
215 test_yaffs_fchmod_EACCES
216 test_yaffs_fchmod_ELOOP
219 test_yaffs_open_EACCES
220 test_yaffs_open_ENOSPC
221 test_yaffs_open_ELOOP
222 test yaffs_open_running_out_of_handles error
224 test_yaffs_close //This function has already been called by the time this test is reached.
226 test_yaffs_stat_ELOOP
227 test_yaffs_stat_EACCES
228 test_yaffs_stat_ENAMETOOLONG
232 test_yaffs_read_EFBIG
233 test what happens if you read off the end of the file?
236 test_yaffs_pread_EBADF
237 test_yaffs_pread_EINVAL
238 test_yaffs_pread_EFBIG
240 test_yaffs_write_EFBIG
241 test_yaffs_write_EINVAL
242 What happens when you run out of space?
244 test_yaffs_write_EBADF
246 test_yaffs_pwrite_EFBIG
247 test_yaffs_pwrite_EINVAL
249 test_yaffs_unlink_EACCES
250 test_yaffs_unlink_ELOOP
251 test_yaffs_unlink_ENOMEM
253 test_yaffs_stat_EACCES
254 test_yaffs_stat_ELOOP
256 test_yaffs_access_EACCESS
257 test_yaffs_access_ELOOP
258 test_yaffs_access_ENAMETOOLONG
259 test_yaffs_access_ENOENT_generated_with_a_dangling_symbloic_link
261 test_yaffs_ftruncate_EACCES
264 test_yaffs_truncate_EACCES
265 test_yaffs_truncate_ELOOP
266 test_yaffs_truncate_ENAMETOOLONG
267 Add a truncate function for truncating a file size to -1.
269 What happens if a handle is opened to a file and the file is then deleted?
270 Check to see if yaffs generates an error code for no reason.
271 What happens when a file is opened with no modes set?
272 Add a test where a directory is moved. /fluffy/box. move "fluffy" to "/fluffy/frog".
273 What happens when yaffs is unmounted twice?
275 What happens when open a handle, unmount yaffs and then try to use the handle?
277 What happens when a mount point is mounted using mount2 with read only mode set and then a file is chmoded?
280 First create the test .c and .h file.
281 The file name and test function name should be the same.
282 This name should follow one of these formats:
283 Test_yaffs_[function of yaffs which is been tested]
284 Test_yaffs_[function of yaffs which is been tested]_[error trying to be generated]
286 The .c file needs to contain two functions.
287 The first function needs to contain the code for the main test and will
288 return -1 on a failure and 0 or greater on a success.
289 The second function needs contain the code for cleaning up after the test.
290 Cleaning up may include closing some open handles, recreating a file, ect.
291 This second function needs to return -1 on a failure and 0 or greater on success.
293 The name of first function needs to be called the same as the file
294 name (without the .c or .h)
295 The second function's name needs be the same as the first function but
296 with "_clean" added on the end.
298 So if a test is been created for the yaffs function yaffs_foo() then
301 Contains int test_yaffs_foo(void); int test_yaffs_foo_clean(void);
303 Which includes "lib.h", "yaffsfs.h" header files.
305 Next write the test code in these files then add these files to the Makefile.
307 Add the name of the test files' object file (test_yaffs_foo.o ) to the
308 TESTFILES tag around line 50 of the Makefile.
310 Now add the test functions to the test_list[] array in quick_tests.h
311 The order of the tests matters. The idea is to test each yaffs_function
312 individualy and only using tested yaffs_components before using this new
314 This array consists of:
315 {[test function], [the clean function], [name of the tests which will be printed when the test fails]},
317 So add this line to the test_list[]: {test_yaffs_foo, test_yaffs_foo_clean, "test_yaffs_foo"},
319 Also include the test's .h file in the quick_test.h file: #include "test_yaffs_foo.h"
321 The test file should now make and run(you may need to make clean first).
325 PS: yaffs_foo() is a made up function for this README (in case you want
326 to find this function in yaffs).