coLunacyDNS tests cover line 1740,1741 of coLunacyDNS.c. Ocverage: 98.71%
coLunacyDNS: Added test for line 1728 of coLunacyDNS.c. Coverage: 98.51%
coLunacyDNS expand sqa_gCovNoOpenDNS test; coverage now at 98.41%
Added sqa_gCovNoOpenDNS test for coLunacyDNS; coverage at 97.92%
coLunacyDNS sqa: Added sqa_badQueryName test, coverage at 97.31%
coLunacyDNS sqa: add sqa_badQueryID test; coverage: 97.11%
coLunacyDNS sqa: Also run maradns with sqa_comppointer
May as well use this part of the test too.
Update sqa_comppointer to reach second comp. pointer test
It took an artifical DNS packet to reach this point, but coLunacyDNS
handles it just fine.
Test coverage: 97.01%
coLunacyDNS sqa: Another code block removed from sqa coverage: 96.51%
I explain in README.md why we do not cover a block of code in
human2DNS (we will never reach it, but I would rather have the
check just in case something I do not see would reach it)
coLunacyDNS: Add code which is not part of the test coverage
* `human2DNS` has a sanity check which will never pass. I will keep this
check in production code just in case some corner case I haven’t thought
of triggers it.
coLunacyDNS bugfix: Return error if we return invalid IPv4
If processQuery() returns a table with an invalid IPv4 address,
instead of giving the client the 255.255.255.255 IPv4 address,
we now do not respond, and log an error that we were given a
Test added for this.
coLunacyDNS sqa: sqa_postanswer has more coverage: 96.02%
coLunacyDNS sqa: Added coverage to sqa_postanswer, now at 95.83%
coLunacyDNS sqa: Add tests for coDNS.solve behavior. Coverage: 95.53%
We run a different branch of code when we handle coDNS.solve() errors
*after* we get our first answer from coDNS.solve(), so we need
coLunacyDNS: Consolidate “Roy Arends” with other sanity tests
This way, we are able to test all of the code runs as planned with
just the “Roy Arends” check.
Test coverage: 93.74%
coLunacyDNS sqa: Update “Roy Arends” test to have IPv6
coLunacyDNS sqa: Begin work on “Roy Arends” check
sqa_badanswer: Test for no table returned by processQuery
This means we now test for all possible processQuery results which
return bad values. Test coverage: 92.97%
coLunacyDNS: Give error messages for bad processQuery return values
Also: Make sure we do not send both an invalid IPv4 and IPv6 answer
when they request an IPv6 answer with processQuery
coLunacyDNS sqa: No need to have gcov artifacts for Lua
I tried adding Lua gcov artifacts to see if that would fix the
issue with gcov not correctly reporting lines. The actual issue is
that SIGTERM caused the coLunacyDNS process to abort without updating
its gcov stats.
coLunacyDNS: Ignore gcov artifacts