redhat-developer
Continuous testing
/kind feature
Which functionality do you think we should add?
Add a testing mode to odo so that it can run the tests continuously. This is a combination of watch and test functionality however the tests should be run on a separate container and should no block the developer's edit/push loop. When the continuous testing is enabled there should be a second copy of the test component that gets updated and the test command is invoked if it is restart true.
Why is this needed?
Odo can be used to offload continuous testing loads to kubernetes based cloud resources.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
