[Server-devel] [XSCE] [RFC] XSCE 6.0 test matrix

[Tim Moody]

From: xsce-devel at googlegroups.com [mailto:xsce-devel at googlegroups.com] On Behalf Of Anish Mangal
Sent: Sunday, November 15, 2015 11:28 AM
To: xsce-devel <xsce-devel at googlegroups.com>
Cc: server-devel <server-devel at lists.laptop.org>
Subject: Re: [XSCE] [RFC] XSCE 6.0 test matrix

 

 

 

On Sun, Nov 15, 2015 at 9:46 PM, Tim Moody <tim at timmoody.com <mailto:tim at timmoody.com> > wrote:

What does install mode mean? (gateway, appliance, nw controller?)

 

 

Yes

 

I added Number Eth adapters and other HW info

 

 

Great. I was actually thinking whether we should have different rows for all such info, or just a link to /etc/xsce.ini. Maybe it makes sense to have them in separate rows just in case the info in /etc/xsce,ini may be stale?

 

some things like ram and storage are not in the ini, but I debated about repeating things that are.  the question could also be asked about the commit hash, which is in the ini.  I guess it's a tradeoff between being able to see the context at a glance and having to copy things.

 

what do L0 and L1 mean?

 

 

This is a remnant of my semiconductor h/w verification days. Wanted to have a basic distinction between depth of testing. So in this case, L0 would mean basic testing of the most critical stuff. L1 means deeper level testing. The idea being an L0 test run would be over much quicker and L1 take additional time (and maybe expertise) so not everybody might want to do it. 

Thoughts?

 

From: xsce-devel at googlegroups.com <mailto:xsce-devel at googlegroups.com>  [mailto:xsce-devel at googlegroups.com <mailto:xsce-devel at googlegroups.com> ] On Behalf Of Tim Moody
Sent: Friday, November 13, 2015 10:49 AM
To: xsce-devel at googlegroups.com <mailto:xsce-devel at googlegroups.com> ; 'server-devel' <server-devel at lists.laptop.org <mailto:server-devel at lists.laptop.org> >
Subject: RE: [XSCE] [RFC] XSCE 6.0 test matrix

 

good start.  I would break out NUC and VM by OS (centos vs f22)

 

also, probably need short explanations on some of the header fields

 

 <https://github.com/XSCE/xsce-tests> https://github.com/XSCE/xsce-tests, most recently owned by George, should get into the picture

 

 <https://github.com/XSCE/xsce/blob/master/docs/TESTING.rst> https://github.com/XSCE/xsce/blob/master/docs/TESTING.rst is getting stale.

 

From:  <mailto:xsce-devel at googlegroups.com> xsce-devel at googlegroups.com [ <mailto:xsce-devel at googlegroups.com> mailto:xsce-devel at googlegroups.com] On Behalf Of Anish Mangal
Sent: Thursday, November 12, 2015 11:15 PM
To: server-devel < <mailto:server-devel at lists.laptop.org> server-devel at lists.laptop.org>; xsce-devel < <mailto:xsce-devel at googlegroups.com> xsce-devel at googlegroups.com>
Subject: [XSCE] [RFC] XSCE 6.0 test matrix

 

With the XSCE 6.0 release imminent in a few weeks, it would be great if we could get the code tested in the many platforms we support. To this end, I have started working on a test-grid. The spreadsheet is linked here:

https://docs.google.com/spreadsheets/d/1pevXOSIoV9LQF_8QV-5_ds0WPqC1Lko3UYYJh8UnUkM/edit#gid=0

At this point, I'm looking for contributions to improve the structure of the sheet, but more importantly, for respective module maintainers to fill in the necessary testing steps in the 'Template' tab. 

Note: This is NOT a call to fill in test data yet. The sheet is not ready - both in completeness and user-friendliness. Please help with making it so. 

Thank you all!

Anish

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/server-devel/attachments/20151115/9d07b64e/attachment-0001.html>