Use github.com/golang/dep as our dependency management tool #5
Comments
|
Dup of #2 |
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 2, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 6, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 14, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 15, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 19, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
ashetty1
added a commit
to ashetty1/odo
that referenced
this issue
Mar 20, 2018
* Pushing this to get some initial feedback on the structure \ of the test cases. * The tests are writting using ginkgo so that it is easier to \ manage the tests going forward * We aren't adhering to the standard requirements of BDD, but \ mapping usecases in ginkgo seems covenient * For starters, we have picked up Usecase redhat-developer#5
cdrage
added a commit
to cdrage/odo
that referenced
this issue
Apr 4, 2018
Adds verbosity to the tests as well as command-line-outout: ```sh ▶ make test-e2e go test github.com/redhat-developer/ocdev/tests/e2e -ginkgo.v $ git clone https://github.com/openshift/nodejs-ex /tmp/ocdev807324634/nodejs-ex Running Suite: ocdev test suite =============================== Random Seed: 1522871416 Will run 9 of 9 specs Usecase redhat-developer#5 ocdev project should create a new project /home/wikus/seafile/files/dev/go/src/github.com/redhat-developer/ocdev/tests/e2e/e2e_test.go:120 $ ocdev project create ocdev-1522871416 New project created and now using project : ocdev-1522871416 $ ocdev project get --short ocdev-1522871416 • ------------------------------ Usecase redhat-developer#5 creating an application when application by the same name doesn't exist should create an application /home/wikus/seafile/files/dev/go/src/github.com/redhat-developer/ocdev/tests/e2e/e2e_test.go:129 $ ocdev application create usecase5 Creating application: usecase5 Switched to application: usecase5 $ ocdev application get --short usecase5 • ------------------------------ Usecase redhat-developer#5 creating an application when application by the same name doesn't exist should be created within the project /home/wikus/seafile/files/dev/go/src/github.com/redhat-developer/ocdev/tests/e2e/e2e_test.go:134 $ ocdev project get --short ocdev-1522871416 ```
cdrage
added a commit
to cdrage/odo
that referenced
this issue
Apr 4, 2018
Adds verbosity to the tests as well as command-line-outout: ```sh ▶ make test-e2e go test github.com/redhat-developer/ocdev/tests/e2e -ginkgo.v $ git clone https://github.com/openshift/nodejs-ex /tmp/ocdev807324634/nodejs-ex Running Suite: ocdev test suite =============================== Random Seed: 1522871416 Will run 9 of 9 specs Usecase redhat-developer#5 ocdev project should create a new project /home/wikus/seafile/files/dev/go/src/github.com/redhat-developer/ocdev/tests/e2e/e2e_test.go:120 $ ocdev project create ocdev-1522871416 New project created and now using project : ocdev-1522871416 $ ocdev project get --short ocdev-1522871416 • ------------------------------ Usecase redhat-developer#5 creating an application when application by the same name doesn't exist should create an application /home/wikus/seafile/files/dev/go/src/github.com/redhat-developer/ocdev/tests/e2e/e2e_test.go:129 $ ocdev application create usecase5 Creating application: usecase5 Switched to application: usecase5 $ ocdev application get --short usecase5 • ------------------------------ Usecase redhat-developer#5 creating an application when application by the same name doesn't exist should be created within the project /home/wikus/seafile/files/dev/go/src/github.com/redhat-developer/ocdev/tests/e2e/e2e_test.go:134 $ ocdev project get --short ocdev-1522871416 ```
johnmcollier
added a commit
to johnmcollier/odo
that referenced
this issue
Sep 5, 2019
Implement the KDO catalog and iterative-dev packs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: