One of the most important task in software development is testing. Without testing developers would not know about certain bugs that they themselves might not be encountering. It is also very important in large projects such as Operating Systems where regresions can often crop up un noticed. It is important to find and quickly deal with regressions as these are easier to fix when their cause is known(ie. a recent commit). Up ahead we'll start of with the basics.
Now I know what most of you are thinking, hardware. Now we don't have anything against hardware, ReactOS should and in most cases(while you cross your fingers) does, but we can't be sure about YOUR hardware. We can't know if you misconfigured your BIOS, or $insert_hardware_manufacturer "tweaked" the hardware somehow. Right now ReactOS is in too early a stage to worry about such things. So we use Virtual Machines to do most of the testing, not only because of the above reason, but it's also more convinient for most people.
- Qemu 0.8.2 (a slight bug might affect video in qemu 0.9.0)feb.28,2007
- Vmware Server
- Vmware Workstation
- Vmware player
Other Virtual Machines are acceptable as long as a developer has access to it.
Write some guidelines here.
Before you start any test you need to know what is going on, why and how the test is failing. The most important way to get information about an issue or bug is the debug output. When compiled with DBG = 1, and booted in debug mode ReactOS can send text to a file, the screen, or the serial port. For more information on configuring this please refer to http://www.reactos.org/wiki/index.php/Debugging
Getting more information
See building ReactOS...How to enable more debugging. what to debug...
How to Test
ready made tests
wine testing framwork ReactOS Test apps. rosapps.
3rd party apps
about 3rd party apps
Write your own tests
learn how to code. http://www.reactos.org/wiki/index.php/Writing_tests
How to report a Bug
what to do with your debug log. http://www.reactos.org/wiki/index.php/File_Bugs