Agenda:

  1. Check readiness of new CSIT team (Sireesh) on Robot test plan - Portal R2 Beijing Functional Test Cases
  2. Portal JUnit code coverage 50% target (Hari team)
  3. Review status on items assigned to dev team
  4. Go over JIRA list assigned for Beijing release


Attendees:

Sireesh, Girish, Lorraine, Saravanan

Discussion Items:

1.Sireesh started setting up local environment for robot test and reviewing test cases from previous release.

  • will contact Leimeng to know new features; 
  • Hima will help setup the Portal in local testers machine.
  • set up new test cases
  • found some bugs, to work out with the development team
  • environment set up; scheduled call on this for this afternoon
  • For PORTAL-173 : 24 test cases from before, added 12 more , will check in test case scripts this week into gerrit 
  • JIRA ticket is in progress state

2.vm11 test environment to check the bugs and to perform testing - Sunder/Leimeng  discovered issue where new function code introduced, but not in DML script. - Lorraine will check

 new JIRA ticket - PORTAL-209 was opened to replace Portal-175. - in submitted state

3. AAF integration with SDC - help Micheal Lando - Sunder/Leimeng  Leimeng will send document to partners (check with Sunder too) ASDC descoped AAF integration 

4. Portal-182 - CLI integration help - Leimeng to setup a working session - Sunder Tattavarada/user-67d6f 

  1. Start working on Jan 31st – Leimeng will organize a call with Sunder/CLI team on Wed 9:00am (Sunder could not join the meeting, when is the next meeting?)
  2. Another working call was made and Making progress - check with Sunder
  3. this ticket is in reopened state

5. Portal-155 - security issues scan - Nexus IQ and Coverity scans

  1. Need Access on Nexus IQ - Farhan/S
  2. Coverity scan followup with Stephen.terrill@ericsson.com - Farhan
  3. many user stories created regarding this big item, pending to assign to developer. (assigned to Sudeep)

6. Security issues status from CLM (Nexus IQ)  - Sudeep  -  this is Portal-155

  1. pull request made, fixed in portal; but not SDK, new pull request for SDK will be made for what is working
  2. ETA today for pull request - SDK
  3. merged in portal/sdk - done
  4. sdk onap issue working
  5. this ticket is in open state

7. Plan to release SDK 2.1.0 version and then communicate to partners to update their poms - Sunder/Leimeng - ETA 1/19.  ==> update ETA to 1/25 - Sunder need help to find 

  1. Sunder emailed to LF team - however, LF team asked for latest build reference as the last build is 2 weeks old.
  2. completed SDK 2.1.0 released

8. Extend Portal-119 to split DB for Portal and SDK - Robert - design session pending and ETA on dev tasks.  - Robert working on it now

  1. Robert is using VM3 for this effort. → 70% done by Robert
  2. Update the deployment scripts with docker image name changes - 
    1. demo repo (heat templates); 
    2. integration repo (CSIT test deployment scripts); 
    3. OOM deployment;
  3. JIRA ticket is in progress state

9. Sent grep scan on "master_dev" branch to check if "ecomp" appears in Portal - done - Hima will be cleaning up - ETA 1/10.

  1. ECOMP keyword in license text - followup with Catherine - Manoop ETA 2/16 ==> still pending - resolved check email
  2. java class names - we can leave it as is 
  3. * ECOMP is a trademark and service mark of AT&T Intellectual Property.        ---------- Can be removed
  4. Catherine suggested via email: I would suggest to remove it in the License.txt file posted on the root repo. Then later on, change in file you are updating

10. JUnit /Sonar coverage to 50% on SDK and Portal. - Deadline March 15th for SDK

    1. SDK - JUnit test coverage reached 19.7% - Hima (pending code review and push to gerrit) - Code need to push to gerrit - PORTAL-161  -  Add the JUNIT plumbing for PortalSDK   Delivered
      1. Shireesh will coordinate his team with Hima and Kishore Gujja - done
      2. Local version is up to 24-25%, planning on pushing today - Sitharaman
      3. 26.1%
      4. Saravanan   now  37.7%
      5. JIRA ticket is in delivered state; I recommend reopening and putting in in progress state until 50% is reached
  2. Portal - target 30% to 50% - Girish/Hari team will continue from Gerrit -     PORTAL-136   -  Raise JUnit test coverage ONAP Portal to 50% for Beijing   Open
      1. Hari is coordinating the remaining code coverage on Portal (right now it is at 48.7%) - Kishore,
      2. Manoop to followup with Gildas on the Sonar upgrade issue which got 2% down for portal form 40 - 38% (this is due to change in sonar calculation with new upgrade).
      3. 50.2 close ticket
      4. now 50.5 Portal-136 should be Closed, it is still in open state

11.Discussed remaining JIRA items in great details → portal-151

a.(assign priority from items in wiki page to JIRA by Leimeng)

b. JIRA ticket is in open state

12. MUSIC integration - add JIRA epic/US - Sunder to provide the % complete

  1. Development is targeting to complete by 02/28
  2. Leimeng to coordinate a meeting to share the MUSIC integration details with testing teams to plan the test strategy for these features.
  3. on-track, couple days to wrap up development
  4. Robert 80% finished ; needs more testing
  5. need update

13. AAF, if AAF is not ready for testing by 2/15, then Portal will not integrated with AAF for Beijing release - Leimeng send email to Sai - Is the AAF instance ready in LAB env to test the integration?

  1. Sunder to followup with Sai -   ask Sunder
  2. need update

14. Defect tracking of Critical and Highs - Naveen and Shireesh to coordinate with Leimeng/Lorraine to test and close them and raise as concern if cannot be closed.

  1. automated testing making progress on VM11 
  2. Sunder will refresh VM11 environment
  3. looking at test cases
  4. will set up separate meeting (if needed) for critical and high issues
  5. will contact Lorraine if there are any road blocks to closing any
  6. Naveen not getting updates from team - Sunder should set up call with Sireesh and Naveen if possible; Sireesh says they  need help with local setup - having call on it with Sunder


15.

  1. Beijing Release Planning:
  2. M0 - dev kick-off, Nov 16
  3. M1 - planning Jan 16
  4. M2 Functionality Freeze  →  fill in the contents by Manoop & Leimeng - done
  5. M3 API/Data Model Freeze 
  6. M4 Code Freeze