- Jul 29, 2021
-
-
Tomas Krizek authored
-
-
- Dec 08, 2020
-
-
- Oct 26, 2020
-
-
- Jul 08, 2020
-
-
Petr Špaček authored
-
Petr Špaček authored
Old behavior where test definition without "return" was silently skipped was very confusing.
-
Petr Špaček authored
It was only generating noise in test logs, especially when network is not abvailable/is intentionally disabled.
-
- Feb 25, 2020
-
-
These files did not have GNU GPL v3 boilderplate in them so I've added machine readable tag with appropriate license.
-
- Apr 18, 2019
-
-
Petr Špaček authored
Output buffering in tests made debugging much harder because crash in middle of operation discarded while buffer and left us without a trace what was going on.
-
- Mar 12, 2019
-
-
Tomas Krizek authored
-
- Jan 08, 2018
-
-
Marek Vavruša authored
-
- Dec 23, 2017
-
-
Petr Špaček authored
We run tests in paralell so have to make sure that coverage tools do not overwrite results from each run. This is hacky because lcov tool insists on having gcno and gcda files in the same place as original source, so we have to copy files to workaround this.
-
Petr Špaček authored
Luacov statistics contained paths to installed files instead of source files that it was a mess. The stats are now rewritten using hacky mapping (created from install commands produced by make). Also, branch and function coverage for Lua was always zero so now it is turned off not to confuse users. kresd config for respdiff now enables luacov as well.
-
- Dec 21, 2017
-
-
Marek Vavruša authored
also disabled priming and TA signalisation during tests
-
Marek Vavruša authored
-
Marek Vavruša authored
This leverages the HTTP interface to trace execution of individual requests. This is helpful for troubleshooting problems with a specific instance, or to generate test files (as it writes out answers received). Ideally it would also print a timeline of request processing broken down by function (or layer) and the amount of time spent, but there's no tracepoint for that yet.
-
- Nov 28, 2017
-
-
I moved the test files to module directories because it allows vendoring of whole modules including tests etc. The test environment provides convenience functions and produces test output in TAP format. Ideally all tests should use a common format, so that CI can parse it provide better test output on PRs. It seems like Gitlab CI doesn't support anything yet, but there are two sort-of standards supported in CI tools - TAP and JUnit. I chose TAP because it's easier to read for humans, cmocka supports it, and it should be easier to adapt Deckard. There are also tools to convert TAP into JUnit XML file. Also added more tests for global functions and variables, and the test tool now also tracks coverage (if `luacov` is installed).
-