Snapshot Testing - Revision history

Langstonius: /* Scope */

2011-03-30T07:42:14Z

Scope

←Older revision		Revision as of 07:42, 30 March 2011
Line 11:		Line 11:
	**Audio		**Audio
	**Video		**Video
			***MythTV
			***VDR
	**Automation - Includes lighting, climate and other automated systems		**Automation - Includes lighting, climate and other automated systems
	**Networking (NAS, File Server discovery, dhcp server, router functions)		**Networking (NAS, File Server discovery, dhcp server, router functions)

Langstonius: /* Scope */

2011-03-29T21:25:56Z

Scope

←Older revision		Revision as of 21:25, 29 March 2011
Line 11:		Line 11:
	**Audio		**Audio
	**Video		**Video
	**Climate		**Automation - Includes lighting, climate and other automated systems
	**Automation - Includes lighting and other automated systems		**Networking (NAS, File Server discovery, dhcp server, router functions)
	**~~Presence~~
	**Security		**Security
			**Telecom

	=Process=		=Process=

Langstonius: /* Process */

2011-03-24T08:29:43Z

Process

←Older revision		Revision as of 08:29, 24 March 2011
Line 30:		Line 30:
	**Sound Card		**Sound Card
	**Ram		**Ram
	**Size of OS drive LinuxMCE is installed onto		**Size of OS drive LinuxMCE is installed onto.

			==Feedback Tools==
			The SVN [http://svn.linuxmce.org LinuxMCE SVN] is where you can submit tickets about problems encountered. If you need to reference anything, there are tools to help you get and pass on this information.

	~~Granted, you may not have all of this information, but the more you can provide, the better.~~
	To easily pastebin your logs		To easily pastebin your logs
	*install pastebinit 'sudo apt-get install pastebinit'		*install pastebinit 'sudo apt-get install pastebinit'
Line 38:		Line 40:
	*this can be used for other troubleshooting output such as lspci, aplay, etc		*this can be used for other troubleshooting output such as lspci, aplay, etc

			And lastly, if you know how to fix it, submit a patch. It can only help.

Langstonius: /* Process */

2011-03-24T08:26:04Z

Process

←Older revision		Revision as of 08:26, 24 March 2011
Line 33:		Line 33:

	Granted, you may not have all of this information, but the more you can provide, the better.		Granted, you may not have all of this information, but the more you can provide, the better.
			To easily pastebin your logs
			*install pastebinit 'sudo apt-get install pastebinit'
			*when trying to send a log simply 'pastebinit /path/to/file'
			*this can be used for other troubleshooting output such as lspci, aplay, etc



	==Development / VM Testing==		==Development / VM Testing==

Langstonius: /* Process */

2011-03-24T08:24:07Z

Process

@@ Line 17: / Line 17: @@
 =Process=
-The process of testing builds will be split into two parts, both of which require volunteers. Both are key to help the project continue growing and moving forward. We encourage everyone to 'get in where they fit in' meaning there is no-one who needs to appoint you. The purpose of this page is to inform so that individuals can test and report back their results. So jump in, the water is fine.
+The process of testing builds will be split into two parts, both of which require volunteers. Both are key to help the project continue growing and moving forward. We encourage everyone to 'get in where they fit in' meaning there is no-one who needs to appoint you. The purpose of this page is to inform so that individuals can test and report back their results. So jump in, the water is fine. However, we do ask that you please report issues to the svn by opening a ticket to at least make someone aware of the problem. Critical information includes:
 ==Development / VM Testing==

Langstonius at 07:40, 24 March 2011

2011-03-24T07:40:48Z

←Older revision		Revision as of 07:40, 24 March 2011
Line 1:		Line 1:
	[[category:Testing]]		[[category:Testing]]
	~~[[stub]]~~
	=Overview=		=Overview=
	The goal of this and its associated pages is provided to outline an informal testing program for LinuxMCE snapshots and major revisions. The work here is voluntary and all help, no matter how small is appreciated. That being said, with the complexity of LinuxMCE some form of structure must exist to get coherent feedback to improve our one of a kind open source project.		The goal of this and its associated pages is provided to outline an informal testing program for LinuxMCE snapshots and major revisions. The work here is voluntary and all help, no matter how small is appreciated. That being said, with the complexity of LinuxMCE some form of structure must exist to get coherent feedback to improve our one of a kind open source project.

			Looking for [[Snapshot_overview\|snapshot list]]?
	=Scope=		=Scope=
	Our goal is to provide feedback for:		Our goal is to provide feedback for:

Langstonius at 07:36, 24 March 2011

2011-03-24T07:36:34Z

←Older revision		Revision as of 07:36, 24 March 2011
Line 1:		Line 1:
			[[category:Testing]]
			[[stub]]
	=Overview=		=Overview=
	The goal of this and its associated pages is provided to outline an informal testing program for LinuxMCE snapshots and major revisions. The work here is voluntary and all help, no matter how small is appreciated. That being said, with the complexity of LinuxMCE some form of structure must exist to get coherent feedback to improve our one of a kind open source project.		The goal of this and its associated pages is provided to outline an informal testing program for LinuxMCE snapshots and major revisions. The work here is voluntary and all help, no matter how small is appreciated. That being said, with the complexity of LinuxMCE some form of structure must exist to get coherent feedback to improve our one of a kind open source project.

Langstonius: /* Testing Spec */

2011-03-24T07:35:08Z

Testing Spec

←Older revision		Revision as of 07:35, 24 March 2011
Line 34:		Line 34:

	=Testing Spec=		=Testing Spec=
	*Development testing form. Please fill this out		*Development testing form. Please fill this out in a very SPECIFIC manner. You are testing arent you :)

			*End- User / Physical testing form. Please fill this out in a very SPECIFIC manner. Your Penguin will thank you.

			*All - Start to finish, top to bottom. Many thanks for filling this out.

Langstonius at 07:31, 24 March 2011

2011-03-24T07:31:46Z

←Older revision		Revision as of 07:31, 24 March 2011
Line 2:		Line 2:
	The goal of this and its associated pages is provided to outline an informal testing program for LinuxMCE snapshots and major revisions. The work here is voluntary and all help, no matter how small is appreciated. That being said, with the complexity of LinuxMCE some form of structure must exist to get coherent feedback to improve our one of a kind open source project.		The goal of this and its associated pages is provided to outline an informal testing program for LinuxMCE snapshots and major revisions. The work here is voluntary and all help, no matter how small is appreciated. That being said, with the complexity of LinuxMCE some form of structure must exist to get coherent feedback to improve our one of a kind open source project.

	==Scope==		=Scope=
	Our goal is to provide feedback for:		Our goal is to provide feedback for:
	*VM installation testing for development work.		*VM installation testing for development work.
Line 13:		Line 13:
	**Security		**Security

	==Process==		=Process=
	The process of testing builds will be split into two parts, both of which require volunteers. Both are key to help the project continue growing and moving forward. We encourage everyone to 'get in where they fit in' meaning there is no-one who needs to appoint you. The purpose of this page is to inform so that individuals can test and report back their results. So jump in, the water is fine.		The process of testing builds will be split into two parts, both of which require volunteers. Both are key to help the project continue growing and moving forward. We encourage everyone to 'get in where they fit in' meaning there is no-one who needs to appoint you. The purpose of this page is to inform so that individuals can test and report back their results. So jump in, the water is fine.

	===Development / VM Testing===		==Development / VM Testing==
	Providing feedback on snapshots for Virtual Machine (VM) installation provides quick feedback on a number of things		Providing feedback on snapshots for Virtual Machine (VM) installation provides quick feedback on a number of things
	*Installation process and any errors		*Installation process and any errors
Line 25:		Line 25:
	As you can see, this is an important part of the process as it allows new user / developers to quickly experience the system (albeit on a _VERY_ limited scale) as well as develop for it without setting up additional physical systems. Please see the installation reports section to get a standardized (ish) form to assist you in providing structured feedback on the installation process.		As you can see, this is an important part of the process as it allows new user / developers to quickly experience the system (albeit on a _VERY_ limited scale) as well as develop for it without setting up additional physical systems. Please see the installation reports section to get a standardized (ish) form to assist you in providing structured feedback on the installation process.

	===End-User / Physical Testing===		==End-User / Physical Testing==
	Providing feedback on the usage of a system no matter the scale is important to develop a home automation platform that is more akin to a traditional appliance than a computer system. That being said, there are many different parts and technologies in used, from powerline communication to HDMI audio / visual setups. For this reason, feedback from the end-user / physical hardware aspect is critical so that we work towards that truly smart appliance. Important feedback includes:		Providing feedback on the usage of a system no matter the scale is important to develop a home automation platform that is more akin to a traditional appliance than a computer system. That being said, there are many different parts and technologies in used, from powerline communication to HDMI audio / visual setups. For this reason, feedback from the end-user / physical hardware aspect is critical so that we work towards that truly smart appliance. Important feedback includes:
	*Audio / Visual setup (i.e. types of devices)		*Audio / Visual setup (i.e. types of devices)
Line 32:		Line 32:
	**LinuxMCE admin		**LinuxMCE admin
	**Mythweb		**Mythweb

			=Testing Spec=
			*Development testing form. Please fill this out

Langstonius: /* Snapshot Testing */

2011-03-24T07:29:19Z

Snapshot Testing

@@ Line 1: / Line 1: @@
-=Snapshot Testing=
+=Overview=
-The purpose of this and its associated pages is provided to outline an informal testing program for LinuxMCE snapshots and major revisions. The work here is voluntary and all help, no matter how small is appreciated. That being said, with the complexity of LinuxMCE some form of structure must exist to get coherent feedback to improve our one of a kind open source project.
+The goal of this and its associated pages is provided to outline an informal testing program for LinuxMCE snapshots and major revisions. The work here is voluntary and all help, no matter how small is appreciated. That being said, with the complexity of LinuxMCE some form of structure must exist to get coherent feedback to improve our one of a kind open source project.
 ==Scope==
@@ Line 12: / Line 12: @@
 **Presence
 **Security