Difference between revisions of "Testing Central"

From ReactOS Wiki
Jump to: navigation, search
(→‎REGRESSION TESTING)
(fixed some grammar and spelling issues.)
Line 1: Line 1:
 
Welcome to the Testing Central!
 
Welcome to the Testing Central!
−
Here we can coordinate our efforts, indeed if you aren't in the IRC.
+
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!
 
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!
  
Line 6: Line 6:
  
 
Here any developer can ask testers for a test: i.e. a testbox, an application, or a patch.  
 
Here any developer can ask testers for a test: i.e. a testbox, an application, or a patch.  
−
The request can be fullfiled just by a developer.  
+
The request can be fulfilled just by a developer.  
−
Testers just can fullfil the result of the request.
+
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.
 
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: Developer name who asked for a test
+
* DEV: Name of the developer who asked for a test.
−
* Request: A short description ( i.e. Test for FF mouse bug)
+
* Request: A short description ( i.e. Test for FF mouse bug).
 
* Application/TestBox: A link to the application (if needed), please use Wiki syntax.
 
* 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 way is described or a short overview how to test. Please try to keep it short.
+
* 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.
 
* 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
 
* LRT (Last Revision Tested): Add a letter before the number, T means currently testing, R means tested
−
* RES: Results of the test: fail or no fail.
+
* RES: Results of the test: failed or no failure.
  
  
Line 32: Line 32:
 
| Short Description
 
| Short Description
 
| Download it:HERE
 
| Download it:HERE
−
| Open the menu and chek if the Blabla is still wrong
+
| Open the menu and check if font spacing still wrong, etc.
 
| TestrNam
 
| TestrNam
 
| r40xxx
 
| r40xxx
Line 40: Line 40:
 
== REGRESSION TESTING ==
 
== REGRESSION TESTING ==
  
−
Here any developer or tester who finds a regression can add a line, so that testers can easily keep track of running regression test and to allow a coordination of efforts.
+
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 tested it. Also add a revision where the bug was not present and the failing one (if you have that information).
+
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.  
+
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 [http://en.wikipedia.org/wiki/Binary_search binary search].
−
When you finished testing a revision, then update the Working/Failing and the VMW/QEM/VBX. Also delete your testing revision number from the testing.
+
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.
 
* Name: The name of the developer or tester who found the regression.
 
* Regression: Description of the regression, or a link to a Bugzilla report.
 
* Regression: Description of the regression, or a link to a Bugzilla report.
−
* VMWA : "Yes" if the regression happens in VMware, "NO" if doesnt. "NTD" if Not Tested.
+
* 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 doesnt. "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 doesnt. "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 doesnt. "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.
 
* WRKs: Number of the revision where the bug isn't present.
 
* Fails: Number of the revision where the bug is failing.
 
* Fails: Number of the revision where the bug is failing.
−
* Testing: Before going to test (indeed before downloading the revision) add your number and your 3 letters here (i.e. 40100VIC).
+
* Testing: Before going to test (before downloading the revision indeed) add your number and your three letters here (i.e. 40100VIC).
  
 
{| class="sortable wikitable" border="1" cellpadding="3" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; width: 90%; text-align: left;"
 
{| class="sortable wikitable" border="1" cellpadding="3" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; width: 90%; text-align: left;"
Line 78: Line 78:
 
|-
 
|-
 
| style="background: #ececec;" | vicmarcal
 
| style="background: #ececec;" | vicmarcal
−
| LMarbles doesnt run
+
| LMarbles doesn't run
 
| {{StatusCell|Stable}} | YES
 
| {{StatusCell|Stable}} | YES
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
Line 108: Line 108:
 
|-
 
|-
 
| style="background: #ececec;" | vicmarcal
 
| style="background: #ececec;" | vicmarcal
−
| Opening the Properties on C: drive crash explorer  
+
| Opening the Properties on C: drive crashes explorer  
 
| {{StatusCell|Stable}} | YES
 
| {{StatusCell|Stable}} | YES
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
Line 122: Line 122:
 
This section is divided in 2 tables.
 
This section is divided in 2 tables.
 
* GoldenAPPS: The "GoldenApps Table" tracks the most important '''working apps which nowadays are working correctly''' on ReactOS.
 
* GoldenAPPS: The "GoldenApps Table" tracks the most important '''working apps which nowadays are working correctly''' on ReactOS.
−
* CandidateAPPs: The "CandidateAPPs Table" tracks''' nonworking apps which must be tracked because their importance'''. They will be moved to "GoldenApps" when they begin working 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.
  
  
Line 129: Line 129:
  
  
−
* Name: If you are the first testing an application, put your name here. It will be used to contact you, if needed.
+
* Name: If you are the first testing an application, put your name here. It will be used to contact you if needed.
−
* App : Name of the application and the link to download it. The link must be provided.
+
* App : Name of the application and the link to download it (required).
 
* Rev: Latest revision where the App was working.
 
* Rev: Latest revision where the App was working.
−
* VMWA: Please add a "Yes" if YOU TESTED it in VMware and works, "NO" if it isnt working,"NTD" if no tested
+
* VMWA: Please add a "Yes" if YOU TESTED it in VMware and it works, "NO" if it isn't working,"NTD" if not tested.
−
* QEMU: Please add a "Yes" if YOU TESTED it in Qemu and works,"NO" if it isnt working "NTD" if no tested
+
* QEMU: Please add a "Yes" if YOU TESTED it in Qemu and it works,"NO" if it isn't working "NTD" if not tested.
−
* VBOX: Please add a "Yes" if YOU TESTED it in Virtual Box and works,"NO" if it isnt working "NTD" if no tested
+
* VBOX: Please add a "Yes" if YOU TESTED it in Virtual Box and it works,"NO" if it isn't working "NTD" if not tested.
 
* BUG INSTALLING: - Bug during the installation. Format: "Virtual machine or ALL:Description.Bugreport" Please file a bugreport each time you find a bug. Thanks.
 
* BUG INSTALLING: - Bug during the installation. Format: "Virtual machine or ALL:Description.Bugreport" Please file a bugreport each time you find a bug. Thanks.
−
* BUG WORKING: - Bug when working with the application. Same Format as for "Bug installing"
+
* BUG WORKING: - Bug when working with the application. Same Format as for "Bug installing".
  
 
=== GOLDENAPPS ===
 
=== GOLDENAPPS ===
Line 188: Line 188:
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
−
| -VMWA:It shows the PDF if you click on the mode FullScreen.
+
| -VMWA:It shows the PDF if you click on fullscreen mode.
 
| -VMWA:None
 
| -VMWA:None
 
|-
 
|-
Line 306: Line 306:
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
 
| -VMWA:None
 
| -VMWA:None
−
| -VMWA:Regression.0.3.9:it doesnt launch. {{Bug|4461}}.
+
| -VMWA:Regression.0.3.9:it doesn't launch. {{Bug|4461}}.
 
|-
 
|-
 
| style="background: #ececec;" | Vicmarcal
 
| style="background: #ececec;" | Vicmarcal
Line 393: Line 393:
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
 
| VMWA:None
 
| VMWA:None
−
| VMWA:Doesnt respond. {{Bug|4151}}
+
| VMWA:Doesn't respond. {{Bug|4151}}
 
|-
 
|-
 
| style="background: #ececec;" | Vicmarcal
 
| style="background: #ececec;" | Vicmarcal
Line 402: Line 402:
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
−
| VMWA: Doesnt get install. {{Bug|4117}}
+
| VMWA: Doesn't get installed. {{Bug|4117}}
 
|  
 
|  
 
|-
 
|-
Line 422: Line 422:
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
 
| {{StatusCell|Unknown}} | NTD
−
| VMWA:Possible it doesnt get installed correctly
+
| VMWA:Possibly it doesn't get installed correctly
−
| VMWA: It doesnt launch. {{Bug|4466}}
+
| VMWA: It doesn't launch. {{Bug|4466}}
 
|-
 
|-
 
| style="background: #ececec;" | Vicmarcal
 
| style="background: #ececec;" | Vicmarcal
Line 490: Line 490:
  
 
==What makes an APP Important==
 
==What makes an APP Important==
−
The apps being tracked are not being tracked because of only there popularity or because someone likes the app a lot, there are more important reasons.
+
The apps being tracked are not being tracked because of only their popularity or because someone likes the app a lot, there are more important reasons.
 
* The app 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 apps.
 
* The app 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 apps.
 
* The app meets common needs that are needed on most systems.
 
* The app meets common needs that are needed on most systems.
 
* The app is needed for development of the operating system.
 
* The app is needed for development of the operating system.
  
−
Because tracking too many apps at this level of detail is difficult you should not just add another app to the list. New additions to this list should be discussed with [[Fireball]],[[User:Haos|Caemyr]],[[user:vicmarcal|vicmarcal]] on [http://www.reactos.org/en/community_irc.html IRC] or their talk page. But before you should ask these questions.
+
Because tracking too many apps at this level of detail is difficult you should not add just another app to the list. New additions to this list should be discussed with [[Fireball]],[[User:Haos|Caemyr]],[[user:vicmarcal|vicmarcal]] on [http://www.reactos.org/en/community_irc.html IRC] or their talk page. But before that you should ask yourself these questions:
 
* Will this app test many different parts of the operating system?
 
* Will this app test many different parts of the operating system?
−
* Does this app do something that will help with testing or Development by tracking its usage?
+
* Does this app do something that will help with testing or development by tracking its usage?
−
* Are there no apps that do what this app dose, being tracked Already?
+
* Are there no apps that do what this app does, being tracked already?
 
* Do you have a good reason for wanting this particular app to be tracked?
 
* Do you have a good reason for wanting this particular app to be tracked?
 
If you can honestly answer yes to 2 of the first 3 and the forth then you might consider asking in IRC about adding it.
 
If you can honestly answer yes to 2 of the first 3 and the forth then you might consider asking in IRC about adding it.
−
===My app doesn't meet these requirements but i still want it to be tracked===
+
===My app doesn't meet these requirements but I still want it to be tracked===
−
You can track the app yourself but note that, It will be your responsibility to test your apps 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 app and not in the operating system. If your still interested Copy the following code to your user page and fill it out. You can put multiple appEntry's in to 1 table for more than 1 app. This template is for your benefit and wont currently help anyone else yet, but, it will let you keep track of your apps and associated bugs.
+
You can track the app yourself but note that it will be your responsibility to test your apps 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 app and not in the operating system. If you're still interested copy the following code to your user page and fill it out. You can put multiple app entry's in one table for more than one app. This template is for your benefit and won't currently help anyone else yet, but, it will let you keep track of your apps and associated bugs.
 
<pre><nowiki>
 
<pre><nowiki>
 
{{template:StartAppsTable|
 
{{template:StartAppsTable|

Revision as of 07:35, 21 May 2009

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!

DEVELOPERS REQUEST

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

REGRESSION TESTING

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,
vicmarcal LMarbles doesn't run YES NTD NTD NTD 0.3.8 39550 ---
Ey3 Acrobat Reader 6 NTD NTD NTD YES 39653 39654 Still present in rev40950. Guilty commit: 39654. Fixes bug #4114
vicmarcal Notepad Lite YES NTD NTD NTD 39653 39654 Guilty commit: 39654.Fixes bug #4114
vicmarcal Opening the Properties on C: drive crashes explorer YES NTD NTD NTD 40825 40826 Guilty commit: 40826.

TESTING APPS

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.


If you see an application, which hasn't been tested with a virtual machine that you have installed, then please test it.Then fill the Virtual Machine column,and if you find any Bugs,add them in the debug description(i.e. QEM+VMW: It fails when copying.). If the three virtual machines have the same issue change the QEM+VMW+VBX to ALL.


  • Name: If you are the first testing an application, put your name here. It will be used to contact you if needed.
  • App : Name of the application and the link to download it (required).
  • Rev: Latest revision where the App was working.
  • VMWA: Please add a "Yes" if YOU TESTED it in VMware and it works, "NO" if it isn't working,"NTD" if not tested.
  • QEMU: Please add a "Yes" if YOU TESTED it in Qemu and it works,"NO" if it isn't working "NTD" if not tested.
  • VBOX: Please add a "Yes" if YOU TESTED it in Virtual Box and it works,"NO" if it isn't working "NTD" if not tested.
  • BUG INSTALLING: - Bug during the installation. Format: "Virtual machine or ALL:Description.Bugreport" Please file a bugreport each time you find a bug. Thanks.
  • BUG WORKING: - Bug when working with the application. Same Format as for "Bug installing".

GOLDENAPPS

During this Week the Testing Revision will be: 40919


Name App Rev VMWA QEMU VBOX BUG INSTALLING BUG WORKING
LinoSP Firefox 2.0.0.20 40919 YES NTD YES -VMWA:None ·VBox:None -VMWA:None ·VBox:None
Vicmarcal Firefox 3.0.10 40770 YES YES NTD -VMWA:None -VMWA:None
LinoSP K-Meleon 1.5.2 40919 YES NTD YES -VMWA:None ·VBox:None -VMWA:None ·VBox:None
Vicmarcal AdobeReader 7.1 40919 YES NTD NTD -VMWA:It shows the PDF if you click on fullscreen mode. -VMWA:None
LinoSP Foxit Reader 2.0 40919 YES NTD YES -VMWA: #4113still present. ·VBox:None #4113 -VMWA: #3503still present. ·VBox:None #3503
Vicmarcal Adobe Flash Player 10 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal Thunderbird 2.0.0.18 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal Sunbird 0.9 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal Abiword 2.6.4 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal FAR Manager 1.7 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal Winrar 3.80 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal 7zip 4.65 40919 YES NTD NTD -VMWA:None -VMWA: #3710still present.
Vicmarcal DosBox 0.72 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal Mirc 6.35 40770 YES YES NTD -VMWA:None -VMWA:None
Vicmarcal Samba-TNG 40919 YES NTD NTD -VMWA:None -VMWA:None
LinoSP IrfanView 4.23 40919 YES NTD YES -VMWA:None ·VBox:None -VMWA:None ·VBox:None
Vicmarcal Notepad Lite 3.3.1 0.3.8 YES NTD NTD -VMWA:None -VMWA:Regression.0.3.9:it doesn't launch. #4461.
Vicmarcal SeaMonkey 1.1.16 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal FileZip 3.06 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal AIDA32 3.94 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal UniversalVW 40919 YES NTD NTD -VMWA:None -VMWA:None
Vicmarcal SciTE 1.77 40919 YES NTD NTD -VMWA:None -VMWA:None
LinoSP VLC Media Player 0.8.0 40919 YES NTD NTD -VMWA:None -VMWA:None
LinoSP VLC Media Player 0.8.6i 40950 NTD NTD YES -RHDW: Does not create shortcut on Desktop -VMWA: Some problems on menu bar, but it can play big videos very smoothly, move window while playing, use timeline to skip parts quickly and with great stability!

CandidateAPPS

Name App Rev VMWA QEMU VBOX RHDW BUG INSTALLING BUG WORKING
Vicmarcal Opera 9.64 40786 NO NTD NTD NTD VMWA:None VMWA:Doesn't respond. #4151
Vicmarcal Chrome 2.0.174 40786 NO NTD NTD NTD VMWA: Doesn't get installed. #4117
Vicmarcal Word Viewer 2003 40786 NO NTD NTD NTD VMWA: MO Word Viewer 2003 fails installing. #4467
Vicmarcal Excel Viewer 2003 40786 NO NTD NTD NTD VMWA:Possibly it doesn't get installed correctly VMWA: It doesn't launch. #4466
Vicmarcal Powerpoint Viewer 2003 NTD NTD NTD NTD
Vicmarcal OpenOffice 3.0.1 NTD NTD NTD NTD
Vicmarcal Total Commander 7.04a NTD NTD NTD NTD
Vicmarcal Net Framework 3.0 40786 NO NTD NTD NTD VMWA: Error:"Insuficient privileges." #4470
Vicmarcal Java 6.13 40786 NO NTD NTD NTD VMWA: Installing Error in Java 6.13. #4468
Ey3 Microsoft Office 2003 40968 NO NTD NTD NO RHDW: Sometimes it stops telling "There was an error" sometimes it crashes while writing registry values

App related bug reports

_TODO_

  • make sure the bug happens only in ReactOS and isn't a bug that also happens in windows. If it happens in both then you should consult with the applications support or Dev team.

What makes an APP Important

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

  • The app 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 apps.
  • The app meets common needs that are needed on most systems.
  • The app is needed for development of the operating system.

Because tracking too many apps at this level of detail is difficult you should not add just another app 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 app test many different parts of the operating system?
  • Does this app do something that will help with testing or development by tracking its usage?
  • Are there no apps that do what this app does, being tracked already?
  • Do you have a good reason for wanting this particular app to be tracked?

If you can honestly answer yes to 2 of the first 3 and the forth then you might consider asking in IRC about adding it.

My app doesn't meet these requirements but I still want it to be tracked

You can track the app yourself but note that it will be your responsibility to test your apps 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 app and not in the operating system. If you're still interested copy the following code to your user page and fill it out. You can put multiple app entry's in one table for more than one app. This template is for your benefit and won't currently help anyone else yet, but, it will let you keep track of your apps and associated bugs. 

{{template:StartAppsTable|

{{template:appEntry
|maintainer=
|appName=
|versionDownload=
|version=
|appSite=
|revision=
|vmwa=
|qemu=
|vbox=
|rhdw=
|bugIns=
|bugRun=

}}
Retrieved from "https://reactos.org/wiki/index.php?title=Testing_Central&oldid=24263"