04da81e9a2
`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 <qt_sanity_bot@ovi.com> Reviewed-by: Kalle Lehtonen <kalle.ju.lehtonen@nokia.com> Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
18 lines
249 B
Prolog
18 lines
249 B
Prolog
load(qttest_p4)
|
|
|
|
# do not run benchmarks by default in 'make check'
|
|
CONFIG -= testcase
|
|
|
|
TEMPLATE = app
|
|
TARGET = tst_bench_qsslsocket
|
|
DEPENDPATH += .
|
|
INCLUDEPATH += .
|
|
|
|
QT -= gui
|
|
QT += network
|
|
|
|
CONFIG += release
|
|
|
|
# Input
|
|
SOURCES += tst_qsslsocket.cpp
|