#opendaylight-persistence: Persistence Weekly meeting

Meeting summary

1. 1. New member joins Persistence project - Raminder (nachiket331, 17:05:47)
   
   
2. System test plan review (nachiket331, 17:09:28)
   1. Integration test page is https://wiki.opendaylight.org/view/Persistence:Lithium:Jpa_Integration_System_Test (nachiket331, 17:12:40)
   2. ACTION: Fabiel to put a note in the system test plan on Recommended Karaf features that these feature are needed and not just recommended (nachiket331, 17:15:16)
   3. ACTION: Step 1 is not required in "Test feature installation" (fabiel, 17:18:50)
   4. ACTION: Step 4 is worng (must be via create) in "Test primary key integrity constraint violation" (fabiel, 17:24:31)
   5. ACTION: add a column to specify the type of datastore the test is valid. For example "Test primary key integrity constraint violation" is only for relational databases. The same with "Test update nonexistent object" (fabiel, 17:26:45)
   6. we need general, relational and non-relational test suites. (fabiel, 17:27:52)
   7. ACTION: "Test delete non existing object": The size of the table should be 1 (not 0), and use "non-existent id" instead of "invalid" (fabiel, 17:29:20)

Action items

1. Fabiel to put a note in the system test plan on Recommended Karaf features that these feature are needed and not just recommended
2. Step 1 is not required in "Test feature installation"
3. Step 4 is worng (must be via create) in "Test primary key integrity constraint violation"
4. add a column to specify the type of datastore the test is valid. For example "Test primary key integrity constraint violation" is only for relational databases. The same with "Test update nonexistent object"
5. "Test delete non existing object": The size of the table should be 1 (not 0), and use "non-existent id" instead of "invalid"

Action items, by person

1. fabiel
   1. Fabiel to put a note in the system test plan on Recommended Karaf features that these feature are needed and not just recommended
2. UNASSIGNED
   1. Step 1 is not required in "Test feature installation"
   2. Step 4 is worng (must be via create) in "Test primary key integrity constraint violation"
   3. add a column to specify the type of datastore the test is valid. For example "Test primary key integrity constraint violation" is only for relational databases. The same with "Test update nonexistent object"
   4. "Test delete non existing object": The size of the table should be 1 (not 0), and use "non-existent id" instead of "invalid"

People present (lines said)

1. fabiel (6)
2. nachiket331 (6)
3. odl_meetbot (4)