[GitHub] [camel-k] tadayosi commented on issue #3847: Rethink E2E execution flow

[GitBox <gi...@apache.org>]

tadayosi commented on issue #3847:
URL: https://github.com/apache/camel-k/issues/3847#issuecomment-1328578238

   I am not sure if I understand it correctly, but isn't it exactly what Paul had done a few months back?
   
   After Paul's work, now basically we have two kinds of E2E tests, 1) **global** tests under `e2e/global`, and 2) **namespaced** tests under `e2e/namespace`. The global tests mean that they can run with a single global operator, whereas the namespaced tests mean that they require a dedicated operator per namespace to run for reasons.
   
   So for the global tests, it should already install a global operator *only once per workflow*. The test code still have operator installation steps but if you look into the helper function further you'll see that the installation is skipped when the global test flag is `true`.
   
   For the namespaced tests, they have reasons. It should be still helpful to review them and find possibility to move them to global, though.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org