Hello Salvatore, I have enabled the Standard Operation "discoverContextAvailability", and I believe test I7 is ready for testing. Please use: http://172.30.1.131:8080/ngsi9/discoverContextAvailability I haven't heard back from either Laurent or Fermin, which probably indicates that they are busy...so I guess we need to wait for them. I hope we can still do the tests. I hope in future when it comes to integration tests, we should be ready to expect issues, errors unaccounted for, misunderstanding etc. and work around that. But anyway, I do apologize from my part. >From my opinion I don't think we need to hang around on the phone. Can still use email. The instances are deployed and ready to be tested, aren't they? If there is an error then please just copy and paste it in an email, then report it. That's what I did with the testbed team when it came to sanity checks, and that went well. But if you still want to contact me directly via IM/VoIP/Phone, please let me know. Just to note, I will be unavailable today between 2-4pm (European time). Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of t.elsaleh at surrey.ac.uk Sent: 21 November 2013 17:03 To: Salvatore.Longo at neclab.eu; fermin at tid.es; laurent.artusio at orange.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Today integration session results (TID's components) Hello Fermin, Laurent and Salvatore, Sorry for today's confusion. Look like I'm focusing more on the "added value" services than the basics. :) 1. Tests I6 and I8 (Data Handling / Backend Device Mgmt) Ok, so now I have added the Standard Operation for RegisterContext. This means tests I6 and I8 can be done. · http://172.30.1.131:8080/ngsi9/registerContext Please go ahead with the tests when you are ready. If you think we should be connected during the test, then let me know you preferable channel. If Skype, my ID is "elsaleh_74". Also it would be useful to send me a copy of what you registered. 2. Test I7: I'm still working on this Salvatore, and will try get back to you early tomorrow. Just a quick question (maybe Fermin can help), when you provide multiple attributes in the discovery request, do you expect an entity with all the attributes (AND), or an entity that has any of these attributes (OR)? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Salvatore Longo Sent: 21 November 2013 16:30 To: Fermín Galán Márquez Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu> Subject: Re: [Fiware-iot] Today integration session results (TID's components) Dear Fermin, Attached there are the screenshot that I did for the ID3, ID4 and ID5 cases. Could you please add to the zip file and attach it to the wiki page. Thanks a lot. BR, - Salvatore Longo ________________________________ Salvatore Longo Software Engineer NEC Europe Ltd. Kurfürsten-Anlage 36 D-69115 Heidelberg Tel. +49/(0) 62 21/43 42 - 246 Fax. +49/(0) 62 21/43 42 - 115 E-Mail: Salvatore.longo at neclab.eu<mailto:Salvatore.longo at neclab.eu> NEC Europe Limited Registered Office: NEC House, 1 Victoria Road, London W3 6BL Registered in England 2832014 ________________________________ From: Fermín Galán Márquez [mailto:fermin at tid.es] Sent: Donnerstag, 21. November 2013 16:49 To: Salvatore Longo Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu> Subject: Today integration session results (TID's components) Hi, As discussed this morning, please find attached (in the .zip) the captures we have gathered related with TID's elements both in screen snapshots and text files (the later extracted from GEis text logs) during today's integration session, using the following naming convention: [BDM-|DH-]ID<test_case>-<step>-[In|Out].[txt.png] The "BDM-" or "DH-" prefix is used only for test cases in which there was different XMLs for Backend Device Management GEi (BDM) or Data Handling (DH) GEi (actually: ID1, ID4 and ID5). Some additional remarks: 1. The reference for test IDs and steps numbers are in the wiki page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2 2. As far as I know, ID6 to ID10 wasn't executed today (ID6 to ID8 not executed given that IoTDiscovery GEi is not supporting the required API calls for integration). 3. We haven't recorded the DH-ID1-1-Out case. Laurent, could you provide it, please? 4. We haven't recorded any ID3 case. Salvatore, could you provide these, please? 5. We haven't recorded the the [BDM-|DH-]ID4-1-Out cases. Salvatore, could you provide these, please? 6. We have edited the test cases in the wiki in which we have participated (in particular ID1, ID2, ID4 and ID5) to update test information at the start of each section (Date, status, etc.) and references to the final XMLs used for "Input Data" and "Actual result". Given that XML has problems to be correctly rendered in this wiki (anybody is able to solve it?), we have opted by citing XML from a (currently not existing) IoTIntegration.zip file (that could be uploaded to docman or passed directly to the person in charge of testing in FI-WARE). * This "IoTIntegration.zip" files doesn't exist yet, but I volunteer to create, upload and link it from the wiki if the other partners provide me the needed screen snapshots for that (bullets 3, 4 and 5 above) (We = TID above) I'm CCing the whole chapter, as I think integration is a general topic. Best regards, ------ Fermín ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20131122/740ec295/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy