hi

I think you need to contact Dovetail project.
As far as I know, the token API has been introduced to secure the reporting for 
dovetail.
Serena should have the best view on this topic now.

/Morgan

Le mardi 29 mai 2018 à 10:46 +0200, [email protected] a écrit :
Hello David,

Functest team doesn't maintain the API (we are endusers) and I'm not aware 
about that changes.
This procedure should be maintained by the right devs instead of Functest team.

Morgan and Jose had very well described the procedure as it was.

Cédric

On lun., 2018-05-28 at 21:24 -0700, David McBride wrote:
+Jose, Morgan for background/history

Cedric,

The procedure was documented by Jose Lausuch (previous Functest PTL), so 
presumably, this procedure is owned by Functest. Is that not correct?  If not, 
then who owns the procedure.

David

On Mon, May 28, 2018 at 5:08 AM, 
<[email protected]<mailto:[email protected]>> wrote:
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<https://wiki.opnfv.org/pages/viewpage.action?pageId=6825128> for 
declaring your project and adding your test cases:
https://wiki.opnfv.org/pages/viewpage.action?pageId=6825128

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 McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018<tel:%2B1.805.276.8018>
Email/Google Talk: 
[email protected]<mailto:[email protected]>
Skype: davidjmcbride1
IRC: dmcbride

_______________________________________________
opnfv-tech-discuss mailing list
[email protected]<mailto:[email protected]>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss






_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to