[Fiware-wpl] Feedback by I2ND Chapter on Unit Testing Plan and Report deliverable proposal

[Garino Pierangelo]

Dear Juanjo,

In the WPL/WPA confcall last Monday you asked for a feedback about the proposed format of Deliverable 'Unit Testing Plan and Report'.

Here is the original text, where I have inserted the proposals provided by I2ND chapter:

We should use the chapter backlogs for this purpose.  After carefully thinking we propose to adopt the following approach:


·         Create a comprehensive set of Features entries in the backlog describing all the features of the GE.   Some of these Features should already be there, but others would map to features already supported in baseline assets.  --> OK



·         Each Feature to include a description on how the feature will be tested (how-to-test). This would mean filling a standard field of the backlog.  --> In order to avoid duplicating descriptions, I2ND suggests that the 'how-to-test' should not be inserted in the ticket backlog, but rather in a wiki page (see next bullet)





·         Note that since they would be features, they should have an entry on the public wiki referred from a ticket on the backlog. However, we need to discuss whether to make it part of the standard template on the wiki entry or just create a field in the ticket. --> I2ND suggests that the how-to-test description of a complete GE be inserted in a unique (and separate) 'how-to-test the GE' wiki page, where each section describes the test procedures for a specific Feature of that GE. This is in our view an advantage, as an initial section(s) can be used to describe only once for the overall GE (or for large portions of the GE's functionality/Features) the common testing environment, as well as tools adopted. Each public wiki page describing a Feature can be updated, to host the link to the section of the test wiki page which describes the test for that Feature, and if the reader wants to get the global information on the test environment can take a look at the whole page.



·         It would be rather useful that the how-to-test field includes a reference to tools or testing clients that automate the testing of the feature.  --> OK (see also above proposal)



·         In theory, it may be argued that description on how-to-test should also be available for Use Case stories but this would be hard to cover in the first release, overall for features already supported in baseline assets. --> It is strongly suggested to keep as minimum 'unit' for test description the Feature level, more granular descriptions would be useless (e.g. no possibility to test separately in many cases).


BR
Pier


------------------------------------------------------------------
Telecom Italia
Pierangelo Garino
Innovation & Industry Relations - Research & Prototyping
Via G. Reiss Romoli 274, I-10148 TORINO
Tel: +39 011 228 7142

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20120413/bcc67e7b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20120413/bcc67e7b/attachment.jpg>