Radim Hopp

@apupier Do you think you would be able to contrubute those tests? We can guide you and help you create them ;-) If not, please try to provide more detailed...

https://github.com/eclipse/che/tree/master/e2e/ is the correct place. You can create another spec.ts file for the devfile/stack you want as this one: https://github.com/eclipse/che/blob/master/e2e/tests/e2e/JavaVertx.spec.ts Instructions of how to run the tests are in the...

Seems like to implement this (mostly the last step - `can launch the build task successfully`) we need a running Camel K instance. This is already being discussed in https://github.com/eclipse/che/issues/17015...

Out of curiosity - what's the compute requirements (ram/cpu) for running camel K instance needed for tests?

Validation would be great! Or at least some message in UI about "something went wrong, please look into browser's console". I can confirm, that it works without capital letters.

Showing error response is great add-on. I've tried it and it works great ;-)

On second thought, putting back the protected constructor wouldn't help, because I have to pass to that factory some parameters (specific for each configuration to be able to create the...

Yes they do. So far I've created a workaround in my solution: The SuperSuite is unchanged, under it there is MyParameterized extending Parameterized and under it are MyParameterizedRunners extending BlockJunit4Class....

Yes they do. The "regular" tests in our suite are not using simple BlockJUnit4Class runner, but our own runner (extending BlockJUnit4Class).

We're writing UI tests for eclipse (JBoss Tools/JBoss Developer Studio). We have mechanism called Requirements, which is basically an annotation on class and some code. This Requirement is something I...