aboutsummaryrefslogtreecommitdiffstats
path: root/tests/fuzzy-test/fuzzytester.h
Commit message (Collapse)AuthorAgeFilesLines
* Fuzzy tester: Print error message also for clean build failures.Christian Kandeler2014-04-221-1/+1
| | | | | | | This will help us find false positives (e.g. "disk full"). Change-Id: I5db9d333809f7067dc5dff81544e9e5f0206ee8c Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
* Make fuzzy test more thorough.Christian Kandeler2014-02-281-0/+6
| | | | | | | | "Successful" incremental builds can also be an error, if a clean build fails for the same project. Change-Id: I9f52d840fbda53a906c039e1ee0db2c656db6f8e Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
* Fuzzy test: Do "resolve" and "build" separately for incremental builds.Christian Kandeler2014-02-211-1/+1
| | | | | | | This should increase the likelihood of errors. Change-Id: I9a7b0fded12db05bc55e2f557d220a2614b73d62 Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
* Introduce tool for fuzzy testing.Christian Kandeler2014-02-111-0/+69
Incremental builds are the likeliest source of problems, as well as the one that is the hardest to reproduce. This new tool turns a given project into a quasi-autotest by checking out random commits and doing incremental builds on them. In case of a build error that is not reproducible with a clean build, it aborts and reports the offending sequence of commits. Any qbs project that comes in a git repository is supported. Change-Id: I9f6f9172ce03140341ed25859092a8ed32d4a17d Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>