diff options
author | Rohan McGovern <rohan.mcgovern@nokia.com> | 2010-03-19 05:27:10 (GMT) |
---|---|---|
committer | Rohan McGovern <rohan.mcgovern@nokia.com> | 2010-03-22 00:27:37 (GMT) |
commit | 7a7dbde042b380f3005deb1c1e72e876eaa57d4c (patch) | |
tree | 621a953cfb1af01d450ecc561d1606be74e9b423 /tests/auto/qfiledialog2 | |
parent | 3f2485e98ff52505d9277459b0b0403c26fb165f (diff) | |
download | Qt-7a7dbde042b380f3005deb1c1e72e876eaa57d4c.zip Qt-7a7dbde042b380f3005deb1c1e72e876eaa57d4c.tar.gz Qt-7a7dbde042b380f3005deb1c1e72e876eaa57d4c.tar.bz2 |
Add a selftest to enforce correct test naming conventions.
When a test runs successfully, it outputs an XML test log, with the
testcase name coming from whatever class is passed to QTest::qExec.
If a test crashes, hangs, fails to compile, or otherwise fails to output
a valid test log, any summary of the test results still has to display
some reasonable testcase name. But we can't tell what the testcase name
_would_ have been had the test run correctly - without, for example,
attempting to parse the C++.
The simplest solution is to make sure that TARGET and the test class
name are always matching. This test will force people to follow this
naming convention.
Diffstat (limited to 'tests/auto/qfiledialog2')
0 files changed, 0 insertions, 0 deletions