tiflash/tests at master · awakeljw/tiflash · GitHub

Name		Name	Last commit message	Last commit date
parent directory ..
delta-merge-test		delta-merge-test
docker		docker
fullstack-test-dt		fullstack-test-dt
fullstack-test		fullstack-test
fullstack-test2		fullstack-test2
sanitize		sanitize
testdata		testdata
tidb-ci		tidb-ci
README.md		README.md
_env.sh		_env.sh
generate-fullstack-test.py		generate-fullstack-test.py
gtest_parallel.py		gtest_parallel.py
run-gtest.sh		run-gtest.sh
run-test.py		run-test.py
run-test.sh		run-test.sh
wait-table.py		wait-table.py

README.md

How to run test cases in local

Deploy a cluster using ti.sh
Use ti.sh x.ti prop to ensure the ports of your cluster
Change the "storage_port", "tidb_port" in ./env.sh to let it connect to your cluster
Run tests with ./run-test.sh fullstack-test/ddl

Instead of ti.sh, you can deploy a cluster with TiUP. But ti.sh is more easy to replace the binary for TiFlash/TiDB/PD, which is convenient for debugging.

For running mock test cases (defined in ./delta-merge-test), you should define a cluster with only one TiFlash node, and set standalone property for that node.
For running intergration test cases (defined in ./fullstack-test, ./fullstack-test-dt, ./new_collation_fullstack), you should define a TiDB cluster with TiFlash node (1 PD, 1 TiKV, 1 TiDB, 1 TiFlash at least).