You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, integration tests depend on a version of CDAP, and always get the application class from that version, and deploy it using the deploy(Class appClassz) method. However, this means that even if you are testing on a cluster with a different version of CDAP than the version that cdap-integration-tests is built with, you will still end up testing a version of the app that was cdap-integration-tests was built with.
The text was updated successfully, but these errors were encountered:
We can achieve this with branching. So there is a workaround between releases. However, this feature would still be a nice-to-have for instances when you have to modify an app to test something out without pushing it to snapshots/local repo.
Currently, integration tests depend on a version of CDAP, and always get the application class from that version, and deploy it using the
deploy(Class appClassz)
method. However, this means that even if you are testing on a cluster with a different version of CDAP than the version that cdap-integration-tests is built with, you will still end up testing a version of the app that was cdap-integration-tests was built with.The text was updated successfully, but these errors were encountered: