David,
It seems that the wiki page is deprecated (the procedure exits on
failure).401: TestAPI id is not provided

We can't add new test cases as proposed by
> https://wiki.opnfv.org/pages/viewpage.action?pageId=6825128
Cédric
On mer., 2018-05-16 at 08:47 -0700, David McBride wrote:
> Team,
> 
> Traditional track:  this is a requirement.
> 
> 
> CD track:  we are making MS2 optional for the CD track until the new
> release process is further developed. Please send me feedback about:
> Does MS2 (test case documentation) make sense for the CD track?Should
> the schedule for the milestone be the same as for the traditional
> track (i.e., two weeks after release plans are due)?How should we
> define compliance? For the traditional track, we have the test case
> database. Projects show compliance by sending me a link to their test
> cases in the DB.  Is there something equivalent for the CD
> track?Milestone 2 - test case documentation - is scheduled for 1 week
> from Friday on May 25.  Once you have documented your test cases in
> the test case database, please send me a link to those test cases so
> that I can credit your compliance.
> See these instructions for declaring your project and adding your
> test cases:https://wiki.opnfv.org/pages/viewpage.action?pageId=682512
> 8
> To demonstrate compliance, please send me a URL like the one used as
> an example in the instructions:http://testresults.opnfv.org/test/api/
> v1/projects/fastdatastacks/cases
> 
> Please let me know if you have any questions.
> 
> -- 
> David McBrideRelease Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
> 
> 
> _______________________________________________
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to