08:07:51 #startmeeting tacker 08:07:52 Meeting started Tue Jun 23 08:07:51 2020 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:07:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:07:55 The meeting name has been set to 'tacker' 08:08:08 please go a head 08:08:16 OK 08:08:22 https://etherpad.opendev.org/p/tacker-meeting 08:09:09 I'd like to discuss TST010 discuss (L17-), especially, bold part. 08:09:21 s/L17/L27/ 08:11:15 First(L36-), I'd like to request to make all 2xx test and 4xx test. I also ask TST's policy about coverage of response code. Is it OK? 08:11:41 I can't access above link 08:12:22 Really? I can access it... 08:12:31 I can access, too. so might be network problem? 08:12:35 no problem from my side too 08:12:58 I can access, too. 08:13:27 takahashi-tsc: could you write down the point here if possible 08:13:46 I can see now sorry 08:13:50 You means all points about TST discuss? 08:15:21 OK, return back to the topic 08:16:10 basically I agree to request all 2xx and 4xx tests 08:16:12 I roughly agreed with your suggestion in the last meeting, and no objection. 08:16:27 LGTM 08:16:33 Sure, so move to next topic. 08:16:45 About HTTP response header 08:17:41 I agree that we need tests which check HTTP response header. 08:17:46 In SOL002/003, there are only description about "Location" and "Link" fileds. Our request is only testing them? Is there anything others? 08:19:46 I'm not sure how our request will be when requesting response header tests 08:20:22 will it be a request to add check points related to response header in TST010? 08:21:18 "Location" and "Link" fields should be reply from server side, so we should check. I think these filed can be checked by Robot Framework. 08:22:20 In my opinion, these test is included in "API test". 08:23:36 I agree. Some testcase in TST010 have some check points like "Check HTTP Response Header Contains ETag" 08:24:23 but not sure our requests can be a request to TST010 to pick up all response header related check points, or simply to implement RF 08:25:23 all RF codes is implemented according to TST010 so we need the check description in TST010 to have the test in RF 08:25:42 +1 08:27:50 OK, so I think this should be a question or suggestion, not a strong request. And before that, we should check TST010 spec document. 08:28:10 +1 08:28:28 +1 08:28:47 +1 08:29:49 Anything else? if no, move to next topic 08:30:35 go a head please 08:31:41 OK, I'll request to clarify tagging/branch naming policy of api-tests repository. 08:32:27 +1 08:32:51 This is just required for development to use ROBOT framework, our task. We need to identify the test code set. I would like TST team to define such policy. 08:33:53 +1 08:35:15 OK, and last is about IOP tests. yoshito-ito thank you for your suggenstion 08:36:38 I think this is not about TST010, so I'll not include this topic in TST010 meeting on 30th June. But we need discussion to define our testing policy. 08:38:49 Sorry but I do not read the details of TST007 and plugtests test code yet... Anyway I'd like to continue to discuss. 08:40:06 IOP test codes in etsi repo seems still under development 08:41:19 so I agree to put this IOP test topic as our testing policy discussion 08:41:44 and not to include in the coming TST010 meeeting 08:42:18 Sure, thanks. 08:42:56 That's all from me. Any other comments about TST discussion? 08:43:01 I agree to include IOP in our target 08:43:32 takahashi-tsc: thanks 08:46:42 It seems done all today 08:46:59 This is for logging. I would like to review EventAlarm from takahashi-tsc, https://review.opendev.org/#/c/700167/ 08:47:11 Thanks 08:48:41 I would like to close this meeting if nothing remained. 08:49:32 Thanks for joining, bye 08:49:46 bye 08:50:04 #endmeeting