|author||Rohan McGovern <email@example.com>||2011-07-19 09:45:08 +1000|
|committer||Qt by Nokia <firstname.lastname@example.org>||2011-07-19 13:11:37 +0200|
tests: do not run benchmarks by default in 'make check'
`make check' is intended primarily for running functional tests. For the most part, it does not make sense to run benchmarks in the same test environment as the functional tests. Also, the runtime for some of these benchmarks is quite long, and some of them share the same name as existing functional tests. These are problematic. Change-Id: I2ca4cfa24c73280a0b73e51423007eaff92085b8 Reviewed-on: http://codereview.qt.nokia.com/1794 Reviewed-by: Qt Sanity Bot <email@example.com> Reviewed-by: Kalle Lehtonen <firstname.lastname@example.org> Reviewed-by: Rohan McGovern <email@example.com>
Diffstat (limited to 'tests/benchmarks/corelib/kernel/qtimer_vs_qmetaobject')
1 files changed, 4 insertions, 0 deletions
diff --git a/tests/benchmarks/corelib/kernel/qtimer_vs_qmetaobject/qtimer_vs_qmetaobject.pro b/tests/benchmarks/corelib/kernel/qtimer_vs_qmetaobject/qtimer_vs_qmetaobject.pro
index 5ecb94c0f6..24b9bbdcc2 100644
@@ -1,4 +1,8 @@
+# do not run benchmarks by default in 'make check'
+CONFIG -= testcase
TEMPLATE = app
TARGET = qtimer_vs_qmetaobject
DEPENDPATH += .