Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Coordinated testing (max 2 hours)

Thanks William!

Hardware debugging is one of the aspects that was not covered very well.
So yes, please add your tests for the hardware debugging to the document.
________________________________________
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of William Riley [william.riley@xxxxxxxxxxx]
Sent: June 2, 2014 8:55 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Coordinated testing (max 2 hours)

Hi Marc

I've been performing some testing of GDB Hardware debugging, using the standard launch type not a customised version. Shall I add these to the spreadsheet/wiki? Just a slightly expanded version of what is already there for Local.

William

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
Sent: 29 May 2014 15:29
To: 'CDT DEV (cdt-dev@xxxxxxxxxxx)'
Subject: [cdt-dev] Coordinated testing (max 2 hours)

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=0AgqbIOVmRSR4dGFEY3UtYm1fMzRDdEMtV1NpV3JOMkE&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


This message is intended only for the use of the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient, you are hereby notified that any dissemination of this email (including any attachments thereto) is strictly prohibited. If you have received this email in error, please notify the sender immediately by telephone or email and permanently destroy the original without making any copy. Please note that any material and advice from this mail is provided free of charge and shall be used as an example for demonstration purposes only.
RENESAS MAKES NO WARRANTIES THAT THE USAGE OF INFORMATION OR ADVICE FROM THIS E-MAIL WILL NOT INFRINGE ANY INTELLECTUAL PROPERTY RIGHTS (E.G. PATENTS, COPYRIGHTS). RENESAS CANNOT GUARANTEE BUG FREE OPERATION AND THE RECIPIENT WILL USE AND/OR DISTRIBUTE IT ONLY AT HIS OWN RISK. IN NO EVENT SHALL RENESAS BE LIABLE FOR ANY DAMAGE. The communication with Renesas Electronics Europe Ltd does not amend any written agreement in place.

Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top