[Fiware-friendly-testing] First results from Bitergia team: A methodology proposal

Paulo Simoes psimoes at onesource.pt
Tue Oct 14 09:50:59 CEST 2014


Thanks.

-- PS

On 14/10/14 08:48, MANUEL ESCRICHE VICENTE wrote:
>
> Dear Paulo,
>
> I'm creating a JIRA tracker for friendly testing.
>
> I hope you have it available today.
>
> Kind regards,
>
> Manuel
>
> *From:*fiware-friendly-testing-bounces at lists.fi-ware.org 
> [mailto:fiware-friendly-testing-bounces at lists.fi-ware.org] *On Behalf 
> Of *Paulo Simoes
> *Sent:* lunes, 13 de octubre de 2014 11:10
> *To:* fiware-friendly-testing at lists.fi-ware.org
> *Subject:* Re: [Fiware-friendly-testing] First results from Bitergia 
> team: A methodology proposal
>
>
> Dear Juanjo, all,
>
> At OneSource we'd prefer to have a JIRA for friendly testing, in order 
> to capture everything that's been performed, otherwise focus will be 
> mostly on found (negative) issues, instead of the whole set of tests 
> performed (some of them without any significant findings - which is 
> positive).
>
> If necessary we can create the JIRA at OneSource and share it with 
> everyone or use FI-WARE's own JIRA service. What do you prefer?
>
> As for the 5 phases proposed by Alvaro (local machine, own virtual 
> machine in filabs, already exiting virtual machine with the GE in 
> filabs, using Chef recipes and using blueprints - when available), in 
> general we also agree with them.
>
> Regards,
>
> -- Paulo Simões
>
>
> On 10/10/14 16:59, Juanjo Hierro wrote:
>
>     Dear all,
>
>       I haven't gone through the contents of the wiki but I just want
>     to make a remark.   It's perfectly fine that you keep track of
>     what you have tested, because we should be able to trace what has
>     been tested (positively), but I want to stress that issues should
>     be reported sending an email to fiware-tech-help at lists.fi-ware.org
>     <mailto:fiware-tech-help at lists.fi-ware.org> or
>     fiware-lab-help at lists.fi-ware.org
>     <mailto:fiware-lab-help at lists.fi-ware.org> which are the channels
>     through which we will are also receiving issues from other users.
>       Those messages automatically create a ticket on a JIRA system so
>     that we can assign tickets to the teams who can solve them and
>     follow-up progress.
>
>       Eventually, one idea that I put on the table is that we may
>     create a JIRA system for the Friendly Testing Task Force.   Then
>     you may create a ticket whenever you start some concrete test (the
>     more fine-grained, the best) or you may create a battery of
>     tickets for a plan of tests.    Then you close a ticket whenever
>     the test has been passed correctly.   Otherwise, you send an issue
>     to some mailing list (who means a ticket is created in the
>     HelpDesk JIRA system).   You may even link the ticket you had
>     initially created for running a test with the ticket you create
>     because sending the issue.   Once the issue is solved, you may
>     redo the test that was blocked pending of solving the issue and,
>     eventually, close it.
>
>       What do you think?   It may require creating a JIRA for Friendly
>     Testing, but I guess this may be ready on Monday/Tuesday ...
>
>       Best regards,
>
>     -- Juanjo
>
>     -------------
>
>     Telefonica - Product Development and Innovation (PDI)
>
>     website:www.tid.es  <http://www.tid.es>
>
>     email:juanjose.hierro at telefonica.com  <mailto:juanjose.hierro at telefonica.com>
>
>     twitter: twitter.com/JuanjoHierro
>
>       
>
>     FI-WARE (European Future Internet Core Platform) Coordinator
>
>     and Chief Architect
>
>       
>
>     You can follow FI-WARE at:
>
>        website:http://www.fi-ware.org
>
>        facebook:http://www.facebook.com/pages/FI-WARE/251366491587242
>
>        twitter:http://twitter.com/FIware
>
>        linkedIn:http://www.linkedin.com/groups/FIWARE-4239932
>
>     On 10/10/14 11:44, Alvaro del Castillo wrote:
>
>         Hi all!
>
>           
>
>         First report from Bitergia team. The goal of this email is not to talk
>
>         about results, but about the methodology followed.
>
>           
>
>         During this week we have been working in the GEs assigned to our team,
>
>         and also in the FIWARE Labs (filabs).
>
>           
>
>         We have defined a methodology that maybe could be useful for others.
>
>           
>
>         According to Juanjo email about how we should test the GEs there are
>
>         five scenarios: local machine, own virtual machine in filabs, already
>
>         exiting virtual machine with the GE in filabs, using Chef recipes and
>
>         using blueprints.
>
>           
>
>         We have created a Wiki with a first table showing the state of each
>
>         scenario for the GEs. For accesing:
>
>           
>
>         user: fiware
>
>         password: fiware
>
>           
>
>         https://www.bitergia.net/redmine/projects/ficore-testing/wiki/TestingGEris
>
>           
>
>         For each GE we have created a Wiki page (linked from the summary table)
>
>         with the description of the tests in each scenario. This description is
>
>         standard for all the GEs.
>
>           
>
>         For example, for Orion Context Broker:
>
>           
>
>         https://www.bitergia.net/redmine/projects/ficore-testing/wiki/GE_Orion_Context
>
>           
>
>         The index we have defined for the templates are:
>
>           
>
>         GE Orion Context #4260
>
>         * Install process
>
>           * From sources
>
>             * Debian: Ubuntu 14.04, 64 bits
>
>           * From packages
>
>             * RPM: CentOS 6.5
>
>             * Debian
>
>         * Test of available pre created images
>
>         * Test of Chef Recipes
>
>         * Test of Blue prints
>
>           
>
>         With this template (which is extensible), based on the experience for
>
>         testing the 5 scenarios in the 4 GEs, we plan to deliver our work.
>
>           
>
>         So, any thoughts about that? Juanjo and the rest of Telefonica team, is
>
>         it ok for you to deliver in this format our work?
>
>           
>
>         Probably we should move this Wiki to someplace in FICORE Mediawiki.
>
>           
>
>         Also, in the Wiki are the "clean" results. There are tickets linked with
>
>         all the background work needed to reach the results. We are opening in
>
>         stackoverflow and github some tickets. And we plan to start using the
>
>         fiware mailing list to ask some specific issues we have for the GEs.
>
>           
>
>         Cheers
>
>     ------------------------------------------------------------------------
>
>
>     Este mensaje y sus adjuntos se dirigen exclusivamente a su
>     destinatario, puede contener información privilegiada o
>     confidencial y es para uso exclusivo de la persona o entidad de
>     destino. Si no es usted. el destinatario indicado, queda
>     notificado de que la lectura, utilización, divulgación y/o copia
>     sin autorización puede estar prohibida en virtud de la legislación
>     vigente. Si ha recibido este mensaje por error, le rogamos que nos
>     lo comunique inmediatamente por esta misma vía y proceda a su
>     destrucción.
>
>     The information contained in this transmission is privileged and
>     confidential information intended only for the use of the
>     individual or entity named above. If the reader of this message is
>     not the intended recipient, you are hereby notified that any
>     dissemination, distribution or copying of this communication is
>     strictly prohibited. If you have received this transmission in
>     error, do not read it. Please immediately reply to the sender that
>     you have received this communication in error and then delete it.
>
>     Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>     destinatário, pode conter informação privilegiada ou confidencial
>     e é para uso exclusivo da pessoa ou entidade de destino. Se não é
>     vossa senhoria o destinatário indicado, fica notificado de que a
>     leitura, utilização, divulgação e/ou cópia sem autorização pode
>     estar proibida em virtude da legislação vigente. Se recebeu esta
>     mensagem por erro, rogamos-lhe que nos o comunique imediatamente
>     por esta mesma via e proceda a sua destruição
>
>
>
>     _______________________________________________
>
>     Fiware-friendly-testing mailing list
>
>     Fiware-friendly-testing at lists.fi-ware.org  <mailto:Fiware-friendly-testing at lists.fi-ware.org>
>
>     https://lists.fi-ware.org/listinfo/fiware-friendly-testing
>
>
> ------------------------------------------------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su 
> destinatario, puede contener información privilegiada o confidencial y 
> es para uso exclusivo de la persona o entidad de destino. Si no es 
> usted. el destinatario indicado, queda notificado de que la lectura, 
> utilización, divulgación y/o copia sin autorización puede estar 
> prohibida en virtud de la legislación vigente. Si ha recibido este 
> mensaje por error, le rogamos que nos lo comunique inmediatamente por 
> esta misma vía y proceda a su destrucción.
>
> The information contained in this transmission is privileged and 
> confidential information intended only for the use of the individual 
> or entity named above. If the reader of this message is not the 
> intended recipient, you are hereby notified that any dissemination, 
> distribution or copying of this communication is strictly prohibited. 
> If you have received this transmission in error, do not read it. 
> Please immediately reply to the sender that you have received this 
> communication in error and then delete it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu 
> destinatário, pode conter informação privilegiada ou confidencial e é 
> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa 
> senhoria o destinatário indicado, fica notificado de que a leitura, 
> utilização, divulgação e/ou cópia sem autorização pode estar proibida 
> em virtude da legislação vigente. Se recebeu esta mensagem por erro, 
> rogamos-lhe que nos o comunique imediatamente por esta mesma via e 
> proceda a sua destruição

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-friendly-testing/attachments/20141014/97d1b8df/attachment.html>


More information about the Fiware-friendly-testing mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy