Re: [cdt-dev] Coordinated testing (max 2 hours)

[Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>]

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Mikhail Khodjaiants
> Sent: Friday, May 30, 2014 10:50 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Coordinated testing (max 2 hours)
> 
> On 30/05/2014 10:05 AM, Marc Khouzam wrote:
> >> -----Original Message-----
> >> From: cdt-dev-bounces@xxxxxxxxxxx
> >> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> >> On Behalf Of Mikhail Khodjaiants
> >> Sent: Friday, May 30, 2014 9:46 AM
> >> To: CDT General developers list.
> >> Subject: Re: [cdt-dev] Coordinated testing (max 2 hours)
> >>
> >> Marc,
> >>
> >> Do you expect the testing to be done for all platforms? If so, it has
> >> to be mentioned in the spreadsheet along with the features that are
> >> not supported for particular platforms.
> > That is a good point.
> > I personally only test on Linux (I don't have a Windows or a Mac).
> > I've always wished someone would do some of the testing on Windows
> > since we have a lot of users on that platform.
> 
> If I have time I'll try to do the testing on Windows.

Thanks!

> > How about I add 3 columns for each test, one for windows, one for Linux
> and one for mac.
> > The person testing for a platform would indicate the result of the
> > test in the column for that platform.

I've modified the sheet for the Debug test to have Linux,Windows,Mac
I think that an optimization is to figure out if the test is platform specific
or if testing it once on any platform is enough.  Until then anyway, I don't
think we'll get all tests run on all platform, but let's aim at getting all
of them on at least one platform.

> > Would that be enough from a testspec perspective?
> 
> I think it's enough. Can you also mark the tests that are expected to fail on
> specific platforms?

I haven't followed the evolution for Windows so I'm not sure of the current
status of GDB features for it.  I believe non-stop still does not work, and
reverse debugging does not either.

As we figure out which test are not expected to pass, we can replace
that cell with an N/A.


> >> Mikhail
> >>
> >> On 29/05/2014 10:28 AM, Marc Khouzam wrote:
> >>> Hi,
> >>>
> >>> as discussed in the Multicore Debug call, let's do some coordinated
> >>> testing
> >> for the release.
> >>> I expect that no more than 2 hours from each of a small amount of
> >> volunteers will be sufficient.
> >>> If you can spend the time, let us know on the mailing list to start
> >>> the ball
> >> rolling.
> >>> We've been using google docs for our internal testing effort and
> >>> find it very
> >> good.
> >>> I've created a document that is public to all and does not require
> >>> logging in
> >> to google.
> >>> The document can be accessed by many at the same time, so just open
> >>> it
> >> and update it.
> >>> CDT wiki->Manual testing->8.4 testing or
> >>>
> >>
> https://docs.google.com/spreadsheet/ccc?key=0AgqbIOVmRSR4dGFEY3UtY
> >> m1fM
> >>> zRDdEMtV1NpV3JOMkE&usp=sharing
> >>>
> >>> It contains tests for Debug which are not exhaustive, but are a start.
> >>> There is a section for Codan but no real tests yet.  I'd like to see
> >>> tests added for other CDT parts, for installation and new ones for
> >>> Debug as time goes on.  Please feel free to grow that document for
> >>> this
> >> release, which we will then copy for the next release.
> >>> RC2 is out and should be used for this testing.
> >>> Or you can take RC3 which will be out tomorrow.
> >>>
> >>> If you find issues you should open bugs.  If you are not sure, you
> >>> can email
> >> the list and ask about your findings.
> >>> An on-going effort will be to replace some of those manual tests
> >>> with automated ones.  But until that is done, it is good to at least
> >>> have the
> >> manual ones.
> >>> Thanks in advance.
> >>>
> >>> Marc
> >>>
> >>> _______________________________________________
> >>> cdt-dev mailing list
> >>> cdt-dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >> _______________________________________________
> >> cdt-dev mailing list
> >> cdt-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev