Integration tests between Gatekeeper and Catalogues about son-gkeeper

[felipevicens]

Integration test:
Gatekeeper <--> Catalogue | Packages

http://wiki.sonata-nfv.eu/index.php/Integration_Test_Gatekeeper_Catalogue_/_Packages

[shuaibsiddiqui]

The different highlevel initial tests I have in mind for integration of GK & SP Catalogue:

1. GK performs a POST for each one of the following one by one i) PD, ii) NSD, iii) VNFD_1, iv) VNFD_2, v) VNFD_3
2. GK performs a GET (using the UUID only) for each one of the following one by one i) PD, ii) NSD, iii) VNFD_1, iv) VNFD_2, v) VNFD_3

@jbonnet: For CTLS, it is obscure that a NSD or VNFD belong to a particular PD, so inconsistencies due to only some of the xDs are stored can be handled in at the GK after receiving the responses for each POST. Either repeat the particular failing POST untill it is successfull or in case of roll back perform DELETE for the successful ones (I prefer the former one:D)

I can populate the wikipage with relevant information and UML user stories for each of the above tests (8 in total if we do them separately)

@felipevicens Can you please elaborate what you mean by "You should write this using Jenkins as a main Actor." under Test Story section of the wikipage you referred to in your previous post.

[felipevicens]

@shuaibsiddiqui The test story should be writing considering that Mr. Jenkins will be the "person" who will execute the actions or will trigger the actions and will check the results. For example 1. Jenkins deploy the test environment. 2. Jenkins trigger an action (POST GET PUT DELETE). Jenkins check the results.

[shuaibsiddiqui]

@felipevicens Ok great .. I'll keep Uncle Jenkins in the loop :D