[
https://issues.jboss.org/browse/SWSQE-145?page=com.atlassian.jira.plugin....
]
Jeeva Kandasamy edited comment on SWSQE-145 at 4/19/18 8:48 AM:
----------------------------------------------------------------
[~gbaufake] The proposed design looks good.
I have a question on Test runs.
* On step-4 we create traffic and on step-5 we execute our tests
* I guess traffic data will be random
* *If yes,*
* In this approach Test will not know about traffic information
* How can we validate Kiali with generated traffic on test phase?
* *If no,*
* When we follow static data all the time, There is a possibility to miss bugs
My personal opinion, we should have some easy mechanism, to trigger traffic(with defined
parameters -> will be used to validate kiali) from test side(at least for integration
tests).
was (Author: jkandasa):
[~gbaufake] The proposed design looks good.
I have a question on Test runs.
* On step-4 we create traffic and on step-5 we execute our tests
* I guess traffic data will be random
# If yes,
* In this approach Test will not know about traffic information
* How can we validate Kiali with generated traffic on test phase?
# If no,
* When we follow static data all the time, There is a possibility to miss bugs
My personal opinion, we should have some easy mechanism, to trigger traffic(with defined
parameters -> will be used to validate kiali) from test side(at least for integration
tests).
Modularize CI/CD Pipline
------------------------
Key: SWSQE-145
URL:
https://issues.jboss.org/browse/SWSQE-145
Project: Kiali QE
Issue Type: Epic
Reporter: Matt Mahoney
Assignee: Guilherme Baufaker RĂªgo
Attachments: Kiali Pipeline Proposal.png
The CI/CD pipeline has become more complex and challenging with which to build CI/CD
usage-cases and to add new functionality:
Use Case Examples:
1) Deploy Istio -> Deploy&build-kiali -> Deploy All Service Meshes ->
Deploy Traffic Generator on all Service Meshes -> Run all test suites
2) Deploy built Kiali -> Run REST suite
3) Build and Deploy Kiali -> Run all test suites
4) Run UI suite on any Openshift Cluster
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)