| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Task-number: QTBUG-94148
Change-Id: I7cc0b1ade676c4f7f963915315c00e317582e56f
Reviewed-by: Daniel Smith <Daniel.Smith@qt.io>
|
| |
|
|
|
| |
Change-Id: If91b39f75e2215a4af125a226fa4b82086f3bd46
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
| |
|
|
|
|
|
| |
These are actually treated differently, so it makes sense to test.
Change-Id: Ibeea3e2003f7d425e1aa62bffd0837107cd47d9f
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
|
|
We now have a slightly better setup:
benchmarks/ (root)
auto/ (all benchmarks for regression testing purposes)
changes/ (old changes benchmarks, may be subject to further change)
creation/
... many subdirs, per module or per type in some cases
js/ (old js tests)
manual/ (useful tests that are probably not useful in an automated way)
gputhroughput/ (useful for HW evaluation)
This should let us explicitly run tests that we want to run in an
automated fashion (good), and provides us with a bit more organization
to allow for much more tests without looking like a disorganized mess.
No new tests as yet, but they will come...
Change-Id: I93d04fca84a7f0f10999691ebe0719c80265c852
Reviewed-by: Gunnar Sletta <gunnar@crimson.no>
|
