Here is a copy of part of our internal wiki on how to run tests:
You can then run the front-end tests with
cd fe; mvn -fae test; cd ..
This can be narrowed by passing mvn arguments specifying which test class
or test method you want to run, like
mvn -fae test -Dtest=AnalyzeStmtsTest
mvn -fae test -Dtest=AnalyzeStmtsTest#TestStar
You can run the backend tests with
# The Impala cluster must not be running for the backend tests
./bin/start-impala-cluster.py --kill
./bin/run-backend-tests.sh
# or
ctest
As in the frontend tests, you can specify which test you want to run:
ctest --output-on-failure -R expr-test # also shows what broke, if anything
To only build the backend test run:
make be-test
You can run the end-to-end tests with
./tests/run-tests.py
Or run a specific one with
./tests/run-tests.py metadata # Run all the tests in a directory
./tests/run-tests.py metadata -k test_partition_metadata_compatibility #
Run only the test with a particular nam
On Mon, Mar 28, 2016 at 9:35 PM, Nishidha Panpaliya
wrote:
>
>
> Hi All,
>
> I again need your help in understanding Impala tests to be run and ensured
> and their estimates.
>
> Last time, I know you had given way to run only backend tests and it was
> helpful to us. I've also gone through run-all-tests.sh which triggers
> backend test, frontend test, end-to-end tests, etc. Could you provide me
> individual commands to run each of them and if any setup steps are
> required? Also, I would like to know if there are any specific system
> requirements that I must have up-front to run all these tests.
>
> Along with these commands/scripts, I'm also interested in knowing how much
> time each of these tests take to run, if we do not run into any issues.
> This is required to know the guess estimate of how long will this activity
> be taking from now.
>
> Thanks in advance,
> Nishidha
>
>
