Difference between revisions of "Quality"
| Line 1: | Line 1: | ||
=Quality Assurance= | =Quality Assurance= | ||
| − | This section of | + | This section of the wiki is about helping to increase the quality of different versions of VideoLAN's products, mainly [[VLC media player]]. |
==Why this page ?== | ==Why this page ?== | ||
===Main idea=== | ===Main idea=== | ||
| − | There is not much | + | There is not much on this page yet, but the idea is to develop ''test protocols'', regroup ''test files'', and at the end improve the whole quality of VLC, to avoid ''regressions'' and check ''roadmaps.'' |
===Who is concerned=== | ===Who is concerned=== | ||
| − | The community of VideoLAN's numerous users and developers can enforce the project by doing systematic tests and | + | The community of VideoLAN's numerous users and developers can enforce the project by doing systematic tests and reporting bugs and regressions. Some projects rely on a lot of external code that evolves a lot. Being '''numerous''' can help to make it better. |
===Bugs=== | ===Bugs=== | ||
| Line 34: | Line 34: | ||
==Tests to run== | ==Tests to run== | ||
| − | You want to help testing VLC ? There are a few tests that you can handle: | + | You want to help by testing VLC ? There are a few tests that you can handle: |
* VLC playback tests (codecs and files related) Win32 and MacOS focused. | * VLC playback tests (codecs and files related) Win32 and MacOS focused. | ||
Revision as of 12:51, 16 May 2009
Contents
Quality Assurance
This section of the wiki is about helping to increase the quality of different versions of VideoLAN's products, mainly VLC media player.
Why this page ?
Main idea
There is not much on this page yet, but the idea is to develop test protocols, regroup test files, and at the end improve the whole quality of VLC, to avoid regressions and check roadmaps.
Who is concerned
The community of VideoLAN's numerous users and developers can enforce the project by doing systematic tests and reporting bugs and regressions. Some projects rely on a lot of external code that evolves a lot. Being numerous can help to make it better.
Bugs
The bugs should be tracked down and killed using trac.
Why should you get involved ?
The more we are, the more bugs are spotted, the better VLC is ! Easy, ain't it ?
So if you help, everyone will be a winner.
How can you get involved ?
Use this talk page or contact; for a start User_talk:J-b (this will change). Then, just run the tests and modify this wiki's pages.
Bug reporting
Use trac to do these.
Urgent
- Prepare the tests for VLC 0.8.6
- Gather original and references video and audio files
VLC
Motto: Let's improve VLC !!!
Tests to run
You want to help by testing VLC ? There are a few tests that you can handle:
- VLC playback tests (codecs and files related) Win32 and MacOS focused.
- VLC functionality tests
- VLC transcode and streaming tests
Files
Official files
All those files should be tested inside the reference FTP.
ftp://streams.videolan.org/streams-videolan/reference/
Use that structure to create the reports.
More files
Where to search for more files:
- MPlayer's MPlayer's FTP
- References codecs pages usually, linking to those should be enough...
Versions roadmaps
0.9.0
0.9.0 should be the first version to review now.
NB
Use the latest NB, 20070425 or newer to run your tests And report. Here you can download experimental versions of VLC.
