Snapshot testing

[golgoj4]

http://wiki.linuxmce.org/index.php/Snapshot_overview This page is doing it wrong.

Testing need to be more indepth that 'it installs'

At a minimum before you list a snapshot as functional, shouldn't

(1) Video
(2) Audio
(3) Network
(4) Storage Devices
(5) Telecom
(6) Automation
(7)Myth / VDR

Be tested before they are listed on a wiki? I appreciate people taking the time, but more complete information needs to accompany these 'tests' otherwise they dont really do much.

-my 2 cents
golgoj4

[bongowongo]

You are right golgoj4.
But we need more resources/manpower to do it.
To elaborate what I do with every snapshot is...........
Go through installation till I see Orbiter UI1.
In the process (2) audio is tested / also to some extend (1), because I see sara.
To dive into the others requires a lot more time, and a proper test setup, and poses problems. What is the standard device for (6)? Zwave/PLCbus/KNX/X10 etc etc.
Usually I take a look at the forum and see if there are common big problems, e.g. not starting AV-wizard or not able to create MD. I test that then. Maybe I should put in the wiki what I exactly tested.

[golgoj4]

Bongo and I talked in IRC and a wiki page outlining our testing process so anyone can join.

Basically its going to be split up by what people have.

So initially bongo is going to install from snapshot at which point i test it on physical hard ware. The more diverse hardware the better so stay tuned for our semi-official testing process.

[bongowongo]

And our team name =
Bongo's Fluffers
team motto =
Test your Bongo regularly
team mascotte =
Elephant

[totallymaxed]

Bongo and I talked in IRC and a wiki page outlining our testing process so anyone can join.

Basically its going to be split up by what people have.

So initially bongo is going to install from snapshot at which point i test it on physical hard ware. The more diverse hardware the better so stay tuned for our semi-official testing process.

I dont know what the new Wiki pages says yet but I can relate the process we use that might be of help;

1. Does the snapshot work and deliver a basic working system?

2. Yes -  then people who have the hardware to test the specific parts of system after that can then focus on those and report back
  No - then report what the failure at 1 was and wait for a new snapshot.

Some people may take on several of the hardware specific testing tasks (dependent on time/hardware availability) others may just focus on a single hardware specific test or tests. Each tester documents their testing process. This makes testing faster and avoids the problem of a single person having to have all the hardware & importantly all of the time to test it all each time. If multiple people test the same hardware/feature thats ok too as it just strengthens the validity of the testing.

Just my 2c worth based on our processes here and our experience from doing this with the Pluto devs 'back in the day'.

All the best


Andrew

[Marie.O]

totallymaxed,

that's exactly the plan we discussed. Good to see we are not too far off from what Pluto successfully did

[totallymaxed]

totallymaxed,

that's exactly the plan we discussed. Good to see we are not too far off from what Pluto successfully did

Great minds think alike :-)

[bongowongo]

Thanks
So everybody agrees upon the name. Good.

[Marie.O]

Great minds think alike :-)

In German it is: Zwei Dumme, ein Gedanke

Go google translate

[joshpond]

Great minds think alike :-)

........but so do idiots my wife tells me 

[golgoj4]

The result of bongo and i discussing and his 1st testing

http://wiki.linuxmce.org/index.php/Snapshot_Testing
http://wiki.linuxmce.org/index.php/Snapshot_overview

Im the hardware tester and lagging at the moment. the iso is sitting on my drive as of yet to be burned.

Here is a question: Now that its all laid out, what the best way for multiple people to help test instead of the two?

[locutus]

i dont know how you would do it but maybe a script that tests each part?

[Michaelree]

Not sure if this is the right place, but i just installed the lastest snapshot 23858.  Everything went fine untill i tryed setting up a media director, a Zotac Ion 330, and i could not get the sound to work over HDMI.

cat /proc/asound/version on the core shows 1.0.23
cat /proc/asound/version on the MD shows 1.0.17
and both are usings alsamixer 1.0.18

Chris

[golgoj4]

Not sure if this is the right place, but i just installed the lastest snapshot 23858.  Everything went fine untill i tryed setting up a media director, a Zotac Ion 330, and i could not get the sound to work over HDMI.

cat /proc/asound/version on the core shows 1.0.23
cat /proc/asound/version on the MD shows 1.0.17
and both are usings alsamixer 1.0.18

Chris

Not exactly but since your here

ssh into the md. normally thats done by
-ssh'ing into the core
-from the core ssh into the md
-run this command apt-get install alsa-modules-`uname -r`

let me know if this works. should bring alsa to 1.0.23 on the MD. The alsamixer version doesnt need to match the alsa version installed I am told.

golgoj4 with fix information from possy.

[pigdog]

Hi,

If golgoj4 solution doesn't work for you look at this...

http://forum.linuxmce.org/index.php?topic=11415.0