timo.kreuzer at web.de
Tue Jul 31 10:29:14 CEST 2007
I am currently working on an api testing framework. Mostly working on
win32k native api test atm, but it shall also include api testing for
gdi32, user32, etc.
win32k test will work with syscall tables to decide on runtime how to
perform a syscall by comparing OS version and build number. On ros
syscalls will be done by linking to w32kdll wich is compiled from
autogenerated win32k.S, so there is no need to update the syscall list
for ros all the time.
The testing framework will include tests, regression tests, and an api
status output is planned.
BTW: I have a suggestion:
1. move w32ksvc.db from nci folder to win32k folder, where it belongs imo
2. autogenerate win32k.S in lib\win32k and compile a static lib there
(no need to compile it more than once)
same for sysfuncs.lst
Magnus Olsen schrieb:
> The problem we fail around 50%-70% of all winetest toghter. a update to
> winetest at moment are not imported
> and we are also plan write test kit for win32k with real syscall test in
> windows and reactos. it mean we will found
> the real bugs in our win32k, so it can behoir more like windows nt win32k,
> next step is todo a over view
> of gdi32, user32 and few part of kernel32, also we need writing big test
> for thuse part,
> We need the automatic testing farm for each build, it is testing system
> that are ready but missing test kit.
> we got janderwald to thanks for the new automatic testing kit and we need
> testing it now and write testkit
> for each api in reactos, it mean we will getting a real large testing farm
> for reactos.
More information about the Ros-dev