Cleanup test naming - e2e vs integration

[kadel]

There is still a lot of places (like Makefile, or names of Describe blocks) where integration tests are named as e2e or have e2e in the name.
This should be cleaned to make it clear that those are two different tests approaches.

/kind bug
/area testing
/priority medium
/project Sprint 168

[kadel]

/project "Sprint 168"

[dharmit]

Issue description is really clear in this case! For example: https://github.com/openshift/odo/blob/009f9d7e775caef0dc63d2a361f2eeb423398a05/Makefile#L106-L109

has the name test-cmp-e2e but lives under tests/integration directory. There are many such tests with e2e in their name but living under test/integration dir.

[dharmit]

/label state/Ready
/remove-label "state/In Analysis"

[kadel]

/label state/Ready
/remove-label "state/In Analysis"

[dharmit]

The bot's on a PTO, maybe? 🤔

[kadel]

This should be also updated in https://github.com/openshift/release

[amitkrout]

This should be also updated in https://github.com/openshift/release

Right, I will fix all those reference of e2e related to test.

[amitkrout]

Pr sent openshift/release#4268 for OpenShift CI job and config changes

[kadel]

Is there a PR for this on odo side?

[girishramnani]

PR for this issue #1878

[kadel]

/close
#1878

[openshift-ci-robot]

@kadel: Closing this issue.

In response to this:

/close
#1878

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.