From bff02d54960b55e16d5c1220719bb86dc1fdd205 Mon Sep 17 00:00:00 2001 From: Noel Grandin Date: Mon, 9 Jul 2018 10:54:36 +0200 Subject: uitests - error if UITEST_TEST_NAME not set to anything useful so the next poor sod who doesn't understand the instructions doesn't waste time with the wrong way of specifying the tests Change-Id: I9759c7f792ec80d660f70f79dc6e2589d44e360f Reviewed-on: https://gerrit.libreoffice.org/57177 Tested-by: Jenkins Reviewed-by: Noel Grandin --- solenv/gbuild/uitest-failed-default.sh | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'solenv/gbuild/uitest-failed-default.sh') diff --git a/solenv/gbuild/uitest-failed-default.sh b/solenv/gbuild/uitest-failed-default.sh index 1aeb8c358b99..c4555d0d069d 100755 --- a/solenv/gbuild/uitest-failed-default.sh +++ b/solenv/gbuild/uitest-failed-default.sh @@ -15,7 +15,10 @@ To rerun just this failed test without all others, use: make UITest_$2 Or to run just a specific test case method, use: - make UITest_$2 UITEST_TEST_NAME="package.ClassName.methodName" + make UITest_$2 UITEST_TEST_NAME="Module.ClassName.methodName" +where + Module - the name of the python file (without the .py extension) + Class - is the name in the "class Class" declaration Or to do interactive debugging, put a long sleep in the beginning of the .py uitest file, and attach gdb to the running soffice process. -- cgit v1.2.3