Hi,
Thanks all for sharing your feedback. I think we all recognize that providing test coverage is something that cannot be achieve overnight hence the reason why we have built the checklists and the periodic milestones. I guess none of us want to be in the same situation we were in M4 for Amsterdam in Paris, negotiating extra time to reach the target. The basic idea is to start early, unit testing should not be an after thoughts but rather baked in. Some repos have already achieve their 50% goals. I can even some repos are over 80% code coverage. Excellent work. Listening to your feedback, I would like to propose the community (the TSC will need to decide here) to set 50% code coverage as a stretch goal for M2 and M3 and a mandatory goal for M4. In the M2 and M3 checklist simply provide a screenshot of your progress. Regarding repos that require Python, LF told me the work is in progress. I am hoping to learn a firm date from LF next week during the V F2F. In the meantime, as we did in Amsterdam, provide a screenshot of your local code coverage. Here is the link to Sonar<https://urldefense.proofpoint.com/v2/url?u=https-3A__sonar.onap.org_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=77AGr306xPmtTxr7jxu2MDoUqQZpL_kIMBlhZlnxEQg&s=RuNscooFGu3NF5LDhD7_jyKAUtFn_fH6k_nhPg2n0rA&e=> to visualize the status (you can sort it out by “Overall Coverage”, by “Name” or by “Last Analysis” date). Let me know if you have any questions, I will be glad to help. Thanks, Gildas ONAP Release Manager 1 415 238 6287 -----Original Message----- From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com] Sent: Thursday, February 01, 2018 6:45 AM To: Seshu m <seshu.kuma...@huawei.com>; Gildas Lanilis <gildas.lani...@huawei.com> Cc: onap-rele...@lists.onap.org Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage Gildas, Same here. Please consider moving 50% as gating requirement for M4. Thanks, Lusheng Ji On 2/1/18, 6:13 AM, "onap-release-boun...@lists.onap.org on behalf of Seshu m<mailto:onap-release-boun...@lists.onap.org%20on%20behalf%20of%20Seshu%20m>" <onap-release-boun...@lists.onap.org on behalf of seshu.kuma...@huawei.com<mailto:onap-release-boun...@lists.onap.org%20on%20behalf%20of%20seshu.kuma...@huawei.com>> wrote: Hi Gildas, I share the same thoughts, we have the functional aspects being worked upon till M2 and still a lot of discussions/clarifications are required there. So, it would be better to consider 50% code coverage for M4 and 30% for M2. Best regards Seshu Kumar M Huawei Technologies India Pvt, Ltd. 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! -----Original Message----- From: onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org> [mailto:onap-release-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine Sent: Thursday, February 01, 2018 5:40 AM To: Shankaranarayanan P N Cc: onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage Gildas, I agree with the feedback provided by the PTLs The 50% test coverage is a new Beijing requirement as part of S3P/Security therefore it should be treated as any other Beijing code deliverable i.e being gated at M4 code freeze milestone. I am not aware that SP3 requirements are expected to be completed earlier. 30% test coverage should be gated at M2/M3 milestone. Please also note that non-java test coverage can not yet been measured. We really need to progress on this issue as well. Best regards Catherine Le 31 janv. 2018 à 15:14, Shankaranarayanan P N <shankarp...@gmail.com<mailto:shankarp...@gmail.com<mailto:shankarp...@gmail.com%3cmailto:shankarp...@gmail.com>>> a écrit : Hi Gildas, I have the same concerns that Jimmy and Randa raised here. In particular, the seed code for OOF is being upstreamed for the first time in Beijing Release. While we do have unit test coverage as one of our priorities in R2, we had planned progressive test coverage increase to happen as we move along towards M4. Given this, it would be very challenging to have a 50% coverage by the M2 timeline. Would providing evidence on the test coverage goals, along with resources committed for the same be sufficient for M2? Thanks, Shankar On Wed, Jan 31, 2018 at 2:02 PM MAHER, RANDA <rx1...@att.com<mailto:rx1...@att.com<mailto:rx1...@att.com%3cmailto:rx1...@att.com>>> wrote: Hi Gildas, The code coverage targets given are for the release; I don’t see how we can require that it be completed by M2, which is only half way into the second sprint, and still quite a ways away from Code Complete. Would you agree that for M2 we should provide evidence that this goal is being addressed as part of the plan and being progresses with every sprint to get to the ultimate goal by M4? Thanks, Randa From: onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org%3cmailto:onap-release-boun...@lists.onap.org>> [mailto:onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org><mailto:onap-release-boun...@lists.onap.org%3cmailto:onap-release-boun...@lists.onap.org%3e>] On Behalf Of Gildas Lanilis Sent: Wednesday, January 31, 2018 1:54 PM To: FORSYTH, JAMES <jf2...@att.com<mailto:jf2...@att.com<mailto:jf2...@att.com%3cmailto:jf2...@att.com>>>; DRAGOSH, PAM <pdrag...@research.att.com<mailto:pdrag...@research.att.com<mailto:pdrag...@research.att.com%3cmailto:pdrag...@research.att.com>>>; onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org%3cmailto:onap-rele...@lists.onap.org>> Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage Hi Jimmy, As usual, we will provide the data as reported in Sonar<https://urldefense.proofpoint.com/v2/url?u=https-3A__sonar.onap.org_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=h2hDhxBMcclnvo943vVwKrajRwLLlCcM9TcYY2wUZ8k&s=X21Pp0rpkrT1088xZAt4eMwKRSx_zZpTx5GZbW9lHKQ&e=> and the TSC will provide its disposition. Thanks, Gildas ONAP Release Manager 1 415 238 6287<tel:(415)%20238-6287> From: FORSYTH, JAMES [mailto:jf2...@att.com] Sent: Wednesday, January 31, 2018 10:45 AM To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com%3cmailto:gildas.lani...@huawei.com>>>; DRAGOSH, PAM <pdrag...@research.att.com<mailto:pdrag...@research.att.com<mailto:pdrag...@research.att.com%3cmailto:pdrag...@research.att.com>>>; onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org%3cmailto:onap-rele...@lists.onap.org>> Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage Hi, Gildas, So does this mean that we will not pass M2 unless we are at 50% coverage in all repos? Thanks, jimmy From: <onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org%3cmailto:onap-release-boun...@lists.onap.org>>> on behalf of Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com%3cmailto:gildas.lani...@huawei.com>>> Date: Wednesday, January 31, 2018 at 1:42 PM To: "DRAGOSH, PAM" <pdrag...@research.att.com<mailto:pdrag...@research.att.com<mailto:pdrag...@research.att.com%3cmailto:pdrag...@research.att.com>>>, "onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org><mailto:onap-rele...@lists.onap.org%3cmailto:onap-rele...@lists.onap.org%3e>" <onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org%3cmailto:onap-rele...@lists.onap.org>>> Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage Hi Pam, Thanks for reaching out. In fact for Beijing release the requirement is to reach 50% of code coverage (included within Maturity Platform requirement<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_download_attachments_16002054_Platform-2520Maturity-2520Level-2520proposal-252013Dec2017v2.pdf-3Fversion-3D1-26modificationDate-3D1513625784000-26api-3Dv2&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Oej6QUk5p2KdqNEWySpOHA&m=seH5IvNvB4JuA_IYSHbvnXoCZTwFA0N4iHJ0pMWgV4M&s=U_wAVey0I4hcujhIXNRGbmu26E_5x0_5PhdZOpE729U&e=>). My fault here, I forgot to update the wiki accordingly (I just fixed it). More specifically to your question, yes 50% code coverage is expected by M2 and M3 and M4. The intend here is to develop unit test simultaneously as the code is being developed. The issue is that it is always hard (if not impossible) for the teams to catch up later on these items. When will come M4, teams will have other urgent matters to focus on. Better to do it as the code is being developed. I understand it can be difficult, but I believe this is the right thing. Thanks, Gildas ONAP Release Manager 1 415 238 6287<tel:(415)%20238-6287> From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com] Sent: Wednesday, January 31, 2018 8:14 AM To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com%3cmailto:gildas.lani...@huawei.com>>>; onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org%3cmailto:onap-rele...@lists.onap.org>> Subject: M2 Requirement for JUnit code coverage Gildas, One of the requirements for M2 is for Incubation Junit coverage 30-50%. I want to clarify if this is still true or if by M2 you are expecting projects to be at the requested 50% coverage level per the Beijing Platform Maturity requirements? If so, that is going to be difficult to attain in such a short period of time and I’m wondering if that should be on the M4 checklist instead? Thanks, Pam _______________________________________________ Onap-release mailing list onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org%3cmailto:onap-rele...@lists.onap.org>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Drelease&d=DwIGbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=Gl7_p27PBsamBr8jY8XImLS_DD3Hj4bsVVec8je4Fb8&s=Iumt1wckOQsZM2ArCXBOs9jiTn7KyPp6ld7gvBeSmqM&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Drelease&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M&m=ta-Ugz8h81Yc7uLGlbVwkFzUyiWuQNInESsS1UOI-Aw&s=br8g9WPiSfcyRi8v3_BkD7458bWdpT0Bezw05sX25gk&e=> _______________________________________________ Onap-release mailing list onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org%3cmailto:onap-rele...@lists.onap.org>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Drelease&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M&m=ta-Ugz8h81Yc7uLGlbVwkFzUyiWuQNInESsS1UOI-Aw&s=br8g9WPiSfcyRi8v3_BkD7458bWdpT0Bezw05sX25gk&e= _______________________________________________ Onap-release mailing list onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Drelease&d=DwIGbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=Gl7_p27PBsamBr8jY8XImLS_DD3Hj4bsVVec8je4Fb8&s=Iumt1wckOQsZM2ArCXBOs9jiTn7KyPp6ld7gvBeSmqM&e= _______________________________________________ Onap-release mailing list onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Drelease&d=DwIGbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=Gl7_p27PBsamBr8jY8XImLS_DD3Hj4bsVVec8je4Fb8&s=Iumt1wckOQsZM2ArCXBOs9jiTn7KyPp6ld7gvBeSmqM&e=
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
