Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RI 1 Dev] Port VSPERF testcases to Xtesting #511

Open
collivier opened this issue Oct 29, 2019 · 7 comments
Open

[RI 1 Dev] Port VSPERF testcases to Xtesting #511

collivier opened this issue Oct 29, 2019 · 7 comments
Assignees
Projects

Comments

@collivier
Copy link
Collaborator

Xtesting allows a smooth integration of sparsed testcases and ease building CI/CD toolchains via an Ansible role.
http://testresults.opnfv.org/functest/stockholm/

Here leveraging on Xtesting will ease building CI/CD toolchains in few commands mixing Functest and VSPERF testcases. It also simplifies any validation process as it avoids extra logics per test frameworks (jenkins job templates, certification, etc.)
https://wiki.opnfv.org/pages/viewpage.action?pageId=32015004

@collivier collivier assigned collivier, acmacm and rrajesh70 and unassigned collivier and acmacm Oct 29, 2019
@rabiabdel rabiabdel added this to the Snezka milestone Nov 5, 2019
@rrajesh70
Copy link
Collaborator

Cedric & Sridhar, It is my understanding that xTesting is a thin layer/framework that integrates with CI/CD pipelines and can execute OPNFV tests from multiple projects, example Yardstick, FuncTest and VSPERF.
Logic contained in xTesting will detect a) any VNF code changes, b) any NFVI/platform code changes, c) any changes to the test scripts or any new test cases added to the OPNFV projects. Upon detection of these changes, xTesting should 'intelligently invoke the right subset of tests to re-run. For example, any changes to Yardstick test cases should only re-run Yardstick tests. The results should be versioned, and associated with all the necessary config files

@michaelfix
Copy link
Collaborator

status update @collivier ?

@michaelfix
Copy link
Collaborator

status?

@michaelfix
Copy link
Collaborator

@collivier - status?

@collivier collivier removed their assignment Jan 10, 2020
@michaelfix michaelfix modified the milestones: Snezka, Backlog Jan 10, 2020
@rabi-abdel rabi-abdel added this to To Do in RI1 via automation Feb 6, 2020
@rabi-abdel rabi-abdel added RI 1 and removed RI 1 Dev labels Feb 6, 2020
@rabi-abdel rabi-abdel added this to To do in RC1 via automation Feb 6, 2020
@rabi-abdel rabi-abdel added RC 1 and removed RC 1 Dev labels Feb 6, 2020
@rabi-abdel rabi-abdel removed this from the Backlog milestone Feb 11, 2020
@rabi-abdel rabi-abdel added this to the M3 (Freeze Contributions) milestone Feb 25, 2020
@michaelfix
Copy link
Collaborator

status @collivier and @opensource-tnbt ?

@jayacha
Copy link
Collaborator

jayacha commented Apr 14, 2020

Performance related, recommending to move to backlog

@jayacha jayacha modified the milestones: M3 (Freeze Contributions), Backlog Apr 14, 2020
@project-bot project-bot bot moved this from To Do to Backlog in RI1 Apr 14, 2020
@project-bot project-bot bot moved this from To do to Backlog in RC1 Apr 14, 2020
@rabi-abdel rabi-abdel removed this from the Backlog milestone May 15, 2020
@fuqiao123 fuqiao123 removed the Backlog label May 18, 2020
@fuqiao123 fuqiao123 added this to the M3 (Freeze Contributions) milestone May 18, 2020
@fuqiao123 fuqiao123 moved this from Backlog to To do in RC1 May 18, 2020
@jayacha jayacha moved this from Backlog to To Do in RI1 May 27, 2020
@gkunz gkunz closed this as completed Aug 26, 2021
RC1 automation moved this from To do to Done Aug 26, 2021
RI1 automation moved this from To Do to Done Aug 26, 2021
@gkunz gkunz reopened this Aug 26, 2021
RI1 automation moved this from Done to To Do Aug 26, 2021
RC1 automation moved this from Done to To do Aug 26, 2021
@gkunz
Copy link
Collaborator

gkunz commented Aug 26, 2021

sorry, wrong ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
RC1
  
To do
RI1
  
To Do
Development

No branches or pull requests

9 participants