This information is from the code coverage report (see http://coverage.cwgordon.com/coverage).
We need to test:
1) Filtering the dblog messages (and then resetting the filters).
2) Looking at dblog when no messages are present.
3) View details about a log message.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | dblog-filters.test.patch | 3.57 KB | Brigadier |
| #5 | dblog-filters.test.patch | 3.57 KB | Brigadier |
Comments
Comment #1
dmitrig01 commentedMine.
Comment #2
catchRequisitioned.
Comment #3
lilou commentedSee also #298444: DBLog tests exceptions
Comment #4
Brigadier commentedWorking on it.
Comment #5
Brigadier commentedHere's a patch for part 1. It tests filtering with each severity level.
Part 2 was already done at line 390 of dblog.test (message is "DBLog contains 0 records after a clear.")
Part 3 was already done at line 153 of dblog.test (message is "DBLog event node was displayed")
Comment #6
naxoc commentedComment #7
naxoc commentedI took a look and it looks fine. I only have one small thing that I saw was one comment that did not have the first word capitalized: "reset the filter, we should see excluded messages too".
Comment #8
Brigadier commentedThanks, fixed it.
Comment #9
naxoc commentedTook another look and I think it looks good :)
Comment #11
timmillwoodI am getting an issue #445482: Convert dblog_build_filter_query() to DBTNG with a fresh install of core head.
Not sure if this helps or not.
Comment #12
Brigadier commentedYeah, I just did a simplified test case and my unit test is actually detecting a bug in dblog.module. When I use dblog_watchdog() to create a log message with a custom 'type' string, filtering at admin/reports/dblog causes the exception you've described. Now I have to figure out if that bug is actually filed yet.
Comment #13
deekayen commentedI merged this into #445482: Convert dblog_build_filter_query() to DBTNG