diff --git a/Makefile b/Makefile
index 919aadcb74..d7903a9cc3 100644
--- a/Makefile
+++ b/Makefile
@@ -445,7 +445,9 @@ test-full:
 test-full-386:
 	GOEXPERIMENT=synctest GOARCH=386 go test -coverprofile=coverage.txt -covermode=atomic ./lib/... ./app/...
 
-integration-test: victoria-metrics vmagent vmalert vmauth vmctl vmbackup vmrestore
+integration-test: apptest
+
+apptest: victoria-metrics vmagent vmalert vmauth vmctl vmbackup vmrestore
 	go test ./apptest/... -skip="^TestCluster.*"
 
 benchmark:
diff --git a/apptest/README.md b/apptest/README.md
index f4a50428ff..1c6bd1a2ab 100644
--- a/apptest/README.md
+++ b/apptest/README.md
@@ -33,7 +33,7 @@ For example, `sharding_test.go` aims at testing data sharding.
 
 Since integration tests start applications in a separate process, they require
 the application binary files to be built and put into the `bin` directory. The
-build rule used for running integration tests, `make integration-test`,
+build rule used for running integration tests, `make apptest`,
 accounts for that, it builds all application binaries before running the tests.
 But if you want to run the tests without `make`, i.e. by executing
 `go test ./app/apptest`, you will need to build the binaries first (for example,