🌱 Remove integration tests from Hub repo (#419)

Integration E2E tests using API are now in
https://github.com/konveyor/go-konveyor-tests those are executed using
global CI workflows.

Related to:
- #310
- #418

Signed-off-by: Marek Aufart <[email protected]>

Author: aufi

Makefile

@@ -131,12 +131,8 @@ test:
 test-api:
 	HUB_BASE_URL=${HUB_BASE_URL} go test -count=1 -v ./test/api/...
 
-# Run Hub API integration tests.
-test-integration:
-	HUB_BASE_URL=${HUB_BASE_URL} go test -count=1 -v ./test/integration/...
-
 # Run Hub test suite.
-test-all: test-unit test-api test-integration
+test-all: test-unit test-api
 
 migration:
 	hack/next-migration.sh

test/README.md

@@ -3,18 +3,18 @@
 Hub tests consist of following parts:
 - Unit tests ```$ make test```
 - REST API tests ```$ make test-api```
-- Integration tests ```$ make test-integration```
-- WIP Export/import tests
 
 All tests can be executed with ```$ make test-all``` which will run all available tests.
 
+For API E2E / integration tests, refer to https://github.com/konveyor/go-konveyor-tests
+
 ## General information
 
 - Tests are written in golang to fit well to the Konveyor project components.
 - Each test is responsible for setup its test data and clean it when finished.
 - The main way of interacting with Hub is its API, to make testing easier, following tools are provided:
   - ```RichClient``` from [binding](https://github.com/konveyor/tackle2-hub/tree/main/binding) package that provides methods working with Hub resources (like ```RichClient.Application.Create(&testApp)```). This is a preffered option.
-  - ```addon.Client``` provides API methods like Get/Post/etc. it can be accessed from ```RichClient.Client()```
+  - ```addon.Client``` provides API methods like Get/Post/etc. it can be accessed from ```RichClient.Client```
   - ```test/assertion``` package provides Should/Must and other equality assertions.
   - Hub's ```API``` package provides predefined routes and resources struct definition.