Test repository reorganization 2

Luis Gomez

Hi all,

After the comments today, I have created 2nd proposal for reorganization:


The resulted structure could be the following:

1) Testopia Repository:

Product —Test Plan (Product Version, Test Type) — Test Case (Category)

2) GIT:

Repo — test — csit — suites — main suite per distro — sub suite per feature group — file

3) Jenkins:

Project — Job — Job Build

4) Testopia Run:

Project — Test Plan (Product Version, Test Type) — Test Run (Build)

Let me know what you think.


On May 27, 2014, at 6:20 PM, Luis Gomez <ecelgp@...> wrote:

Hi all,

I have not received many comments on this so I am not sure if my mail is clear enough. I will explain all this in the call tomorrow, I hope to see you there!


On May 23, 2014, at 4:22 PM, Luis Gomez <ecelgp@...> wrote:

Hi all,

I would like to share with you a proposal to reorganize our test repository that will address some of the latest discussions like:

- Create smaller test suites that can run stand-alone without need of running entire distros test
- Use these modules to easily build the distros test
- Align GIT/Robot structure with Testopia
- Align Jenkins jobs with Testopia
- Understand the test variables declared in repository and those passed at run time
- Understand how new Robot plugin reports to Testopia

Please take a look on this sheet:


And some comments on the tabs:

1) Test Repository:

- If you look at first row, I tried to match GIT/Robot terminology with Testopia terminology
- Testopia Product is "Integration" for 2 reasons: 1) a Test Run cannot cross 2 products and 2) I would like to offer projects possibility to document their tests (like Junit) in Testopia
- Testopia Test plan is the overall Continuous System Integration Test (CSIT) because Test Runs cannot go across Test Plans
- A Testopia Test category is what I call an individual test suite
- Finally Testopia Test case matches a Robot test file

2) Test Runs:

- If you look at first row, I also tried to match Jenkins/Robot terminology with Testopia terminology
- Testopia Test Runs match the existing distribution CSIT jobs we have in Jenkins. Test Runs will be dynamically created in Testopia every time a CSIT job gets fired. This is the mission of the new Robot plugin that will be developed by Mohammad
- Every Test Run or CSIT job is composed of smaller test suites organized in Test Categories

3) Test Variables:

- Some variables already existed, others are new like the ones needed by new Robot plugin to report to Testopia

Please let me know your comments and suggestions asap and also feel free to propose other alternatives.


Join integration-dev@lists.opendaylight.org to automatically receive all group messages.