Create integration test suites for devfile support

[johnmcollier]

Currently there's no integration test suites for the devfile support in odo. While this isn't much of an issue right now, when there isn't much in terms of devfile support (at this moment, just creating a deployment), as we add more features and as the devfile-mode becomes more complete, this will become a bigger and bigger issue. Additionally, adding integration tests for devfile support will require more work the longer that we delay it (as more and more functionality needs to be tested).

So, we should create integration test suites for odo's devfile support sooner rather than later.

• Create new test suites under tests/integration for the devfile/experimental features in odo
  • Need to add some sample devfiles and projects under tests/examples
• Get the integration tests running in Travis
  • Update the makefile with the new test suites
  • Update the .travis.yml to run those tests
• Get the integration tests running in OpenShift CI
  • @kadel What needs to be done for this step? For Travis it's pretty clear, but I'm not sure how/where to tell the OpenShift CI which tests to run.

/area testing
/area devfile

[openshift-ci-robot]

@johnmcollier: The label(s) area/devfiles cannot be applied, because the repository doesn't have them

In response to this:

Currently there's no integration tests for the devfile support in odo. While this isn't much of an issue right now, when there isn't much in terms of devfile support (at this moment, just creating a deployment), as we add more features and as the devfile-mode becomes more complete, this will become a bigger and bigger issue. Additionally, adding integration tests for devfile support will require more work the longer that we delay it (as more and more functionality needs to be tested).

So, we should create integration test suites for odo's devfile support sooner rather than later.

• Create new test suites under tests/integration for the devfile/experimental features in odo
  • Need to add some sample devfiles and projects under tests/examples
• Get the integration tests running in Travis
  • Update the makefile with the new test suites
  • Update the .travis.yml to run those tests
• Get the integration tests running in OpenShift CI
  • @kadel What needs to be done for this step? For Travis it's pretty clear, but I'm not sure how/where to tell the OpenShift CI which tests to run.

/area testing
/area devfiles

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.

[openshift-ci-robot]

@johnmcollier: The label(s) area/devfiles cannot be applied, because the repository doesn't have them

In response to this:

Currently there's no integration tests for the devfile support in odo. While this isn't much of an issue right now, when there isn't much in terms of devfile support (at this moment, just creating a deployment), as we add more features and as the devfile-mode becomes more complete, this will become a bigger and bigger issue. Additionally, adding integration tests for devfile support will require more work the longer that we delay it (as more and more functionality needs to be tested).

So, we should create integration test suites for odo's devfile support sooner rather than later.

• Create new test suites under tests/integration for the devfile/experimental features in odo
  • Need to add some sample devfiles and projects under tests/examples
• Get the integration tests running in Travis
  • Update the makefile with the new test suites
  • Update the .travis.yml to run those tests
• Get the integration tests running in OpenShift CI
  • @kadel What needs to be done for this step? For Travis it's pretty clear, but I'm not sure how/where to tell the OpenShift CI which tests to run.

/area testing
/area devfiles

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.

[openshift-ci-robot]

@johnmcollier: The label(s) area/devfiles cannot be applied, because the repository doesn't have them

In response to this:

Currently there's no integration test suites for the devfile support in odo. While this isn't much of an issue right now, when there isn't much in terms of devfile support (at this moment, just creating a deployment), as we add more features and as the devfile-mode becomes more complete, this will become a bigger and bigger issue. Additionally, adding integration tests for devfile support will require more work the longer that we delay it (as more and more functionality needs to be tested).

So, we should create integration test suites for odo's devfile support sooner rather than later.

• Create new test suites under tests/integration for the devfile/experimental features in odo
  • Need to add some sample devfiles and projects under tests/examples
• Get the integration tests running in Travis
  • Update the makefile with the new test suites
  • Update the .travis.yml to run those tests
• Get the integration tests running in OpenShift CI
  • @kadel What needs to be done for this step? For Travis it's pretty clear, but I'm not sure how/where to tell the OpenShift CI which tests to run.

/area testing
/area devfiles

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.

[johnmcollier]

I took a crack at writing integration test suites for devfiles (mostly just odo push and syncing) and hit #2684 as a blocker.

[johnmcollier]

My sync PR does the following:

• Adds a —namespace flag to odo push, meaning [Devfile] odo needs to be storing namespace in local env.yaml file #2684 is no longer a blocker for integration tests (though we should still fix [Devfile] odo needs to be storing namespace in local env.yaml file #2684)
• Adds integration tests for devfile push and syncing.

Once my sync PR has been delivered, this issue can be closed out.

[johnmcollier]

/assign

[johnmcollier]

This can be closed out - looks like my PR didn't close it when it was merged