15:04:18 <trevc> #startmeeting OPNFV Test WG
15:04:18 <collabot`> Meeting started Thu Nov 17 15:04:18 2016 UTC.  The chair is trevc. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:04:18 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:04:18 <collabot`> The meeting name has been set to 'opnfv_test_wg'
15:04:31 <hongbo1> #info hongbo
15:04:47 <kubi001> #info kubi
15:04:53 <bryan_att> #info Bryan Sullivan
15:05:23 <trevc> #info Trevor Cooper
15:05:43 <yujunz> #info Yujun Zhang
15:06:00 <jose_lausuch> #info Jose Lausuch
15:06:05 <HelenYao> info Helen Yao
15:06:12 <HelenYao> #undo
15:06:18 <HelenYao> #info Helen Yao
15:06:18 <morgan_orange> #info Morgan Richomme
15:06:18 <Mingjiang5> #info Rex
15:06:25 <trevc> #topic Test community common goals (20') https://etherpad.opnfv.org/p/TestCommunityGoals
15:06:52 <wenjing> #info Wenjing Chu
15:07:09 <yujunz> Poor audio here. Anybody experiencing the same?
15:07:35 <JingLu_> #info Jing Lu
15:08:18 <trevc> #info Discuss goals and priorities for D release
15:08:33 <trevc> #info Was difficult to describe exactly what was in Colorado
15:09:33 <trevc> #info Morgan proposed making a summary (1 pager) of what is in the release
15:11:44 <bryan_att> #info isn't this type of planning for Danube already too late per the release schedule?
15:12:18 <trevc> #info Several categories are described in https://etherpad.opnfv.org/p/TestCommunityGoals ... everybody is invited to comment and add items
15:15:29 <trevc> #info Need to be realistic as to what can get done. If not already tasks in Danube may not be possible but we should try and get started / experimental
15:17:31 <trevc> #info Bryan suggests organized as common goals and assign to releases
15:28:24 <trevc> #info Will continue to take input and discuss until end of November and plan to take recommendations to TSC
15:31:39 <trevc> #topic Dovetail
15:32:34 <trevc> #info Wenjing presents on Dovetail
15:33:09 <trevc> #info Dovetail building test suite based on Colorado
15:34:40 <trevc> #info First Dovetail test suite uses Functest and Yardstick test cases
15:42:23 <bryan_att> #info for putting tests into JIRA that we can track, see https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=147&projectKey=DOVETAIL ; we need to continue the transfer of tests from the wiki to JIRA if we intend to use JIRA as a test tracking tool.
15:46:43 <dmcbride> #info there are many tools available for documenting and managing test cases, such as Test Link, for example.
15:48:25 <bryan_att> #info the set of tests on the wiki https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Cases are a start on a set of assertions, that on an earlier Dovetail call we agreed to start migrating to JIRA. But since that initial concept demo (the JIRA link above) no further tests have been migrated as there (AFAICT) has not been explicit agreement that we should
15:48:25 <bryan_att> use JIRA in this way.
15:48:46 <bryan_att> #info ... use JIRA in this way
15:51:08 <bryan_att> #info So I think dovetail needs to make a specific decision as to how it intends to manage the test assertion and case lists (they will be different, as cases will cover multiple assertions typically), and we need to know who specifically is signing up to do the work of populating the initial test assertion/case databases (if in JIRA or otherwise).
16:00:46 <bryan_att> #info so I'm getting that we do not intend to use JIRA for management of tests
16:02:18 <yujunz> #info kindly reminding that we are running out of time
16:02:30 <yujunz> I would propose to postpone the last topic to next week
16:03:54 <bryan_att> #info to me the topic is clear - where (in what tool) are we intending to manage the set of tests and what they claim to validate (test assertions)
16:05:16 <bryan_att> #info if the existing mongodb database has a way to do that, it should be clarified so we can start the process of populating it with test assertions in addition to the test cases
16:06:21 <bryan_att> #info having some tests, and having them generate some results, is inadequate. We need to know what those tests do specifically, and measure that against what we are expecting to be covered in testing.
16:07:04 <trevc> bryan_att: agreed
16:07:25 <bryan_att> trevc: thanks!
16:08:33 <bryan_att> #info I'm happy to jump in and start populating the data with other's help, if we can just agree what tool we plan to use and how within that tool we will achieve the goals of managing test coverage
16:20:00 <yujunz> If no embedded image or video, size of text is not a big deal for database
16:20:59 <trevc> #endmeeting