Hi,
Agreed. “Releasing” something that has not been –properly– tested is not a good
practice. By “properly” I mean following the same procedures we use to verify
all the other scenarios.
We need to emphasize that manual testing or “I run my own tests and it works”
is not sufficient. Testing
Hi all --
So first of all kudos to the JOID team for introducing this new technology
-- it's an important step forward.
Secondly, obviously it doesn't make sense to run OpenStack tests against
something that doesn't implement OpenStack.
I'm really worried, however, about "releasing" something
Hi,
I tend to agree about running the same set of test cases to all scenarios. But
if the test frameworks are not prepared for a certain technology (like in this
case K8), it doesn’t make sense to execute them. It’s a waste of time and we
know beforehand that it will fail systematically.
We
This is a follow-up to a conversation on IRC (opnfv-release) earlier today.
When asked about disabling Functest and Yardstick for the new K8 scenarios
on Joid, I agreed. My reasoning was that I didn't want to delay release of
new and potentially interesting scenarios. I also know that functest
