Dear All,
in addition to the mail I sent you on Wednesday, here is a further mail of details concerning the work to be done mainly for Unit Testing Plan (and completing the features description for each GE).
Please take note of such inputs to properly complete the activity requested.
BR
Pier
Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro
Inviato: giovedì 31 maggio 2012 10:04
A: Leidig, Torsten
Cc: fiware at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
Oggetto: Re: [Fiware-wpl] [Fiware] Fwd: Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE
Hi,
The example will be provided by tomorrow EOB, but mostly in order to avoid missunderstandings about where to place things and to give some hints about formatting of sections, etc so that everything looks homogeneous.
However, the rather important things you should be working on since some time, because they may require some time, are:
* the addition of features that, complementing the existing ones, provide a accurate and complete description of the features by the GE
* the development of the unit testing programs to be run in order to test the different features
For the former, it is clear where they are placed (Materializing the FI-WARE Vision) and the format is also clear since months. The second is a matter of having the required unit testing programs ready, each GE will have its own suite of unit testing programs.
So, therefore, don't use the lack of a example as an excuse not to do the above.
Creating the wiki document describing the Unit Testing plan will be pretty straightforward is the above is ready. Nevertheless, you will see a reference example by tomorrow EOB.
Best regards,
-- Juanjo
-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro
FI-WARE (European Future Internet Core Platform) Chief Architect
You can follow FI-WARE at:
website: http://www.fi-ware.eu
facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
twitter: http://twitter.com/FIware
linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
On 31/05/12 09:29, Leidig, Torsten wrote:
Any news about the reference example?
How do we handle GE implementations which are not installed by the user but rather offered as a service under control of the developer or any other administrator/operator?
From: Juanjo Hierro <jhierro at tid.es<mailto:jhierro at tid.es>>
Date: Thu, 31 May 2012 06:15:56 +0200
To: "fiware at lists.fi-ware.eu<mailto:fiware at lists.fi-ware.eu>" <fiware at lists.fi-ware.eu<mailto:fiware at lists.fi-ware.eu>>
Subject: [Fiware] Fwd: Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE
Note that a separate Unit Test may be defined per tested Feature. However, this is not mandatory so a given Unit Test may be used to test several features. What is
Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo
Inviato: mercoledì 30 maggio 2012 21:18
A: fiware-i2nd at lists.fi-ware.eu
Oggetto: [Fiware-i2nd] I: [Fiware-wpl] [Fiware-wpa] Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE
Dear All,
please find below the description of how the Unit Testing Plan deliverable is planned to be produced for each chapter (e.g. D7.5a). Please read in detail the two mails below (starting with the older one); although in I2ND this first release is concerning the Cloud Edge GE only (Henk/Serge, can you tell me what's the status for this GE?), we need to rapidly progress updating the structure of the 'Materializing the FI-WARE vision' for all the GEs, independent of the need to provide a Unit Testing plan for them.
I'll try to create a 'diagram'/picture of the different links and references, I believe a graphical view of the final structuring would help understanding it better.
BR
Pier
Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro
Inviato: lunedì 28 maggio 2012 23:44
A: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
Oggetto: Re: [Fiware-wpl] [Fiware-wpa] Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE
Hi,
I miss the references to the comments from the reviewers in my last email:
[1] - Comments from reviewers:
* The vague description of functionalities (such as "Extended support for network context data
management and resource management") will not allow the Use Case projects to understand
the FI-WARE propositions correctly, might lead to wrong expectations and might create
further difficulties in the collaboration
* Listing feature deliverables as a set of abilities is also unacceptable. The roadmap should
instead indicate the delivery schedule for precise Generic Enablers, which should then be
described in terms of the abilities they will provide.
By making a link to the appropriate chapter within "Materializing the FI-WARE Vision" from each of the chapter sections within the Technical Roadmap deliverable, these comments by the reviewers would be addressed. Actually, nobody would be able to keep these complains because because the list of Features that will be supported by each of our FI-WARE GEs would be detailed.
Cheers,
-- Juanjo
On 28/05/12 23:34, Juanjo Hierro wrote:
Dear all,
As you know, a Unit Testing Plan deliverable has to be produced for each of the GEs to be released as part of the first FI-WARE Release. Note that this Unit Testing Plan has nothing to do with the Integration Testing Plan which has been asked by the Testbed Chapter team.
The approach proposed to tackle this deliverable was initially shared in April 10th, and was approved after the integration of some of the compiled comments during the joint WPLs/WPAs confcall that took place in May 7th.
Here, we will try to elaborate on the details about how to generate this deliverable per GE on the public wiki.
The very first step will be extend the set of Features listed for each GE within the corresponding section of the "Materializing the FI-WARE Vision" part of the public wiki. As per now, each GE was supposed to have already a number of Features, Epics and User-Stories listed on the "Materializing the FI-WARE Vision" part of the wiki. However, listed Features were supposed to only map to new features to be incorporated in the baseline assets for the first FI-WARE Release (i.e., features that required some sort of development on the baseline asset). Now, we will extend these list of Features so that the whole list of Features provide a comprehensive and complete description of the set of features that will be supported by the GE in the first FI-WARE Release.
Note that with this first step, we hope that we will be able to address some of the comments made by reviewers on the "FI-WARE Technical Roadmap" deliverable, arguing that the information provided in that deliverable was too abstract (see [1]). Making this first step, we will be able to add a link to the set of features to be supported by each FI-WARE GE from the "FI-WARE Technical Roadmap" deliverable. This way, the argument about lack of concreteness should fly away.
Once we have completed the set of Features for a given GE and listed them within the corresponding section inside the "Materializing the FI-WARE Vision" part of the wiki, we will create a last section, right after the section listing the User-Stories, that will be titled "Unit Testing Plan" and will contain a link to a wiki page describing the Unit Testing Plan that will be applied to the GE. This wiki page will be titled "<name of GE> - Unit Testing Plan" and will be structured into one section titled "Information Common to all tests" and then several sections, each linked to a Unit Test. Each Unit Test, will contain:
* a subsection titled "Tested Features" which contains a list of links to the wiki pages describing the Features that are tested through the Unit Test
* a subsection titled "Test description" which contains detailed information about:
* what client programs and (potentially) data sets will be used to run the test
* how to run the test:
* this should be detailed enough to allow an administrator/operator of a FI-WARE Instance to test if the GE is working properly
* dependencies on third party libraries or software should be specified
* expected results to be obtained by running the client programs with the referred data set
* (note: it would be highly recommended to define a maven project which would be used to run the test and where all dependencies are specified
Note that a separate Unit Test may be defined per tested Feature. However, this is not mandatory so a given Unit Test may be used to test several features. What is important is that the Test description provides the information that is needed to run the tests, not only by the developer of the GE but also by any party (e.g., an administrator/operator of a FI-WARE Instance containing that GE) who decides to use the Unit Testing Plan to verify that the GE is working properly in a given FI-WARE Instance setup.
A link to the corresponding section in the Unit Testing Plan document at the wiki will be included in a "how-to-test" field of the corresponding backlog entry. We will soon inform you whether this field will be created in the template linked to Features descriptions in the public Wiki or in the ticket at the tracker that corresponds to the Feature.
We couldn't provide a reference example of the formula described above because the wiki was down, but we hope to provide it along this week. Nevertheless, don't hesitate to make any question or complement this proposal. Your input is more than welcome.
Please, share these instructions with members of your respective teams.
Best regards,
-- Juanjo
-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro
FI-WARE (European Future Internet Core Platform) Chief Architect
You can follow FI-WARE at:
website: http://www.fi-ware.eu
facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
twitter: http://twitter.com/FIware
linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
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/old-fiware-i2nd/attachments/20120601/d7cf49c0/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/old-fiware-i2nd/attachments/20120601/d7cf49c0/attachment.jpg>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120601/d7cf49c0/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120601/d7cf49c0/attachment-0001.txt>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy