Difference between revisions of "Testing Central"

From ReactOS Wiki
Jump to: navigation, search
Line 183: Line 183:
| style="background: #FDD017;" |[http://downloads.uptodown.net/dm/farmanager-1.70.exe FAR Manager 1.7]
| style="background: #FDD017;" |[http://downloads.uptodown.net/dm/farmanager-1.70.exe FAR Manager 1.7]
| {{StatusCell|Unknown}} | NTD
| http://www.reactos.org/compat/?show=submit&version=237
| style="background: #FDD017;" |[http://www.rarlab.com/rar/wrar380.exe Winrar 3.80]
| {{StatusCell|Stable}} | <b>wojo664</b> Tested in CirtualBox 3.1.8, WinRar 3.80 Works rather stable, but has some problems. This is what I find so far:
| {{StatusCell|Stable}} | <b>wojo664</b> Tested in CirtualBox 3.1.8, WinRar 3.80 Works rather stable, but has some problems. This is what I find so far:
Line 192: Line 197:
- strange window "Add the data the entry? " after exporting settings
- strange window "Add the data the entry? " after exporting settings
- after exporting the settings after confirmation dialog, clicking "yes" in the "Add the data the entry" seems to lock the WinRar.
- after exporting the settings after confirmation dialog, clicking "yes" in the "Add the data the entry" seems to lock the WinRar.
| http://www.reactos.org/compat/?show=submit&version=237
| style="background: #FDD017;" |[http://www.rarlab.com/rar/wrar380.exe Winrar 3.80]
| {{StatusCell|Unknown}} | NTD
| http://www.reactos.org/compat/?show=submit&version=903
| http://www.reactos.org/compat/?show=submit&version=903

Revision as of 13:01, 26 June 2011

Welcome to the Testing Central! Here we can coordinate our efforts, this is useful in case you don't have access to or aren't in IRC. To fill the tables just follow the easy understandable guidelines. If you don't understand them please ask in the IRC channel #reactos-testers. Thanks!


Here any developer can ask testers for a test: i.e. a testbox, an application, or a patch. The request can be fulfilled just by a developer. Testers can fill in the result report. While you are about to test a revision, change the tester field and set the LRT to T+number(i.e. T40020) so other testers know you are testing this revision. After testing and knowing the result change the T to R (i.e. R40020) and update the result field.

  • DEV: Name of the developer who asked for a test.
  • Request: A short description ( i.e. Test for FF mouse bug).
  • Application/TestBox: A link to the application (if needed), please use Wiki syntax.
  • Way of Testing: A link to a Bugzilla report where the testing steps are described or a short overview of how to test. Please try to keep it short.
  • Tester: The name of the tester who did the testing.
  • LRT (Last Revision Tested): Add a letter before the number, T means currently testing, R means tested
  • RES: Results of the test: failed or no failure.

Dev Request App/TestBox Way of Testing Tester LRT Res:
Devname Short Description Download it:HERE Open the menu and check if font spacing still wrong, etc. TestrNam r40xxx FAIL
rafalh Test newest UniATA 0.41b2 (without ReactOS specific hacks) http://www.megaupload.com/?d=5ZZF478R Check for regressions in real hardware and all virtual machines. - - -


Here any developer or tester who finds a regression can add a line, so that testers can easily keep track of running regression tests and to allow the coordination of the efforts. If you discovered the regression then add your name, the regression description and in which Virtual Machines did you test it. Also add a revision where the bug was not present and the failing one (if you have that information). If you are regression testing, then add (don't delete others testing efforts) the testing revision that you are going to test in the testing field (add your 4 first nick letters). If there are more testers regtesting you will see the revisions they are going to test. It will help you to choose the most interesting revision. We recommend the binary search. When you finished testing a revision, update the Working/Failing and the VMW/QEM/VBX columns. Also delete your testing revision number from the testing.

  • Name: The name of the developer or tester who found the regression.
  • Regression: Description of the regression, or a link to a Bugzilla report.
  • VMWA : "Yes" if the regression happens in VMware, "NO" if doesn't. "NTD" if Not Tested.
  • QEMU : "Yes" if the regression happens in QEMU, "NO" if doesn't. "NTD" if Not Tested.
  • VBOX : "Yes" if the regression happens in VirtualBox, "NO" if doesn't. "NTD" if Not Tested.
  • RHDW : "Yes" if the regression happens in Real Hardware, "NO" if doesn't. "NTD" if Not Tested.
  • WRKs: Number of the revision where the bug isn't present.
  • Fails: Number of the revision where the bug is failing.
  • Testing: Before going to test (before downloading the revision indeed) add your number and your three letters here (i.e. 40100VIC).
Name Regression VMWA QEMU VBOX RHDW Works Fails Testing
DEV/TES Regression description YES YES NTD NTD 40102 40235 40180CAE,40210VIC,40150AMI,
Sh4ring4n mshtml freezes NTD NTD YES NTD r50311 r50312 50481SH4, 50458SH4, 50411SH4, 50381SH4, 50311SH4, 50365SH4, 50319SH4, 50312SH4
Ey3 Acrobat Reader 6 NTD NTD NTD YES r39653 r39654 Still present in r43812. Guilty commit: r39654 - "Fixes #4114"


Testing APPS is being currently linked to the greatest, impresive, astonishing and new Compatibility Database. So it will keep the Database updated and at the same time we can track easily GoldenApps and CandidateApps. All the Apps has their own links also you can find here a list of all of them.

This section is divided in 2 tables.

  • GoldenAPPS: The "GoldenApps Table" tracks the most important working apps which nowadays are working correctly on ReactOS.
  • CandidateAPPs: The "CandidateAPPs Table" tracks non working apps which must be tracked because of their importance. They will be moved to "GoldenApps" when they start working on ReactOS.


  • App : Name of the application and the link to download it.
  • Latest Working Revision: Latest revision where the App was working.
  • Status: It shows if the App has been tested with the "Golden Revision" (NTD: Not tested) and if it Worked(YES) or Not(NO).
  • Link to Compatibility Database(CD): Link to the App's Form in the CD to fill.


During this Week the "Golden Revision" will be: 52433

App Latest working revision Status Link to Compatibility Database
Firefox 52433 Works with issues http://www.reactos.org/compat/?show=submit&version=54
Firefox 3.0.11 NTD http://www.reactos.org/compat/?show=submit&version=49
K-Meleon 1.5.2 NTD http://www.reactos.org/compat/?show=submit&version=837
Adobe Reader 7.1 NTD http://www.reactos.org/compat/?show=submit&version=838
Foxit Reader 2.1 NTD http://www.reactos.org/compat/?show=submit&version=200
Adobe Flash Player 10 NTD http://www.reactos.org/compat/?show=submit&version=839
Thunderbird NTD http://www.reactos.org/compat/?show=submit&version=1050
Sunbird 0.9 NTD http://www.reactos.org/compat/?show=submit&version=840
Abiword 2.6.4 NTD http://www.reactos.org/compat/?show=submit&version=841
FAR Manager 1.7 NTD http://www.reactos.org/compat/?show=submit&version=237
Winrar 3.80 wojo664 Tested in CirtualBox 3.1.8, WinRar 3.80 Works rather stable, but has some problems. This is what I find so far:

- Assertion after "Viewing" an .exe (Assertion 'MmAvailablePages != 0' failed at ntoskrnl/mm/ARM3/pfnlist.c line 356 �[7h�Entered debugger on embedded INT3 at 0x0008:0x80901c46. kdb:> (ntoskrnl/kd/kdio.c:302) ) - broken comments after convert to sfx - partially working help - strange window "Add the data the entry? " after exporting settings - after exporting the settings after confirmation dialog, clicking "yes" in the "Add the data the entry" seems to lock the WinRar.

7-Zip 4.65 NTD http://www.reactos.org/compat/?show=submit&version=116
DosBox 0.72 NTD http://www.reactos.org/compat/?show=submit&version=557
Mirc 6.35 NTD http://www.reactos.org/compat/?show=submit&version=842
Samba-TNG NTD http://www.reactos.org/compat/?show=submit&version=281
IrfanView 4.23 NTD http://www.reactos.org/compat/?show=submit&version=25
Notepad Lite 3.3.1 NTD http://www.reactos.org/compat/?show=submit&version=654
SeaMonkey 1.1.17 NTD http://www.reactos.org/compat/?show=submit&version=843
FileZip 3.06 NTD http://www.reactos.org/compat/?show=submit&version=1051
AIDA32 3.94 NTD http://www.reactos.org/compat/?show=submit&version=902
UniversalVW NTD http://www.reactos.org/compat/?show=submit&version=1243
SciTE 1.77 NTD http://www.reactos.org/compat/?show=submit&version=904
VLC Media Player 0.8.6i NTD http://www.reactos.org/compat/?show=submit&version=192


Vic,Jedi,(Bit) Opera 9.64 44317 NTD NTD YES YES YES VMWA/VBOX/RHDW:None VMWA/VBOX/ViPC7/RHDW:None - @Jedi and Vic: doesn't it crash for you if you type something in Opera?- basisbit

It hangs - Jedi

Vic/Bit/Ey3 Chrome 10.0.648.204 44317 NO NTD NO NTD NTD VMWA: None. HW: It keeps saying "Initialising" in a loop.
Ey3/Bit Word Viewer 2003 44317 NO NTD NO NTD NO All: none VMWA: It doesn't launch. #4587
Ey3/Bit Excel Viewer 2003 44317 NO NTD NO NTD NO HW: None HW: It doesn't launch. Then it tries to run in safe mode, but fails again.#4466
Ey3 Powerpoint Viewer 2003 42470 YES NTD YES NTD YES VBOX/VMWA/HW: None VBOX/VMWA/HW: None - not online at microsoft.com any more...
Ey3/Bit OpenOffice 3.3.0 44317 NO NTD NO NTD NO HW: Installation fails because MSVCR90.dll was not found.
Vic/Bit, Jedi-to-be Total Commander 7.56a 42470


Vic/Bit Net Framework 3.0 42470 NO NTD NO NTD NO VMWA: Error:"Insuficient privileges." #4470
Vicmarcal, Jedi-to-be Java 6.25 41233


NO NTD NTD NO NTD VMWA,ViPC7:None VMWA,ViPC7: Error the memory could not be read #4176
Ey3 Microsoft Office 2003 43812 NO NTD NO NTD NO HW: It does no longer freeze. It stops telling "Installation interrupted because of an error"

Application related bug reports

Main article: File Bugs

Make sure the bug happens only in ReactOS and is not a bug that also happens in Windows. If it happens in both then you should consult with the applications support or Dev team. You should, if possible, try different versions of Windows, making sure to use versions the application is meant to work with.

If the bug happens on some versions of Windows and in ReactOS, it is probably not ReactOS.

  • Note all details of your testing on different versions of windows when filing your bug report
  • Try a recent nightly build
  • With your nightly build gather a debug log from ReactOS
  • Make your bug report.
    • Attach your debug log detailed notes from Windows tests
    • Record full versions of all software involved (usually something like "2.34.4567.562 rev 19382 RC2 ..."): VMware, ReactOS SVN number, failing application.
    • Take screen shots if applicable of how the app failed, how it worked or failed differently in Windows than ReactOS and attach them.
  • If it is a commercial application that is closed source and cost money then you may be the one that has to do all Debugging for ReactOS and possibly the one whom submits the patches.
  • Give a appropriately formated copy of the bug report to the applications support or Dev team that made the app.

What makes an application important

The applications being tracked are not being tracked because of only their popularity or because someone likes the application a lot, there are more important reasons.

  • The application makes use of some critical part of the operating system, and it may be able to show progression or regression that will affect many other applications.
  • The application meets common needs that are needed on most systems.
  • The application is needed for development of the operating system.

Because tracking too many applications at this level of detail is difficult you should not just add another application to the list. New additions to this list should be discussed with Fireball, Caemyr, vicmarcal on IRC or their talk page. But before that you should ask yourself these questions:

  • Will this application test many different parts of the operating system?
  • Does this application do something that will help with testing or development by tracking its usage?
  • Is there a tracked application that already does this?
  • Is there a good reason for wanting this particular application to be tracked?

If you can answer yes to two of the first three and the fourth then you might consider asking in IRC about adding it.

Tracking other applications

You can track the app yourself but note that it will be your responsibility to test your applications and report any bugs. You must also make sure the bugs are not reproducible on the current version/versions of Windows, in case the bug is in the application and not in the operating system. If you are still interested your best option is to track the bug on your user page. You can copy the above apps table and edit it for this.