Hi,

during the last release meeting we had a discussion on the structure of
the testing documentation for Danube

we suggest to adopt the following approach for the test projects

|/docs|

||_ release|

|...|
|   |_ release-notes // release note of the projects involved in the
release|
|                         reference
http://testresults.opnfv.org/reporting snapshot of the status at the
release date|
|...|
||_ testing|

|    testing overview // umbrella document => figure, description of the
testing ecosystem, pointers to project documentation|
|    |__ user         // will collect the documentation of the test
projects allowing the end user to perform testing towards a OPNFV SUT|
|                     e.g.
Functest/Yardstick/Vsperf/Storperf/Bottlenecks/Qtip installation/config
& user guides|
|    |__ developer    // will collect documentation to explain how to
create your own test case and leverage existing testing frameworks|
|                     e.g. devloper guides|



the umbrella testing documentation "testing overview" is under opnfvdocs
=> will be put into /testing

the other documents are in the project repos under
<repo>/docs
                        /installation guide
                        /config guide
                        /user guide
                        /release note
                        /development
                                    /development guide
                                    / interships

----------------------------------------------------------------------------------
|      Test Project Repo                   |   Target in docs.opnfv.org 
|                           
----------------------------------------------------------------------------------
| installation, config, user guide    |  testing/user                      |
| development guide                     |  testing/developer             |
| release note                                | 
release-notes/testing       |
----------------------------------------------------------------------------------

@Sofia, David: is it OK for you?

Morgan

_________________________________________________________________________________________________________________________

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
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to