From juanjose.hierro at telefonica.com Fri Oct 10 01:26:02 2014 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Fri, 10 Oct 2014 01:26:02 +0200 Subject: [Fiware-friendly-testing] Working on friendly testing of FIWARE Message-ID: <5437198A.1050607@telefonica.com> Dear all, We have created the fiware-friendly-testing at lists.fi-ware.org mailing list which include all the people that will be involved in friendly testing activities. We will typically use this list to forward general instructions, guidelines, etc that need to be taken into account during the FIWARE friendly testing Task Force. You can also use this list to provide feedback or ask questions that you believe may be of general interest to all the friendly testers, not just you. If you want to communicate with us without the need to involve the rest of friendly testers, then better you use the fiware-friendly-testing-coordination at lists.fi-ware.org mailing list as commented in one of our previous emails. We may reply you copying fiware-friendly-testing at lists.fi-ware.org if we believe that the reply to your question is of interest to all the friendly testers. Please also send to this coordination mailing list the list of email addresses of people in your team that you wish to include in the fiware-friendly-testing at lists.fi-ware.org mailing list. We strongly advise this be all people in your team to make sure that all communications from our side reach all members of the teams asap. We need to be rather effective in our communications. At this point, we understand you have all the info necessary to start the first phase of the FIWARE Friendly Testing Task Force and soon we should expect your first feedback in the form of concrete messages reporting issues, requests for enhancements, etc in either of the two available lists: fiware-tech-help at lists.fi-ware.org or fiware-lab-help at lists.fi-ware.org We are eager to receive your first messages to both lists ! Best regards, -- Juanjo ________________________________ 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 From acs at bitergia.com Fri Oct 10 11:44:07 2014 From: acs at bitergia.com (Alvaro del Castillo) Date: Fri, 10 Oct 2014 11:44:07 +0200 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Message-ID: <1412934247.23235.14.camel@bitboy> 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 -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From juanjose.hierro at telefonica.com Fri Oct 10 17:59:31 2014 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Fri, 10 Oct 2014 17:59:31 +0200 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <1412934247.23235.14.camel@bitboy> References: <1412934247.23235.14.camel@bitboy> Message-ID: <54380263.3070109@telefonica.com> 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 or 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 email: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From psimoes at onesource.pt Mon Oct 13 11:09:57 2014 From: psimoes at onesource.pt (Paulo Simoes) Date: Mon, 13 Oct 2014 10:09:57 +0100 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <54380263.3070109@telefonica.com> References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> Message-ID: <543B96E5.3060706@onesource.pt> 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 or > 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 > email: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 > https://lists.fi-ware.org/listinfo/fiware-friendly-testing -------------- next part -------------- An HTML attachment was scrubbed... URL: From joagonca at onesource.pt Mon Oct 13 11:43:33 2014 From: joagonca at onesource.pt (=?utf-8?Q?Jo=C3=A3o_Gon=C3=A7alves?=) Date: Mon, 13 Oct 2014 10:43:33 +0100 Subject: [Fiware-friendly-testing] Some usability questions Message-ID: Dear all, Since we?ve got the other two mailing lists to provide feedback and/or issue questions that a regular user might do, we figured we could use this mailing list to provide reports on usability questions that might, at some point, create some distrust on the end user regarding the FI-WARE platform. If by any means you?re not OK with this approach, please let us know. General Certificate error when accessing the labs. When issuing a command, often the interface fails to inform the user that it is performing the task on the background (this could trigger the user to request the same action more than one time). Modal loading screens with no option to cancel or go back (the whole page is blacked out). The user can create an account without accepting the Terms of Service. Could/Instances When creating an instance, the bar counters (the numbers only) are not updated. The placeholder text on ?Add Security Group? cannot be read in its entirety, not informing the user correctly about the limitations of the names allowed. Cloud/Security Downloaded key file comes with the name ?Unknown? and no extension. When creating the rules, there?s a ?Cancel" button whereas a ?Close? reflects more the action in cause. FIWARE Catalogue The images names on the catalogue do not correspond to the names present in the lab interface, leading to confusion. Regards, - - - Jo?o Gon?alves joagonca at onesource.pt 00 351 927 997 531 http://onesource.pt -------------- next part -------------- An HTML attachment was scrubbed... URL: From acs at bitergia.com Mon Oct 13 11:59:17 2014 From: acs at bitergia.com (Alvaro del Castillo) Date: Mon, 13 Oct 2014 11:59:17 +0200 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <543B96E5.3060706@onesource.pt> References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> Message-ID: <1413194357.23235.66.camel@bitboy> Hi Paulo! El lun, 13-10-2014 a las 10:09 +0100, Paulo Simoes escribi?: > > 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). We are using a Wiki and ticketing for capturing all activity (including also successes). I think that just using JIRA misses the generation of reports (structured contents) that we thing will be the final deliverables. Maybe using a combination of JIRA+MediaWiki could be the solution. Both are standards tools used in FIWARE. > > 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? I suppose it is better to use FIWAREs JIRA service. > > 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. We are missing a possible 6th use case. Using the global instance of the GE that it is available in some cases in FIWARE Labs. For example, for Access Control, Identity or Context Broker. Cheers > > 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 or > > 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 > > email: 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 > > https://lists.fi-ware.org/listinfo/fiware-friendly-testing > > _______________________________________________ > Fiware-friendly-testing mailing list > Fiware-friendly-testing at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-friendly-testing -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From fernando.lopezaguilar at telefonica.com Mon Oct 13 16:05:02 2014 From: fernando.lopezaguilar at telefonica.com (FERNANDO LOPEZ AGUILAR) Date: Mon, 13 Oct 2014 14:05:02 +0000 Subject: [Fiware-friendly-testing] Some usability questions In-Reply-To: References: Message-ID: Hi Jo?o Thank you very much for your description. I am try to reproduce your comments. Could you clarify in more details what are you describing here: * "When creating an instance, the bar counters (the numbers only) are not updated." Could you give me an image or more description of where you have this problem? You are talking about the Instance count do not show the green part when you try to create a new instance? Regarding the following comments: * "The user can create an account without accepting the Terms of Service." Could you say me which browser are you using? In Chrome I cannot reproduce it. * "The placeholder text on "Add Security Group" cannot be read in its entirety, not informing the user correctly about the limitations of the names allowed." You mean the option "Add new Security Group in the "Launch Instances" window? De: Jo?o Gon?alves > Responder a: Jo?o Gon?alves > Fecha: Monday 13 October 2014 11:43 Para: "fiware-friendly-testing at lists.fi-ware.org" > Asunto: [Fiware-friendly-testing] Some usability questions Nuevo env?o de: Jo?o Gon?alves > Nuevo env?o para: > Fecha de nuevo env?o: Monday 13 October 2014 11:45 Dear all, Since we've got the other two mailing lists to provide feedback and/or issue questions that a regular user might do, we figured we could use this mailing list to provide reports on usability questions that might, at some point, create some distrust on the end user regarding the FI-WARE platform. If by any means you're not OK with this approach, please let us know. General Certificate error when accessing the labs. When issuing a command, often the interface fails to inform the user that it is performing the task on the background (this could trigger the user to request the same action more than one time). Modal loading screens with no option to cancel or go back (the whole page is blacked out). The user can create an account without accepting the Terms of Service. Could/Instances When creating an instance, the bar counters (the numbers only) are not updated. The placeholder text on "Add Security Group" cannot be read in its entirety, not informing the user correctly about the limitations of the names allowed. Cloud/Security Downloaded key file comes with the name "Unknown" and no extension. When creating the rules, there's a "Cancel" button whereas a "Close" reflects more the action in cause. FIWARE Catalogue The images names on the catalogue do not correspond to the names present in the lab interface, leading to confusion. Regards, - - - Jo?o Gon?alves joagonca at onesource.pt 00 351 927 997 531 [OneSource] http://onesource.pt ________________________________ 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: From manuel.escrichevicente at telefonica.com Tue Oct 14 09:48:33 2014 From: manuel.escrichevicente at telefonica.com (MANUEL ESCRICHE VICENTE) Date: Tue, 14 Oct 2014 07:48:33 +0000 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <543B96E5.3060706@onesource.pt> References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> Message-ID: <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> 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 or 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 email: 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 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: From psimoes at onesource.pt Tue Oct 14 09:50:59 2014 From: psimoes at onesource.pt (Paulo Simoes) Date: Tue, 14 Oct 2014 08:50:59 +0100 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> Message-ID: <543CD5E3.3080909@onesource.pt> 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 > or > 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 > > email: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 > > 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: From fernando.lopezaguilar at telefonica.com Tue Oct 14 12:13:41 2014 From: fernando.lopezaguilar at telefonica.com (FERNANDO LOPEZ AGUILAR) Date: Tue, 14 Oct 2014 10:13:41 +0000 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <543CD5E3.3080909@onesource.pt> References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> Message-ID: Dear Paulo, In that case, we should send an email to the fiware-lab-help at lists.fi-ware.org with the Subject [Fiware-friendly-testing] in order to identify it. @Manuel, is it possible it? @Manuel, take into consideration that those issues should be assigned to GE owners in order to resolve them. @Manuel, is it possible it? What do you think? De: Paulo Simoes > Organizaci?n: OneSource Lda. Fecha: Tuesday 14 October 2014 09:50 Para: MANUEL ESCRICHE VICENTE >, "fiware-friendly-testing at lists.fi-ware.org" > Asunto: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal 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 or 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 email: 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 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 ________________________________ 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: From manuel.escrichevicente at telefonica.com Tue Oct 14 13:03:44 2014 From: manuel.escrichevicente at telefonica.com (MANUEL ESCRICHE VICENTE) Date: Tue, 14 Oct 2014 11:03:44 +0000 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> Message-ID: <7503764f911046fe8d2fbabadf7e9235@DB4PR06MB489.eurprd06.prod.outlook.com> Well, let me check I understand it well. 1- The JIRA tracker for friendly testing is not for issues but for workitems to track what work done by testers. 2- Issues found are channelled to the tech-help and lab-help lists, which have their own trackers to make the FIWARE team react to fix the questions and bugs. Then, I'm afraid the request for additional automatic filtering and assignation based on subject and component cannot be done at this moment. Let me explain that the basic scheme used in the help desk is PULL. It means project partners are observing the lists and answer the incoming issues by picking them up. The PUSH scheme is implemented by me by assigning those issues not addressed by anyone. I hope it's clear. Otherwise, please, let me know. Kind regards, Manuel From: FERNANDO LOPEZ AGUILAR Sent: martes, 14 de octubre de 2014 12:14 To: Paulo Simoes; MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Importance: High Dear Paulo, In that case, we should send an email to the fiware-lab-help at lists.fi-ware.org with the Subject [Fiware-friendly-testing] in order to identify it. @Manuel, is it possible it? @Manuel, take into consideration that those issues should be assigned to GE owners in order to resolve them. @Manuel, is it possible it? What do you think? De: Paulo Simoes > Organizaci?n: OneSource Lda. Fecha: Tuesday 14 October 2014 09:50 Para: MANUEL ESCRICHE VICENTE >, "fiware-friendly-testing at lists.fi-ware.org" > Asunto: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal 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 or 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 email: 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 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 ________________________________ 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: From acs at bitergia.com Tue Oct 14 17:22:46 2014 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 14 Oct 2014 17:22:46 +0200 Subject: [Fiware-friendly-testing] Report from Bitergia team Message-ID: <1413300166.23235.118.camel@bitboy> Hi all, After some weeks working with FIWARE Labs Cloud here are some issues we have detected in Bitergia team. In general the experience is good and we have not found blocker issues. In the cloud tab we have found: * General: - Sometimes there are performance problems that affects all services: virtual machines ssh connections are less responsive, the web interface in the cloud is less responsive (or not responsive at all) and sometimes it is incomplete (missing checkboxes in items for example). - We have some issues with sessions but not reproducible (sometimes we need to clean the URL and reload the page). * Instances and Images - Include user in ssh access info in the connection tag: ssh root at .... - Connect to VM display: we detected problems with the VNC iframe but last days they are fixed opening a new web window. But now sometimes the keyboard does not work as expected, and the VNC window does not echo the char typed or show strange chars (d is interpreted as ^[d). - In the list of instances some instances do not have information about "Size". - Instance logs: do not appear. - Instance monitoring: : does not appear. - When working in an instance tabs, you don't know in which instance are you working. - Depending on the image, the allocated space is not completely formatted initially. You need to create a new partition with the free disk space, format it and mount it. Maybe a note could be enough. * Security - Is it possible to add a keypair to an already created instance? If not, advice the user about this fact when creating the instance. * Storage - Volumes creation fails: in the status field after the creating status, a final error status appears. The log messages just says "Success: Volume v3 created" inside a green bar. * Blueprint - Software in Catalog menu for blueprint tiers needs a clock to show it is loading data (general recommendation for all places) Cheers! -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From manuel.escrichevicente at telefonica.com Wed Oct 15 09:27:00 2014 From: manuel.escrichevicente at telefonica.com (MANUEL ESCRICHE VICENTE) Date: Wed, 15 Oct 2014 07:27:00 +0000 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <543CD5E3.3080909@onesource.pt> References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> Message-ID: Well, the tracker is ready for use. Its name is Testers - it can be changed, if it doesn't capture your role properly. It's placed at the following link: http://jira.fi-ware.org/browse/TEST I need to clarify this is not a tracker for bugs you find but for work items recording what you've tested. For bugs you have those trackers pointed out by Juanjo. Have a snapshot below for visual identification [cid:image002.jpg at 01CFE85A.28D7B680] There's need to create the components - I created COMP1 to test it. Please, let me know what or better tell me who'll be leading this (I wrote Juanjo), and I'll appoint him, this way he can create them as you progress. There's also need to create the users. I you are three works group, I'd propose 1 user for each group. Please, give me feedback to complete the creation and so you can start using it right away. Kind regards, Manuel From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com] On Behalf Of Paulo Simoes Sent: martes, 14 de octubre de 2014 9:51 To: MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal 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 or 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 email: 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 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 ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 13472 bytes Desc: image002.jpg URL: From acs at bitergia.com Wed Oct 15 10:56:07 2014 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 15 Oct 2014 10:56:07 +0200 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> Message-ID: <1413363367.23235.133.camel@bitboy> Hi! El mi?, 15-10-2014 a las 07:27 +0000, MANUEL ESCRICHE VICENTE escribi?: > Well, the tracker is ready for use. Its name is Testers ? it can be > changed, if it doesn?t capture your role properly. > > It?s placed at the following link: http://jira.fi-ware.org/browse/TEST > > > > I need to clarify this is not a tracker for bugs you find but for work > items recording what you?ve tested. For bugs you have those trackers > pointed out by Juanjo. Ok > > > There?s need to create the components ? I created COMP1 to test it. > Please, let me know what or better tell me who?ll be leading this (I > wrote Juanjo), and I?ll appoint him, this way he can create them as > you progress. Hmmm, I was thinking in creating one component per GE to be tested. And also, a global one for FIWARE Labs cloud (what about store, data and mashup?). Also, we can create tickets for tracking also the development samples. > > > > There?s also need to create the users. I you are three works group, > I?d propose 1 user for each group. I have requested accounts using JIRA interface. For Bitergia, could you add a ficore-testing at bitergia.com acocount? > > > > Please, give me feedback to complete the creation and so you can start > using it right away. Cheers! > > > > Kind regards, > > Manuel > > > > > > From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com] On Behalf Of > Paulo Simoes > Sent: martes, 14 de octubre de 2014 9:51 > To: MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org > Subject: Re: [Fiware-friendly-testing] First results from Bitergia > team: A methodology proposal > > > > > > 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 or > 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 > email: 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 > 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 > > > > > > > > ______________________________________________________________________ > > 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 > https://lists.fi-ware.org/listinfo/fiware-friendly-testing -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Wed Oct 15 11:04:12 2014 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 15 Oct 2014 11:04:12 +0200 Subject: [Fiware-friendly-testing] About samples development Message-ID: <1413363852.23235.139.camel@bitboy> Hi all! I know the idea is to start with the samples development in mid November but for us it is useful to start defining them if possible. We have read about the kind of things FIWARE is expected to offer to third party developers [0]. Thinking about it we have thought in a possible sample scenario: monitoring the activity in a project. Maybe you have already defined in FIWARE the testing samples but if not, we can give you more details about this scenario to evaluate it. Cheers [0] http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Frequently_Asked_Questions_(FAQ)#What_kind_of_things_can_FIWARE_do_for_me.3F__How_can_I_incorporate_FIWARE_gradually.3F -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From manuel.escrichevicente at telefonica.com Thu Oct 16 11:30:40 2014 From: manuel.escrichevicente at telefonica.com (MANUEL ESCRICHE VICENTE) Date: Thu, 16 Oct 2014 09:30:40 +0000 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <1413363367.23235.133.camel@bitboy> References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> <1413363367.23235.133.camel@bitboy> Message-ID: Alvaro, I've sent you an invitation to join JIRA. We cannot afford to have three accounts for each group sorry. I understand you're three groups. Paulo? Should I send you another invitation? Who else am I missing? - Sorry!? Manuel -----Original Message----- From: Alvaro del Castillo [mailto:acs at bitergia.com] Sent: mi?rcoles, 15 de octubre de 2014 10:56 To: MANUEL ESCRICHE VICENTE Cc: Paulo Simoes; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Hi! El mi?, 15-10-2014 a las 07:27 +0000, MANUEL ESCRICHE VICENTE escribi?: > Well, the tracker is ready for use. Its name is Testers ? it can be > changed, if it doesn?t capture your role properly. > > It?s placed at the following link: http://jira.fi-ware.org/browse/TEST > > > > I need to clarify this is not a tracker for bugs you find but for work > items recording what you?ve tested. For bugs you have those trackers > pointed out by Juanjo. Ok > > > There?s need to create the components ? I created COMP1 to test it. > Please, let me know what or better tell me who?ll be leading this (I > wrote Juanjo), and I?ll appoint him, this way he can create them as > you progress. Hmmm, I was thinking in creating one component per GE to be tested. And also, a global one for FIWARE Labs cloud (what about store, data and mashup?). Also, we can create tickets for tracking also the development samples. > > > > There?s also need to create the users. I you are three works group, > I?d propose 1 user for each group. I have requested accounts using JIRA interface. For Bitergia, could you add a ficore-testing at bitergia.com acocount? > > > > Please, give me feedback to complete the creation and so you can start > using it right away. Cheers! > > > > Kind regards, > > Manuel > > > > > > From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com] On Behalf Of > Paulo Simoes > Sent: martes, 14 de octubre de 2014 9:51 > To: MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org > Subject: Re: [Fiware-friendly-testing] First results from Bitergia > team: A methodology proposal > > > > > > 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 or > 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 > email: 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/TestingG > Eris > > 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 > > 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 > > > > > > > > ______________________________________________________________________ > > 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 > https://lists.fi-ware.org/listinfo/fiware-friendly-testing -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" ________________________________ 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 From psimoes at onesource.pt Thu Oct 16 11:42:15 2014 From: psimoes at onesource.pt (Paulo Simoes) Date: Thu, 16 Oct 2014 10:42:15 +0100 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> <1413363367.23235.133.camel@bitboy> Message-ID: <543F92F7.7080808@onesource.pt> Yes. Please send us another invitation. Regards, -- PS On 16/10/14 10:30, MANUEL ESCRICHE VICENTE wrote: > Alvaro, I've sent you an invitation to join JIRA. > We cannot afford to have three accounts for each group sorry. > > I understand you're three groups. Paulo? Should I send you another invitation? > > Who else am I missing? - Sorry!? > Manuel > > -----Original Message----- > From: Alvaro del Castillo [mailto:acs at bitergia.com] > Sent: mi?rcoles, 15 de octubre de 2014 10:56 > To: MANUEL ESCRICHE VICENTE > Cc: Paulo Simoes; fiware-friendly-testing at lists.fi-ware.org > Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal > > Hi! > > El mi?, 15-10-2014 a las 07:27 +0000, MANUEL ESCRICHE VICENTE escribi?: >> Well, the tracker is ready for use. Its name is Testers ? it can be >> changed, if it doesn?t capture your role properly. >> >> It?s placed at the following link: http://jira.fi-ware.org/browse/TEST >> >> >> >> I need to clarify this is not a tracker for bugs you find but for work >> items recording what you?ve tested. For bugs you have those trackers >> pointed out by Juanjo. > Ok > > >> >> There?s need to create the components ? I created COMP1 to test it. >> Please, let me know what or better tell me who?ll be leading this (I >> wrote Juanjo), and I?ll appoint him, this way he can create them as >> you progress. > Hmmm, I was thinking in creating one component per GE to be tested. And also, a global one for FIWARE Labs cloud (what about store, data and mashup?). > > Also, we can create tickets for tracking also the development samples. > >> >> >> There?s also need to create the users. I you are three works group, >> I?d propose 1 user for each group. > I have requested accounts using JIRA interface. For Bitergia, could you add a ficore-testing at bitergia.com acocount? > >> >> >> Please, give me feedback to complete the creation and so you can start >> using it right away. > Cheers! > >> >> >> Kind regards, >> >> Manuel >> >> >> >> >> >> From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com] On Behalf Of >> Paulo Simoes >> Sent: martes, 14 de octubre de 2014 9:51 >> To: MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org >> Subject: Re: [Fiware-friendly-testing] First results from Bitergia >> team: A methodology proposal >> >> >> >> >> >> 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 or >> 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 >> email: 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/TestingG >> Eris >> >> 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 >> >> 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 >> >> >> >> >> >> >> >> ______________________________________________________________________ >> >> 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 >> https://lists.fi-ware.org/listinfo/fiware-friendly-testing > > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" > > > > ________________________________ > > 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 From pablofernandezmoniz at gmail.com Sun Oct 19 18:38:16 2014 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Sun, 19 Oct 2014 17:38:16 +0100 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: <543F92F7.7080808@onesource.pt> References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> <1413363367.23235.133.camel@bitboy> <543F92F7.7080808@onesource.pt> Message-ID: Dear Manuel, Please, send me another invitation too. (ULPGC team) Kind regards, 2014-10-16 10:42 GMT+01:00 Paulo Simoes : > > Yes. Please send us another invitation. > > Regards, > > -- PS > > > On 16/10/14 10:30, MANUEL ESCRICHE VICENTE wrote: > >> Alvaro, I've sent you an invitation to join JIRA. >> We cannot afford to have three accounts for each group sorry. >> >> I understand you're three groups. Paulo? Should I send you another >> invitation? >> >> Who else am I missing? - Sorry!? >> Manuel >> >> -----Original Message----- >> From: Alvaro del Castillo [mailto:acs at bitergia.com] >> Sent: mi?rcoles, 15 de octubre de 2014 10:56 >> To: MANUEL ESCRICHE VICENTE >> Cc: Paulo Simoes; fiware-friendly-testing at lists.fi-ware.org >> Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: >> A methodology proposal >> >> Hi! >> >> El mi?, 15-10-2014 a las 07:27 +0000, MANUEL ESCRICHE VICENTE escribi?: >> >>> Well, the tracker is ready for use. Its name is Testers ? it can be >>> changed, if it doesn?t capture your role properly. >>> >>> It?s placed at the following link: http://jira.fi-ware.org/browse/TEST >>> >>> >>> >>> I need to clarify this is not a tracker for bugs you find but for work >>> items recording what you?ve tested. For bugs you have those trackers >>> pointed out by Juanjo. >>> >> Ok >> >> >> >>> There?s need to create the components ? I created COMP1 to test it. >>> Please, let me know what or better tell me who?ll be leading this (I >>> wrote Juanjo), and I?ll appoint him, this way he can create them as >>> you progress. >>> >> Hmmm, I was thinking in creating one component per GE to be tested. And >> also, a global one for FIWARE Labs cloud (what about store, data and >> mashup?). >> >> Also, we can create tickets for tracking also the development samples. >> >> >>> >>> There?s also need to create the users. I you are three works group, >>> I?d propose 1 user for each group. >>> >> I have requested accounts using JIRA interface. For Bitergia, could you >> add a ficore-testing at bitergia.com acocount? >> >> >>> >>> Please, give me feedback to complete the creation and so you can start >>> using it right away. >>> >> Cheers! >> >> >>> >>> Kind regards, >>> >>> Manuel >>> >>> >>> >>> >>> >>> From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com] On Behalf Of >>> Paulo Simoes >>> Sent: martes, 14 de octubre de 2014 9:51 >>> To: MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org >>> Subject: Re: [Fiware-friendly-testing] First results from Bitergia >>> team: A methodology proposal >>> >>> >>> >>> >>> >>> 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 or >>> 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 >>> email: 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/TestingG >>> Eris >>> >>> 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 >>> >>> 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 >>> >>> >>> >>> >>> >>> >>> >>> ______________________________________________________________________ >>> >>> 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 >>> https://lists.fi-ware.org/listinfo/fiware-friendly-testing >>> >> >> -- >> Alvaro del Castillo San F?lix >> acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com >> "Software metrics for your peace of mind" >> >> >> >> ________________________________ >> >> 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 > https://lists.fi-ware.org/listinfo/fiware-friendly-testing > -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Mon Oct 20 00:09:35 2014 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Mon, 20 Oct 2014 00:09:35 +0200 Subject: [Fiware-friendly-testing] About samples development In-Reply-To: <1413363852.23235.139.camel@bitboy> References: <1413363852.23235.139.camel@bitboy> Message-ID: <5444369F.5070809@telefonica.com> Dear Alvaro, We don't agree that the proposed sample scenario is a good scenario. Thanks, anyways, for your proactivity suggesting to start rolling-out this second phase of the Task Force. Please stay tuned until we make a proposal. Cheers, -- Juanjo ------------- Telefonica - Product Development and Innovation (PDI) website: www.tid.es email: 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 15/10/14 11:04, Alvaro del Castillo wrote: Hi all! I know the idea is to start with the samples development in mid November but for us it is useful to start defining them if possible. We have read about the kind of things FIWARE is expected to offer to third party developers [0]. Thinking about it we have thought in a possible sample scenario: monitoring the activity in a project. Maybe you have already defined in FIWARE the testing samples but if not, we can give you more details about this scenario to evaluate it. Cheers [0] http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Frequently_Asked_Questions_(FAQ)#What_kind_of_things_can_FIWARE_do_for_me.3F__How_can_I_incorporate_FIWARE_gradually.3F ________________________________ 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: From acs at bitergia.com Mon Oct 20 08:37:16 2014 From: acs at bitergia.com (Alvaro del Castillo) Date: Mon, 20 Oct 2014 08:37:16 +0200 Subject: [Fiware-friendly-testing] About samples development In-Reply-To: <5444369F.5070809@telefonica.com> References: <1413363852.23235.139.camel@bitboy> <5444369F.5070809@telefonica.com> Message-ID: <1413787036.3699.94.camel@bitboy> Hi! El lun, 20-10-2014 a las 00:09 +0200, Juanjo Hierro escribi?: > Dear Alvaro, > > We don't agree that the proposed sample scenario is a good scenario. > Thanks, anyways, for your proactivity suggesting to start rolling-out > this second phase of the Task Force. > > Please stay tuned until we make a proposal. > Great! Cheers > Cheers, > > -- Juanjo > ------------- > Telefonica - Product Development and Innovation (PDI) > website: www.tid.es > email: 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 15/10/14 11:04, Alvaro del Castillo wrote: > > > Hi all! > > > > I know the idea is to start with the samples development in mid November > > but for us it is useful to start defining them if possible. > > > > We have read about the kind of things FIWARE is expected to offer to > > third party developers [0]. > > > > Thinking about it we have thought in a possible sample scenario: > > monitoring the activity in a project. > > > > Maybe you have already defined in FIWARE the testing samples but if not, > > we can give you more details about this scenario to evaluate it. > > > > Cheers > > > > > > [0] > > http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Frequently_Asked_Questions_(FAQ)#What_kind_of_things_can_FIWARE_do_for_me.3F__How_can_I_incorporate_FIWARE_gradually.3F > > > > ______________________________________________________________________ > > 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 > https://lists.fi-ware.org/listinfo/fiware-friendly-testing -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From manuel.escrichevicente at telefonica.com Mon Oct 20 09:45:33 2014 From: manuel.escrichevicente at telefonica.com (MANUEL ESCRICHE VICENTE) Date: Mon, 20 Oct 2014 07:45:33 +0000 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> <1413363367.23235.133.camel@bitboy> <543F92F7.7080808@onesource.pt> Message-ID: Pablo, I cannot accent any gmail address. Would you please tell me your ?oficial? address? Thanks. Manuel From: Pablo Fern?ndez Moniz [mailto:pablofernandezmoniz at gmail.com] Sent: domingo, 19 de octubre de 2014 18:38 To: Paulo Simoes Cc: MANUEL ESCRICHE VICENTE; Alvaro del Castillo; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Dear Manuel, Please, send me another invitation too. (ULPGC team) Kind regards, 2014-10-16 10:42 GMT+01:00 Paulo Simoes >: Yes. Please send us another invitation. Regards, -- PS On 16/10/14 10:30, MANUEL ESCRICHE VICENTE wrote: Alvaro, I've sent you an invitation to join JIRA. We cannot afford to have three accounts for each group sorry. I understand you're three groups. Paulo? Should I send you another invitation? Who else am I missing? - Sorry!? Manuel -----Original Message----- From: Alvaro del Castillo [mailto:acs at bitergia.com] Sent: mi?rcoles, 15 de octubre de 2014 10:56 To: MANUEL ESCRICHE VICENTE Cc: Paulo Simoes; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Hi! El mi?, 15-10-2014 a las 07:27 +0000, MANUEL ESCRICHE VICENTE escribi?: Well, the tracker is ready for use. Its name is Testers ? it can be changed, if it doesn?t capture your role properly. It?s placed at the following link: http://jira.fi-ware.org/browse/TEST I need to clarify this is not a tracker for bugs you find but for work items recording what you?ve tested. For bugs you have those trackers pointed out by Juanjo. Ok There?s need to create the components ? I created COMP1 to test it. Please, let me know what or better tell me who?ll be leading this (I wrote Juanjo), and I?ll appoint him, this way he can create them as you progress. Hmmm, I was thinking in creating one component per GE to be tested. And also, a global one for FIWARE Labs cloud (what about store, data and mashup?). Also, we can create tickets for tracking also the development samples. There?s also need to create the users. I you are three works group, I?d propose 1 user for each group. I have requested accounts using JIRA interface. For Bitergia, could you add a ficore-testing at bitergia.com acocount? Please, give me feedback to complete the creation and so you can start using it right away. Cheers! Kind regards, Manuel From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com] On Behalf Of Paulo Simoes Sent: martes, 14 de octubre de 2014 9:51 To: MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal 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 or 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 email: 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/TestingG Eris 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 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 ______________________________________________________________________ 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 https://lists.fi-ware.org/listinfo/fiware-friendly-testing -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" ________________________________ 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 https://lists.fi-ware.org/listinfo/fiware-friendly-testing -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter ________________________________ 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: From pablofernandezmoniz at gmail.com Mon Oct 20 10:00:43 2014 From: pablofernandezmoniz at gmail.com (=?UTF-8?Q?Pablo_Fern=C3=A1ndez_Moniz?=) Date: Mon, 20 Oct 2014 09:00:43 +0100 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> <1413363367.23235.133.camel@bitboy> <543F92F7.7080808@onesource.pt> Message-ID: Yes, of course: fiware at ulpgc.es Have a nice day! 2014-10-20 8:45 GMT+01:00 MANUEL ESCRICHE VICENTE < manuel.escrichevicente at telefonica.com>: > Pablo, I cannot accent any gmail address. > > Would you please tell me your ?oficial? address? > > Thanks. > > Manuel > > > > *From:* Pablo Fern?ndez Moniz [mailto:pablofernandezmoniz at gmail.com] > *Sent:* domingo, 19 de octubre de 2014 18:38 > *To:* Paulo Simoes > *Cc:* MANUEL ESCRICHE VICENTE; Alvaro del Castillo; > fiware-friendly-testing at lists.fi-ware.org > > *Subject:* Re: [Fiware-friendly-testing] First results from Bitergia > team: A methodology proposal > > > > Dear Manuel, > > > > Please, send me another invitation too. (ULPGC team) > > > > Kind regards, > > > > 2014-10-16 10:42 GMT+01:00 Paulo Simoes : > > > Yes. Please send us another invitation. > > Regards, > > -- PS > > > > On 16/10/14 10:30, MANUEL ESCRICHE VICENTE wrote: > > Alvaro, I've sent you an invitation to join JIRA. > We cannot afford to have three accounts for each group sorry. > > I understand you're three groups. Paulo? Should I send you another > invitation? > > Who else am I missing? - Sorry!? > Manuel > > -----Original Message----- > From: Alvaro del Castillo [mailto:acs at bitergia.com] > Sent: mi?rcoles, 15 de octubre de 2014 10:56 > To: MANUEL ESCRICHE VICENTE > Cc: Paulo Simoes; fiware-friendly-testing at lists.fi-ware.org > Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A > methodology proposal > > Hi! > > El mi?, 15-10-2014 a las 07:27 +0000, MANUEL ESCRICHE VICENTE escribi?: > > Well, the tracker is ready for use. Its name is Testers ? it can be > changed, if it doesn?t capture your role properly. > > It?s placed at the following link: http://jira.fi-ware.org/browse/TEST > > > > I need to clarify this is not a tracker for bugs you find but for work > items recording what you?ve tested. For bugs you have those trackers > pointed out by Juanjo. > > Ok > > > There?s need to create the components ? I created COMP1 to test it. > Please, let me know what or better tell me who?ll be leading this (I > wrote Juanjo), and I?ll appoint him, this way he can create them as > you progress. > > Hmmm, I was thinking in creating one component per GE to be tested. And > also, a global one for FIWARE Labs cloud (what about store, data and > mashup?). > > Also, we can create tickets for tracking also the development samples. > > > > There?s also need to create the users. I you are three works group, > I?d propose 1 user for each group. > > I have requested accounts using JIRA interface. For Bitergia, could you > add a ficore-testing at bitergia.com acocount? > > > > Please, give me feedback to complete the creation and so you can start > using it right away. > > Cheers! > > > > Kind regards, > > Manuel > > > > > > From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com] On Behalf Of > Paulo Simoes > Sent: martes, 14 de octubre de 2014 9:51 > To: MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org > Subject: Re: [Fiware-friendly-testing] First results from Bitergia > team: A methodology proposal > > > > > > 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 or > 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 > email: 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/TestingG > Eris > > 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 > > 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 > > > > > > > > ______________________________________________________________________ > > 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 > https://lists.fi-ware.org/listinfo/fiware-friendly-testing > > > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com > "Software metrics for your peace of mind" > > > > ________________________________ > > 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 > https://lists.fi-ware.org/listinfo/fiware-friendly-testing > > > > > > -- > > > Pablo Fern?ndez Moniz > > GIT Analyst > > Web Linkedin > Twitter > > > ------------------------------ > > 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 > -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From manuel.escrichevicente at telefonica.com Mon Oct 20 10:09:24 2014 From: manuel.escrichevicente at telefonica.com (MANUEL ESCRICHE VICENTE) Date: Mon, 20 Oct 2014 08:09:24 +0000 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> <1413363367.23235.133.camel@bitboy> <543F92F7.7080808@onesource.pt> Message-ID: <250442767442456fbd2bd95185bb3ff0@DB4PR06MB489.eurprd06.prod.outlook.com> Pablo, I?ve sent the invitation to your gmail address. As soon as you accept it, I?ll modify your address to this: fiware at ulpgc.es From that moment on, all notifications to your user will go to that address. Manuel From: Pablo Fern?ndez Moniz [mailto:pablofernandezmoniz at gmail.com] Sent: lunes, 20 de octubre de 2014 10:01 To: MANUEL ESCRICHE VICENTE Cc: Paulo Simoes; Alvaro del Castillo; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Yes, of course: fiware at ulpgc.es Have a nice day! 2014-10-20 8:45 GMT+01:00 MANUEL ESCRICHE VICENTE >: Pablo, I cannot accent any gmail address. Would you please tell me your ?oficial? address? Thanks. Manuel From: Pablo Fern?ndez Moniz [mailto:pablofernandezmoniz at gmail.com] Sent: domingo, 19 de octubre de 2014 18:38 To: Paulo Simoes Cc: MANUEL ESCRICHE VICENTE; Alvaro del Castillo; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Dear Manuel, Please, send me another invitation too. (ULPGC team) Kind regards, 2014-10-16 10:42 GMT+01:00 Paulo Simoes >: Yes. Please send us another invitation. Regards, -- PS On 16/10/14 10:30, MANUEL ESCRICHE VICENTE wrote: Alvaro, I've sent you an invitation to join JIRA. We cannot afford to have three accounts for each group sorry. I understand you're three groups. Paulo? Should I send you another invitation? Who else am I missing? - Sorry!? Manuel -----Original Message----- From: Alvaro del Castillo [mailto:acs at bitergia.com] Sent: mi?rcoles, 15 de octubre de 2014 10:56 To: MANUEL ESCRICHE VICENTE Cc: Paulo Simoes; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal Hi! El mi?, 15-10-2014 a las 07:27 +0000, MANUEL ESCRICHE VICENTE escribi?: Well, the tracker is ready for use. Its name is Testers ? it can be changed, if it doesn?t capture your role properly. It?s placed at the following link: http://jira.fi-ware.org/browse/TEST I need to clarify this is not a tracker for bugs you find but for work items recording what you?ve tested. For bugs you have those trackers pointed out by Juanjo. Ok There?s need to create the components ? I created COMP1 to test it. Please, let me know what or better tell me who?ll be leading this (I wrote Juanjo), and I?ll appoint him, this way he can create them as you progress. Hmmm, I was thinking in creating one component per GE to be tested. And also, a global one for FIWARE Labs cloud (what about store, data and mashup?). Also, we can create tickets for tracking also the development samples. There?s also need to create the users. I you are three works group, I?d propose 1 user for each group. I have requested accounts using JIRA interface. For Bitergia, could you add a ficore-testing at bitergia.com acocount? Please, give me feedback to complete the creation and so you can start using it right away. Cheers! Kind regards, Manuel From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com] On Behalf Of Paulo Simoes Sent: martes, 14 de octubre de 2014 9:51 To: MANUEL ESCRICHE VICENTE; fiware-friendly-testing at lists.fi-ware.org Subject: Re: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal 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 or 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 email: 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/TestingG Eris 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 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 ______________________________________________________________________ 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 https://lists.fi-ware.org/listinfo/fiware-friendly-testing -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" ________________________________ 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 https://lists.fi-ware.org/listinfo/fiware-friendly-testing -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter ________________________________ 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 -- Pablo Fern?ndez Moniz GIT Analyst Web Linkedin Twitter ________________________________ 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: From psimoes at onesource.pt Mon Oct 20 10:24:33 2014 From: psimoes at onesource.pt (Paulo Simoes) Date: Mon, 20 Oct 2014 09:24:33 +0100 Subject: [Fiware-friendly-testing] First results from Bitergia team: A methodology proposal In-Reply-To: References: <1412934247.23235.14.camel@bitboy> <54380263.3070109@telefonica.com> <543B96E5.3060706@onesource.pt> <407c2d55a68748f9ae8a5a3a9fc2fccc@DB4PR06MB489.eurprd06.prod.outlook.com> <543CD5E3.3080909@onesource.pt> <1413363367.23235.133.camel@bitboy> <543F92F7.7080808@onesource.pt> Message-ID: <5444C6C1.2070303@onesource.pt> psimoes at onesource.pt Regards, -- PS On 20/10/14 08:45, MANUEL ESCRICHE VICENTE wrote: > > Pablo, I cannot accent any gmail address. > > Would you please tell me your ?oficial? address? > > Thanks. > > Manuel > > *From:*Pablo Fern?ndez Moniz [mailto:pablofernandezmoniz at gmail.com] > *Sent:* domingo, 19 de octubre de 2014 18:38 > *To:* Paulo Simoes > *Cc:* MANUEL ESCRICHE VICENTE; Alvaro del Castillo; > fiware-friendly-testing at lists.fi-ware.org > *Subject:* Re: [Fiware-friendly-testing] First results from Bitergia > team: A methodology proposal > > Dear Manuel, > > Please, send me another invitation too. (ULPGC team) > > Kind regards, > > 2014-10-16 10:42 GMT+01:00 Paulo Simoes >: > > > Yes. Please send us another invitation. > > Regards, > > -- PS > > > > On 16/10/14 10:30, MANUEL ESCRICHE VICENTE wrote: > > Alvaro, I've sent you an invitation to join JIRA. > We cannot afford to have three accounts for each group sorry. > > I understand you're three groups. Paulo? Should I send you > another invitation? > > Who else am I missing? - Sorry!? > Manuel > > -----Original Message----- > From: Alvaro del Castillo [mailto:acs at bitergia.com > ] > Sent: mi?rcoles, 15 de octubre de 2014 10:56 > To: MANUEL ESCRICHE VICENTE > Cc: Paulo Simoes; fiware-friendly-testing at lists.fi-ware.org > > Subject: Re: [Fiware-friendly-testing] First results from > Bitergia team: A methodology proposal > > Hi! > > El mi?, 15-10-2014 a las 07:27 +0000, MANUEL ESCRICHE VICENTE > escribi?: > > Well, the tracker is ready for use. Its name is Testers ? > it can be > changed, if it doesn?t capture your role properly. > > It?s placed at the following link: > http://jira.fi-ware.org/browse/TEST > > > > > I need to clarify this is not a tracker for bugs you find > but for work > items recording what you?ve tested. For bugs you have > those trackers > pointed out by Juanjo. > > Ok > > > There?s need to create the components ? I created COMP1 to > test it. > Please, let me know what or better tell me who?ll be > leading this (I > wrote Juanjo), and I?ll appoint him, this way he can > create them as > you progress. > > Hmmm, I was thinking in creating one component per GE to be > tested. And also, a global one for FIWARE Labs cloud (what > about store, data and mashup?). > > Also, we can create tickets for tracking also the development > samples. > > > > There?s also need to create the users. I you are three > works group, > I?d propose 1 user for each group. > > I have requested accounts using JIRA interface. For Bitergia, > could you add a ficore-testing at bitergia.com > acocount? > > > > Please, give me feedback to complete the creation and so > you can start > using it right away. > > Cheers! > > > > Kind regards, > > Manuel > > > > > > From: Paulo Simoes [mailto:paulo.a.f.simoes at gmail.com > ] On Behalf Of > Paulo Simoes > Sent: martes, 14 de octubre de 2014 9:51 > To: MANUEL ESCRICHE VICENTE; > fiware-friendly-testing at lists.fi-ware.org > > Subject: Re: [Fiware-friendly-testing] First results from > Bitergia > team: A methodology proposal > > > > > > 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 > or > 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 > email: 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/TestingG > Eris > > 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 > > > 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 > > > > > > > > ______________________________________________________________________ > > 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 > > https://lists.fi-ware.org/listinfo/fiware-friendly-testing > > > -- > Alvaro del Castillo San F?lix > acs at bitergia.com - Chief Technical > Officer (CTO) http://www.bitergia.com "Software metrics for > your peace of mind" > > > > ________________________________ > > 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 > > https://lists.fi-ware.org/listinfo/fiware-friendly-testing > > > > -- > > > Pablo Fern?ndez Moniz > > GIT Analyst > > Web Linkedin > Twitter > > > > ------------------------------------------------------------------------ > > 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: From fiware at ulpgc.es Wed Oct 22 11:19:59 2014 From: fiware at ulpgc.es (Fi-ware ULPGC) Date: Wed, 22 Oct 2014 10:19:59 +0100 Subject: [Fiware-friendly-testing] [Cloud] [Design] Field errors are shown in two languages Message-ID: Web Browser: Google Chrome version 38.0.2125.104 Operating System: OSX version 10.9.5 User id: cloudtestulpgc Tenant: 00000000000000000000000000006443 Description Errors are displayed in a combination of english and spanish. Even if you change the region, spanish is still used. If all web is in written in english, errors should be in english to. How to replicate: Leave blank a mandatory field or use an invalid format. [image: Captura de pantalla 2014-10-20 a la(s) 13.36.37.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From fiware at ulpgc.es Wed Oct 22 16:46:57 2014 From: fiware at ulpgc.es (Fi-ware ULPGC) Date: Wed, 22 Oct 2014 15:46:57 +0100 Subject: [Fiware-friendly-testing] [Store] Resource registering form - Selectable Content type Message-ID: Web Browser: Mozilla Firefox, v. 33 ; Google Chrome, v. 38.0.2125.104 Operating System: Windows 8 User id: storedata.test.ulpgc at gmail.com Description The resource registering form is working fine. Maybe it could be better if the ?Control-type? field allows you to choose between regularly used options, like ?application/x-widget+mashable-application-component?. Or there should be any help to know how or what we have to fill in this box. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pgalves at onesource.pt Fri Oct 24 17:59:41 2014 From: pgalves at onesource.pt (Pedro Alves) Date: Fri, 24 Oct 2014 16:59:41 +0100 Subject: [Fiware-friendly-testing] Request: Floating IP in Spain region Message-ID: Hello, I'm testing the CEP GE but I don have a Floating IP in the Spanish region. The IP pool for this region has no available IPs. This GE is not available in all regions. I tried to deploy an instance (based on cep) in the Mexico and Trento Regions but there where errors on launching on both regions. Could you provide me one Floating IP in Spain? My user name is Pedteste with email: pgalves at o*****k..com (some chars were striped from the email) Thanks in advance. Regards, -- Pedro Alves pgalves at onesource.pt http://onesource.pt -------------- next part -------------- An HTML attachment was scrubbed... URL: From joagonca at onesource.pt Mon Oct 13 11:43:41 2014 From: joagonca at onesource.pt (=?utf-8?Q?Jo=C3=A3o_Gon=C3=A7alves?=) Date: Mon, 13 Oct 2014 09:43:41 -0000 Subject: [Fiware-friendly-testing] Some usability questions Message-ID: Dear all, Since we?ve got the other two mailing lists to provide feedback and/or issue questions that a regular user might do, we figured we could use this mailing list to provide reports on usability questions that might, at some point, create some distrust on the end user regarding the FI-WARE platform. If by any means you?re not OK with this approach, please let us know. General Certificate error when accessing the labs. When issuing a command, often the interface fails to inform the user that it is performing the task on the background (this could trigger the user to request the same action more than one time). Modal loading screens with no option to cancel or go back (the whole page is blacked out). The user can create an account without accepting the Terms of Service. Could/Instances When creating an instance, the bar counters (the numbers only) are not updated. The placeholder text on ?Add Security Group? cannot be read in its entirety, not informing the user correctly about the limitations of the names allowed. Cloud/Security Downloaded key file comes with the name ?Unknown? and no extension. When creating the rules, there?s a ?Cancel" button whereas a ?Close? reflects more the action in cause. FIWARE Catalogue The images names on the catalogue do not correspond to the names present in the lab interface, leading to confusion. Regards, - - - Jo?o Gon?alves joagonca at onesource.pt 00 351 927 997 531 http://onesource.pt -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Thu Oct 16 21:17:52 2014 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 16 Oct 2014 21:17:52 +0200 Subject: [Fiware-friendly-testing] Testing from create-net on all lab Message-ID: Dear all, Here are some reports: GUI issues: https://docs.google.com/document/d/1b_HGA5U4Y082eIOYZniTzJyz70hCt1J4qsvz9_h8fQM/edit Node status: https://docs.google.com/spreadsheets/d/14y5fsgQn_mcS1joEX8zGQV9OO0C-h1XmOWQEmdCEsN4/edit I will re-run node status tomorrow. I had experienced some huge delays with tokens from the interface and this may be affecting all nodes behavior (including spain, that as you can see is affected as well). Best, Federico -- Dr. Federico M. Facca CREATE-NET Via alla Cascata 56/D 38123 Povo Trento (Italy) T +39 0461 408400 (1669) F +39 0461 421157 M +39 334 6049758 E federico.facca at create-net.org W www.create-net.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From joagonca at onesource.pt Mon Oct 13 16:16:27 2014 From: joagonca at onesource.pt (=?utf-8?Q?Jo=C3=A3o_Gon=C3=A7alves?=) Date: Mon, 13 Oct 2014 14:16:27 -0000 Subject: [Fiware-friendly-testing] Some usability questions In-Reply-To: References: Message-ID: Hi Fernando, The bar numbers not being updated can be seen in the screenshot_1.png in attach. But now by looking again at it, I can understand that the counters refer to the number of items already taken by previous instances. Am I correct? I created my account without accepting the Terms of Service. I did that using the latest installation of Safari for Mac OS X. The placeholder text can be seen in screenshot_2.png in attach. And yes, the ?Create new security group option?. Apologies for not being clear. Best, - - - Jo?o Gon?alves joagonca at onesource.pt 00 351 927 997 531 http://onesource.pt On 13 Oct 2014 at 15:05:13, FERNANDO LOPEZ AGUILAR (fernando.lopezaguilar at telefonica.com) wrote: Hi?Jo?o Thank you very much for your description. I am try to reproduce your comments. Could you clarify in more details what are you describing here: * ?When creating an instance, the bar counters (the numbers only) are not updated.? Could you give me an image or more description of where you have this problem? You are talking about the Instance count do not show the green part when you try to create a new instance? Regarding the following comments: * ?The user can create an account without accepting the Terms of Service.? Could you say me which browser are you using? In Chrome I cannot reproduce it. * "The placeholder text on ?Add Security Group? cannot be read in its entirety, not informing the user correctly about the limitations of the names allowed.? You mean the option ?Add new Security Group in the ?Launch Instances? window? De: Jo?o Gon?alves Responder a: Jo?o Gon?alves Fecha: Monday 13 October 2014 11:43 Para: "fiware-friendly-testing at lists.fi-ware.org" Asunto: [Fiware-friendly-testing] Some usability questions Nuevo env?o de: Jo?o Gon?alves Nuevo env?o para: Fecha de nuevo env?o: Monday 13 October 2014 11:45 Dear all, Since we?ve got the other two mailing lists to provide feedback and/or issue questions that a regular user might do, we figured we could use this mailing list to provide reports on usability questions that might, at some point, create some distrust on the end user regarding the FI-WARE platform. If by any means you?re not OK with this approach, please let us know. General Certificate error when accessing the labs. When issuing a command, often the interface fails to inform the user that it is performing the task on the background (this could trigger the user to request the same action more than one time). Modal loading screens with no option to cancel or go back (the whole page is blacked out). The user can create an account without accepting the Terms of Service. Could/Instances When creating an instance, the bar counters (the numbers only) are not updated. The placeholder text on ?Add Security Group? cannot be read in its entirety, not informing the user correctly about the limitations of the names allowed. Cloud/Security Downloaded key file comes with the name ?Unknown? and no extension. When creating the rules, there?s a ?Cancel" button whereas a ?Close? reflects more the action in cause. FIWARE Catalogue The images names on the catalogue do not correspond to the names present in the lab interface, leading to confusion. Regards, - - - Jo?o Gon?alves joagonca at onesource.pt 00 351 927 997 531 http://onesource.pt 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: screenshot_1.png Type: image/png Size: 164863 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: screenshot_2.png Type: image/png Size: 69854 bytes Desc: not available URL: From fiware at ulpgc.es Wed Oct 22 16:35:23 2014 From: fiware at ulpgc.es (Fi-ware ULPGC) Date: Wed, 22 Oct 2014 15:35:23 +0100 Subject: [Fiware-friendly-testing] [Store] [Data] You can purchase a paid CKAN dataset or a paid Widget at the Store without paying for it Message-ID: Web Browser: Mozilla Firefox, v. 33 ; Google Chrome, v. 38.0.2125.104 Operating System: Windows 8 User id: storedata.test.ulpgc at gmail.com/pablofm at hotmail.com Description: While we are checking the resources information of a CKAN dataset or a Widget, you can see a [X.XX ?] button below the icon. If you decide to push it and fill all the steps with fake information, you can acquire a paid dataset without paying. A invoice PDF with your fake information is generated and you can access to the data without any problem. We tested with ?Midemo2?, and ?Madrid Transport Evolution? datasets (1.0? and 2.0?) and "Berlin Chat" widget (1?). Some screenshow with the paid data in CKAN is showed below this lines. We found not intuitive the current way to "pay" for it and also is hard to know if the process of buying has been completed successfully or not. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Captura de pantalla 2014-10-21 a las 22.21.49.png Type: image/png Size: 152366 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Captura de pantalla 2014-10-21 a las 21.10.20.png Type: image/png Size: 799196 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Purchasing a paid dataset without pay for it - 1.png Type: image/png Size: 293678 bytes Desc: not available URL: From abbas.ahmad at edu.univ-fcomte.fr Tue Oct 28 09:43:48 2014 From: abbas.ahmad at edu.univ-fcomte.fr (abbas ahmad) Date: Tue, 28 Oct 2014 09:43:48 +0100 (CET) Subject: [Fiware-friendly-testing] Reporting issues. In-Reply-To: <359996120.9283312.1414485756294.JavaMail.root@edu.univ-fcomte.fr> Message-ID: <9375008.9283374.1414485828671.JavaMail.root@edu.univ-fcomte.fr> Dear all, from now own we should only report issues in Jira ( http://jira.fi-ware.org/ browse/TEST ) or keep using this mailing list ? Best -------------- next part -------------- An HTML attachment was scrubbed... URL: