Difference between revisions of "Quality"

From VideoLAN Wiki
Jump to navigation Jump to search
m (Reverted edits by Gggg (Talk); changed back to last version by Remiii)
 
(23 intermediate revisions by 17 users not shown)
Line 1: Line 1:
=Quality Assurance=
+
'''Quality Assurance'''
  
This section of this wiki is about helping to increase the quality of different versions of VideoLAN's products, and mainly [[VLC media player]].
+
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 yet on this page, 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.''
+
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 report bugs and regressions. Some projects rely on a lot of external code that evolves a lot. Being '''numerous''' can help to make it better.
+
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===
The '''bugs''' should be tracked down and killed using [http://trac.videolan.org trac]
+
The '''bugs''' should be tracked down and killed using [http://trac.videolan.org '''trac'''].
  
 
==Why should you get involved ?==
 
==Why should you get involved ?==
The '''more''' we are, the more bugs are spotted, the best VLC is !
+
The '''more''' we are, the more bugs are spotted, the better VLC is !
 
Easy, ain't it ?
 
Easy, ain't it ?
  
Line 24: Line 24:
  
 
===Bug reporting===
 
===Bug reporting===
Use trac to do these.
+
:''Main article: [[Report bugs]]''
 +
Use trac to do these. If you compile {{VLC}} yourself, please enable [[debug]] to get readable bactraces if any.
  
 
==Urgent==
 
==Urgent==
* Prepare the tests for VLC 0.8.6
 
 
* Gather original and references video and audio files
 
* Gather original and references video and audio files
  
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.
 +
* VLC functionality tests
 +
* VLC transcode and streaming tests
 +
* VLC fundamental tests in src/test (run ''make check'')
  
* VLC functionnality tests
+
There is a small test suite for the [[Android]] port located at ''[[Android test suite]]''.
 
 
* VLC transcode and streaming tests
 
  
 
==Files==
 
==Files==
Line 46: Line 46:
 
All those files should be tested inside the reference FTP.
 
All those files should be tested inside the reference FTP.
  
ftp://streams.videolan.org/streams-videolan/reference/
+
ftp://streams.videolan.org/streams/
  
 
Use that structure to create the reports.
 
Use that structure to create the reports.
Line 55: Line 55:
 
* References codecs pages usually, linking to those should be enough...
 
* References codecs pages usually, linking to those should be enough...
  
==Versions roadmaps==
+
==Nightly builds==
 
 
=== 0.9.0 ===
 
0.9.0 should be the first version to review now.
 
  
==== NB ====
+
In general, use the latest nightly build when you run your tests and report,
Use the latest NB, 20070425 or newer to run your tests And report.
+
available at http://nightlies.videolan.org/.
[http://nightlies.videolan.org/ Here] you can download experimental versions of VLC.
 
  
=MiniSAPServers=
 
  
=VLS=
+
[[Category:Coding]]

Latest revision as of 07:12, 16 April 2016

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

Main article: Report bugs

Use trac to do these. If you compile VLC media player yourself, please enable debug to get readable bactraces if any.

Urgent

  • 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
  • VLC fundamental tests in src/test (run make check)

There is a small test suite for the Android port located at Android test suite.

Files

Official files

All those files should be tested inside the reference FTP.

ftp://streams.videolan.org/streams/

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...

Nightly builds

In general, use the latest nightly build when you run your tests and report, available at http://nightlies.videolan.org/.