Sergio Ahumada 31d6ac1386 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. Change-Id: I33b2cf1e833fc6b1d0b3525018945148ba2d3492 Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>		2011-10-24 09:36:58 +02:00
..
containers-associative	tests: do not run benchmarks by default in 'make check'	2011-07-19 13:11:37 +02:00
containers-sequential	Remove Symbian-specific code from tests.	2011-09-29 06:41:42 +02:00
qbytearray	Remove Symbian-specific code from tests.	2011-09-29 06:41:42 +02:00
qchar	Add benchmark for QChar	2011-09-15 20:39:28 +02:00
qhash	tests: do not run benchmarks by default in 'make check'	2011-07-19 13:11:37 +02:00
qlist	tests: do not run benchmarks by default in 'make check'	2011-10-24 09:36:58 +02:00
qrect	tests: do not run benchmarks by default in 'make check'	2011-07-19 13:11:37 +02:00
qregexp	tests: do not run benchmarks by default in 'make check'	2011-07-19 13:11:37 +02:00
qstring	Remove Symbian-specific code from tests.	2011-09-29 06:41:42 +02:00
qstringbuilder	tests: do not run benchmarks by default in 'make check'	2011-07-19 13:11:37 +02:00
qstringlist	Remove Symbian-specific code from tests.	2011-09-29 06:41:42 +02:00
qvector	tests: do not run benchmarks by default in 'make check'	2011-07-19 13:11:37 +02:00
tools.pro	optimize QList::removeAll()	2011-09-12 16:03:47 +02:00