| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Certain benchmarks that referred to private
headers are removed from the list of 'trusted'
benchmarks.
Benchmarks referring to private headers are considered
bad practice for several reasons:
1) Such tests won't even build if private headers
are not avaiable in the installed version of Qt.
2) APIs should be designed well enough to be fully
testable through its public headers only.
Change-Id: Iccd81e12829a7b7f4bd2b88a72f3e9722520f6e2
Reviewed-by: Rohan McGovern
|
| |
|
|
| |
Reviewed-by: Sergio Ahumada
|
| |
|
|
| |
Reviewed-by: Joao
|
| |
|
|
|
|
|
|
|
|
| |
Reuse the ByteArray implementation from
examples/script/customclass and create a benchmark out of it.
This benchmark actually measures a meaningful, real-world
use case for QScriptClass.
Task-number: QTBUG-17192
Reviewed-by: Jedrzej Nowacki
|
| |
|
|
|
|
|
|
|
|
| |
Reuse the Context2D implementation from
examples/script/context2d and create a benchmark out of it.
This benchmark actually measures a meaningful, real-world
use case.
Task-number: QTBUG-17192
Reviewed-by: Jedrzej Nowacki
|
| |
|
|
|
|
|
| |
For some reasons script.pro file was missing a few benchmarks.
QScriptValueIterator benchmark didn't follow naming rules.
Reviewed-by: Olivier Goffart
|
| | |
|
| |
|
|
|
|
|
|
|
| |
To run the list of trusted benchmark do 'make check-trusted' in
either the root benchmarks directory or for any of the immediate
sub-targets. Normal 'make check' environment variables apply,
such as TESTRUNNER and TESTARGS.
Reviewed-by: João Abecasis <joao.abecasis@nokia.com>
|
|
|
We follow the same structure as used in the src directory. This makes it
easier to navigate through the jungel, especially now that we are going
to add functional tests etc.
|
