V4L Test Suite - Revision history

CityK: /* Test applications */ minor edits

2011-10-08T16:09:34Z

Test applications: minor edits

← Older revision		Revision as of 16:09, 8 October 2011
Line 15:		Line 15:
	Simple programs that test various functionality of a V4L2 driver.		Simple programs that test various functionality of a V4L2 driver.

-	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.	+	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment or context. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code if it does not comply with such ideal qualifications - as something is better than nothing.

	* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]		* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]

CityK: /* Test applications */ fix spelling mistake; move note to proper location; remove outdated link

2011-10-08T15:51:44Z

Test applications: fix spelling mistake; move note to proper location; remove outdated link

← Older revision		Revision as of 15:51, 8 October 2011
Line 16:		Line 16:

	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.		There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.
-
-	{{Note\|One user encountered problems between the vivi.c driver and the V4L2 capture.c example, suggesting that they do not "play well" together. See the [[Talk:V4L Test Suite\|article's discussion page]] for more details}}

	* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]		* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]

-	* [http://linuxtv.org/hg/dvb-apps/file/887beb83943a/test dvb-apps/test/] -- though not V4L2 focused, ~~their~~ may be some applicable tests worth examining	+	* [http://linuxtv.org/hg/dvb-apps/file/887beb83943a/test dvb-apps/test/] -- though not V4L2 focused, there may be some applicable tests worth examining

	* [http://www.raphnet.net/programmation/v4l_tools/ v4l_tools]		* [http://www.raphnet.net/programmation/v4l_tools/ v4l_tools]
Line 29:		Line 27:
	* [http://code.google.com/p/python-video4linux2/ python-video4linux2] - starting to build a tester using that.		* [http://code.google.com/p/python-video4linux2/ python-video4linux2] - starting to build a tester using that.

-	* [http://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html Video for Linux Two API Specification Appendix C. Video Capture Example] - not exactly a tester, but worth listing. ~~latest: http://linuxtv~~.~~org/hg/~hverkuil/v4l-dvb-media2/file/7ff930a1268f/v4l2-apps/test/capture_example~~.c	+	* [http://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html Video for Linux Two API Specification Appendix C. Video Capture Example] - not exactly a tester, but worth listing.
		+
		+	{{Note\|One user encountered problems between the vivi.c driver and the V4L2 capture.c example, suggesting that they do not "play well" together. See the [[Talk:V4L Test Suite\|article's discussion page]] for more details}}

	* [http://svn.quickcamteam.net/svn/luvcview/trunk/luvcview/ luvcview ]		* [http://svn.quickcamteam.net/svn/luvcview/trunk/luvcview/ luvcview ]

	* [http://v4l-test.sourceforge.net/ v4l-test] - a V4L2 test environment based directly on the V4L2 API Specification		* [http://v4l-test.sourceforge.net/ v4l-test] - a V4L2 test environment based directly on the V4L2 API Specification
-
-
-


	[[Category:Development]] [[Category:Software]]		[[Category:Development]] [[Category:Software]]

CityK: some clarification; slight formating; general cleanups

2011-10-08T15:49:12Z

some clarification; slight formating; general cleanups

← Older revision		Revision as of 15:49, 8 October 2011
Line 1:		Line 1:
-	~~Code~~ to test other code.	+	This article outlines some V4L2 compliant software which can be used as a means to test the functionality of V4L2 device drivers or applications -- essentially, code to test other code. If you create a new test utility, or if you know of a test that is not listed, please add it to the lists below.

-	~~If you need a test, look here~~.	+	==Test Drivers==
		+	* [[VIVI]] -- Virtual Video Driver: A real v4l2 device driver with no physical hardware. This means anyone can use it (it is part of the Linux kernel: modprobe vivi).

-	If you ~~create~~ a ~~new test~~, ~~add~~ it ~~here~~.	+	:If your application has problems with a specific device driver, try using vivi instead. If you still have a problem, it is much more likely to be a problem with the application than with the driver. Knowing where to look is a big help in fixing problems.

-	~~If you know of a test that~~ is not ~~listed, please add~~ it.	+	:However, vivi is not
		+	:* perfect. Not surprising given it doesn't get the amount of real world use that real drivers do.
		+	:* feature complete. It does not implement every interface of the v4l2 spec.

-	~~==Test Driver==~~	+	:But it is something anyone can run, so it makes reproducing some problems possible that would otherwise be impossible without the specific hardware.
-	~~[[VIVI]] - Virtual Video Driver~~	+
-		+
-	~~A real v4l2 device driver with no physical hardware. This means anyone can use it (it is part of the Linux kernel~~: ~~modprobe vivi).~~	+
-		+
-	If your application has problems with a specific device driver, try using vivi instead. If you still have a problem, it is much more likely to be a problem with the application than with the driver. Knowing where to look is a big help in fixing problems.	+
-		+
-	~~However, vivi is not~~	+
-	* perfect. Not surprising given it doesn't get the amount of real world use that real drivers do.	+
-	* feature complete. It does not implement every interface of the v4l2 spec.	+
-		+
-	But it is something anyone can run, so it makes reproducing some problems possible that would otherwise be impossible without the specific hardware.	+

	==Test applications==		==Test applications==
Line 25:		Line 17:
	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.		There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.

-	{{Note\|~~It has been suggested that~~ the vivi.c driver and the V4L2 capture.c example do not "play well" together. See the [[Talk:V4L Test Suite\|article's discussion page]] for more details}}	+	{{Note\|One user encountered problems between the vivi.c driver and the V4L2 capture.c example, suggesting that they do not "play well" together. See the [[Talk:V4L Test Suite\|article's discussion page]] for more details}}

	* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]		* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]

-	* [http://linuxtv.org/hg/dvb-apps/file/887beb83943a/test dvb-apps/test/]	+	* [http://linuxtv.org/hg/dvb-apps/file/887beb83943a/test dvb-apps/test/] -- though not V4L2 focused, their may be some applicable tests worth examining

	* [http://www.raphnet.net/programmation/v4l_tools/ v4l_tools]		* [http://www.raphnet.net/programmation/v4l_tools/ v4l_tools]

CityK: fixed the note

2011-10-05T22:43:54Z

fixed the note

← Older revision		Revision as of 22:43, 5 October 2011
Line 24:		Line 24:

	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.		There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.
		+
		+	{{Note\|It has been suggested that the vivi.c driver and the V4L2 capture.c example do not "play well" together. See the [[Talk:V4L Test Suite\|article's discussion page]] for more details}}

	* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]		* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]
Line 41:		Line 43:
	* [http://v4l-test.sourceforge.net/ v4l-test] - a V4L2 test environment based directly on the V4L2 API Specification		* [http://v4l-test.sourceforge.net/ v4l-test] - a V4L2 test environment based directly on the V4L2 API Specification

-	~~{Note\|It has been suggested that the vivi.c driver and the V4L2 capture.c example do not "play well" together. See the discussion page for more details~~	+



	[[Category:Development]] [[Category:Software]]		[[Category:Development]] [[Category:Software]]

CityK: removed end user report of vivi & capture compatibility problems to the article's talk page; minor formating

2011-10-05T22:40:56Z

removed end user report of vivi & capture compatibility problems to the article's talk page; minor formating

Show changes

CityK: minor link fixes

2011-10-05T04:36:16Z

minor link fixes

← Older revision		Revision as of 04:36, 5 October 2011
Line 26:		Line 26:
	Simple programs that test various functionality of a driver.		Simple programs that test various functionality of a driver.

-	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[~~http~~:~~//en.wikipedia.org/wiki/~~Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.	+	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[Wikipedia:Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.

	* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]		* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]
Line 294:		Line 294:

	====Canonical source of capture and vivi====		====Canonical source of capture and vivi====
-	http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/v4l2spec/capture.c	+	* http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/v4l2spec/capture.c

-	http://linuxtv.org/hg/~~v4l-dvb~~/~~file/50e4cdc46320/linux~~/drivers/media/video/vivi.c	+	*[http://git.linuxtv.org/media_tree.git/blob/HEAD:/drivers/media/video/vivi.c vivi.c]
-	[[Category:Development]]	+
		+	[[Category:Development]] [[Category:Software]]

CityK: fixed some links; removed a bit of the first person narrative

2011-10-05T04:09:15Z

fixed some links; removed a bit of the first person narrative

← Older revision		Revision as of 04:09, 5 October 2011
Line 26:		Line 26:
	Simple programs that test various functionality of a driver.		Simple programs that test various functionality of a driver.

-	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause false ~~problems~~ when someone else uses them in a different environment. For instance, a test should not be run unless the driver advertises ~~suppport~~ for it. ~~This~~ means all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test	+	There are many small test apps that seem to have been written to help isolate an existing problem, as opposed to actively looking for problems. This means the tests make assumptions about what is/isn't supported, which can cause [[http://en.wikipedia.org/wiki/Type_I_and_type_II_errors\|false positives]] when someone else uses them in a different environment. For instance, a specific feature test should not be run unless the device driver advertises support for the feature. Ideally, this means that all tests should first xioctl(fd, VIDIOC_QUERYCAP, &cap) and test cap.capabilities to see if the rest of the test is applicable. However, this does not mean you shouldn't post your test code it it does not comply with such ideal qualifications - as something is better than nothing.
-	cap.capabilities to see if the rest of the test is applicable. ~~(note I said 'should' - This~~ does not mean you shouldn't post your test code it it does not comply - something is better than nothing.)	+

-	http://linuxtv.org/~~cgi~~-~~bin/viewcvs~~.~~cgi~~/~~dvb-apps~~/test/	+	* [http://git.linuxtv.org/v4l-utils.git/tree/HEAD:/contrib/test v4l-utils/contrib/test]

-	http://~~www.video4linux~~.org/~~browser~~/~~v4l2~~-apps/test	+	* [http://linuxtv.org/hg/dvb-apps/file/887beb83943a/test dvb-apps/test/]

-	http://~~git~~.~~linuxtv~~.~~org~~/~~v4l-utils.git~~	+	* [http://www.raphnet.net/programmation/v4l_tools/ v4l_tools]

-	http://~~www~~.~~raphnet~~.net/~~programmation~~/~~v4l_tools~~/	+	* The utilities in the test/ directory of the zvbi tarball, available on [http://zapping.sourceforge.net/cgi-bin/view/ZVBI/Download#Source_Code zvbi's project page];

-	~~The utilities in the test/ directory of the zvbi tarball, available on~~ [http://~~zapping~~.~~sourceforge~~.~~net~~/~~cgi~~-~~bin~~/~~view/ZVBI/Download#Source_Code zvbi's project page~~];	+	* [http://code.google.com/p/python-video4linux2/ python-video4linux2] - starting to build a tester using that.

-	http://~~code~~.~~google.com~~/p/~~python~~-~~video4linux2~~/ - ~~starting to build~~ a tester ~~using that~~.	+	* [http://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html Video for Linux Two API Specification Appendix C. Video Capture Example] - not exactly a tester, but worth listing. latest: http://linuxtv.org/hg/~hverkuil/v4l-dvb-media2/file/7ff930a1268f/v4l2-apps/test/capture_example.c

-	http://~~v4l2spec~~.~~bytesex~~.~~org~~/~~spec~~/~~a16706.htm Appendix B. Video Capture Example - not exactly a tester, but worth listing. latest: http:~~//~~linuxtv.org~~/~~hg/~hverkuil/v4l-dvb-media2/file/7ff930a1268f/v4l2-apps/test/capture_example.c~~	+	* [http://svn.quickcamteam.net/svn/luvcview/trunk/luvcview/ luvcview ]

-	~~http://svn.quickcamteam.net/svn/luvcview/trunk/luvcview/~~	+	* [http://v4l-test.sourceforge.net/ v4l-test] - a V4L2 test environment based directly on the V4L2 API Specification
-		+
-	http://v4l-test.sourceforge.net/ - a V4L2 test environment based directly on the V4L2 API Specification	+

	==Bugs in Examples==		==Bugs in Examples==

CityK: /* Test applications */ add some links

2011-09-30T01:12:46Z

Test applications: add some links

← Older revision		Revision as of 01:12, 30 September 2011
Line 32:		Line 32:

	http://www.video4linux.org/browser/v4l2-apps/test		http://www.video4linux.org/browser/v4l2-apps/test
		+
		+	http://git.linuxtv.org/v4l-utils.git
		+
		+	http://www.raphnet.net/programmation/v4l_tools/

	The utilities in the test/ directory of the zvbi tarball, available on [http://zapping.sourceforge.net/cgi-bin/view/ZVBI/Download#Source_Code zvbi's project page];		The utilities in the test/ directory of the zvbi tarball, available on [http://zapping.sourceforge.net/cgi-bin/view/ZVBI/Download#Source_Code zvbi's project page];

Jimbley: Added category: Development

2009-05-03T01:47:57Z

Added category: Development

← Older revision		Revision as of 01:47, 3 May 2009
Line 296:		Line 296:

	http://linuxtv.org/hg/v4l-dvb/file/50e4cdc46320/linux/drivers/media/video/vivi.c		http://linuxtv.org/hg/v4l-dvb/file/50e4cdc46320/linux/drivers/media/video/vivi.c
		+	[[Category:Development]]

Nmarci: v4l-test.sourceforge.net added

2009-04-23T03:52:50Z

v4l-test.sourceforge.net added

← Older revision		Revision as of 03:52, 23 April 2009
Line 41:		Line 41:
	http://svn.quickcamteam.net/svn/luvcview/trunk/luvcview/		http://svn.quickcamteam.net/svn/luvcview/trunk/luvcview/

		+	http://v4l-test.sourceforge.net/ - a V4L2 test environment based directly on the V4L2 API Specification

	==Bugs in Examples==		==Bugs in Examples==