Hi again folks, So we have at this point a few test cases that are still failing, and we’re awaiting at least two fixes on the CTT. I don’t know whether all the issues will be resolved when we get the new CTT (hopefully Monday), but at this point, there isn’t a whole lot more we can do in the meantime. Mitch, Dan and I are all traveling for the weekend anyway, so that’s ok.
We’ll see what the results are with the new CTT 1.5.24 and I’ll update again. I should clarify: what we are seeing, for the most part, is corner-case behavior that is causing issues. In many cases, the CTT is doing things that a normal Client wouldn’t do, in order to test aspects of the Specification that are not easy to test via the RESTful interfaces (SVRs, primarily) provided by the IUT. So we’re as much debugging the CTT and steps it takes to test IoTivity, as we are IoTivity. Still, we are finding issues in the IoTivity code that need to be addressed, and fixing them, so it’s not wasted time. But hopefully that explains why we’re still testing/fixing, even though the basic nominal flows have been okay for a while now. Thanks, Nathan From: Heldt-Sheller, Nathan Sent: Thursday, October 26, 2017 9:48 PM To: 'uzc...@samsung.com' <uzc...@samsung.com>; 'iotivity-dev@lists.iotivity.org' <iotivity-dev@lists.iotivity.org> Cc: abith...@samsung.com; 'Mitch Kettrick' <c...@openconnectivity.org>; 'Daniel Mihai (WINDOWS)' <daniel.mi...@microsoft.com> Subject: RE: [dev] P1 Pending Issues and CTT Open Issues for 1.3.1 release Hi folks, update time: Dan, Mitch and I went full speed all day and into this evening (thanks again Dan and Mitch), and we resolved several more issues. We also identified a few more issues in the CTT that we’ll need to have fixed before we can pass. We also may (or may not) have more IoTivity issues still lurking… so we’ll do our best to test & fix while we wait for the CTT fixes, and I’ll update EOD tomorrow with status, so Abitha can create (or postpone) RC5 tag. Thanks, Nathan From: Heldt-Sheller, Nathan Sent: Wednesday, October 25, 2017 6:44 PM To: '최우제 (Uze Choi)' <uzc...@samsung.com<mailto:uzc...@samsung.com>>; iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org> Subject: RE: [dev] P1 Pending Issues and CTT Open Issues for 1.3.1 release Will do Uze; Mitch and I are working on the issue right now. Dan Mihai is digging into another issue, and I’ll get his status tomorrow a.m. (PST) and report back. Thanks, Nathan From: 최우제 (Uze Choi) [mailto:uzc...@samsung.com] Sent: Wednesday, October 25, 2017 6:42 PM To: Heldt-Sheller, Nathan <nathan.heldt-shel...@intel.com<mailto:nathan.heldt-shel...@intel.com>>; iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org> Subject: RE: [dev] P1 Pending Issues and CTT Open Issues for 1.3.1 release Thanks for prompt response. If they are resolved, please inform to us for tagging and starting test. BR, Uze Choi From: Heldt-Sheller, Nathan [mailto:nathan.heldt-shel...@intel.com] Sent: Thursday, October 26, 2017 10:40 AM To: uzc...@samsung.com<mailto:uzc...@samsung.com>; iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org> Subject: RE: [dev] P1 Pending Issues and CTT Open Issues for 1.3.1 release Hi Uze, We still have at least one Test Case failing that we aren’t sure yet if it’s an IoTivity bug or not. Also, we need to confirm with SecWG that they are aligned with OSWG Security TG in making some test cases “optional”. So I think we cannot tag RC5 yet. Thanks, Nathan From: iotivity-dev-boun...@lists.iotivity.org<mailto:iotivity-dev-boun...@lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ??? (Uze Choi) Sent: Wednesday, October 25, 2017 6:36 PM To: iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org> Subject: Re: [dev] P1 Pending Issues and CTT Open Issues for 1.3.1 release Dear Nathan/Abitha, According to Nathan Comment below for IOT-2829 and status report, all related code are already in 1.3-rel branch as of now. https://jira.iotivity.org/browse/IOT-2829 - Comment [nathanheldtsheller] Nathan Heldt-Sheller<https://jira.iotivity.org/secure/ViewProfile.jspa?name=nathanheldtsheller> added a comment - 2 hours ago After discussing with OSWG Sec TG this a.m., I think we've decided that this isn't smart to try to "diving catch" implement, and is corner-case and security-certification (vs. interop-certification) related. For all those reasons we're going to suggest removing from the list of Required for Cert TCs. Abitha, do we need to make a tag for final release candidate for testing start? BR, Uze Choi From: iotivity-dev-boun...@lists.iotivity.org<mailto:iotivity-dev-boun...@lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ABITHA S Sent: Wednesday, October 25, 2017 9:37 PM To: iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org> Subject: [dev] P1 Pending Issues and CTT Open Issues for 1.3.1 release Dear All, Please find below the current status of Open issues. Pending P1 Issues Security 2 Alljoyn Bridge<https://jira.iotivity.org/issues/?jql=project+%3D+IOT+AND+component+%3D+%22Alljoyn+Bridge%22> 1 Total 3 CTT Bugs Count 1 and below is the summary of the current list of P1 issues captured from Iotivity Jira. Issue key Summary Assignee Priority Status Found in Version Component/s Status 1 IOT-1738 AllJoyn Bridge implementation todd.malsbary P1 Assigned 1.3-rel Alljoyn Bridge Pending testing with updated CTT tool 2 IOT-2821 CT1.7.8.11 - DOXS should have implicit access to /cred and /acl2 in RFOTM mkettrick P1 In Progress 1.3-rel Security Pending QA verification 3 IOT-2829 CT1.7.8.11 - Access to Vertical Resources is only allowed in RFNOP nathanheldtsheller P1 In Progress 1.3-rel Security Fix in Progress And Below the list of CTT bugs pending for Affected Version set to Amsterdam Bug ID Product Component Assignee Status Summary 1 1397 OCF (public) CTT c...@openconnectivity.org<mailto:c...@openconnectivity.org> UNCONFIRMED Create a schema file to represent the allowable enumerations in the SH Device spec As per the Work items shared from each maintainers for respective modules for 1.3.1 release, updated in https://wiki.iotivity.org/1.3.1_release_plan Below are the list of issues which are not yet resolved but mentioned as work items to be taken for the release. Kindly update the status of below issues and estimated date of completion for the same. Base Layer. • https://jira.iotivity.org/browse/IOT-2684 - Rectify RD delete request error returning two error responses in place of one Security • https://jira.iotivity.org/browse/IOT-1896 - Implement privacy mitigation approach for unique identifiers Bridging • https://jira.iotivity.org/browse/IOT-1738 - AllJoyn Bridge implementation Other Fixes • https://jira.iotivity.org/browse/IOT-2539 - Remove Compiler Warnings in Linux Few of the above changes are pending approvals from Reviewers. I request reviewers to review the same so that we can incorporate these changes in 1.3.1 Regards, Abitha Thanks and Regards, Abitha.S [cid:image002.png@01D34F53.E0C2F7B0] [http://ext.samsung.net/mail/ext/v1/external/status/update?userid=abitha.s&do=bWFpbElEPTIwMTcxMDI1MTIzNzExZXBjbXM1cDZkMDlhYjYwMDAyYThmMjVkMzBkYzgxYzkzMGVjMzVkOSZyZWNpcGllbnRBZGRyZXNzPWlvdGl2aXR5LWRldkBsaXN0cy5pb3Rpdml0eS5vcmc_]
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
