One suggestion if we agree, we can move all "plugin" related functional test cases added so far like nuage,brocade or others, in to test/integration/component/"plugins"/. Not always, we may run them with equipment available for those plugins, in regular regression we can still run normal functional suites, otherwise picking up complete component folder enables all test suites to be picked up for automation run.
Santhosh ________________________________________ From: Trippie [trip...@gmail.com] on behalf of Hugo Trippaers [h...@apache.org] Sent: Wednesday, July 23, 2014 5:16 AM To: <dev@cloudstack.apache.org> Subject: Re: Guidelines on Functional Test for plugins Talluri, Can you also add the new functional tests in the brocade plugin? test/integration/component/test_brocade_vcs.py Cheers, Hugo On 21 jul. 2014, at 12:09, Hugo Trippaers <trip...@gmail.com> wrote: > Santosh, Talluri, > > Can you guys make sure the functional tests created by Suresh are integrated > in the CI runs? > > test/integration//component/test_nuage_vsp.py > > Cheers, > > Hugo > > > On 15 jul. 2014, at 14:07, Suresh Ramamurthy > <suresh.ramamur...@nuagenetworks.net> wrote: > >> Hi All, >> >> Can any one please point me to any document or example for sample FT for >> plugins. >> Testing plugin needs some setup tp be available. >> >> Is there any way in ACS framework where we can bypass the setup and still >> test the functionality? >> In some cases where the client library can not be redistributed, how do we >> test it? >> >> Please let me know so that I can write some FT for plugin that we are >> developing. >> >> Thanks, >> Suresh >
