1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
-- Test the menubar
local runner = require("_runner")
local menubar = require("menubar")
local menubar_refreshed = false
local orig_refresh = menubar.refresh
function menubar.refresh(...)
menubar_refreshed = true
orig_refresh(...)
end
-- XXX We are building Lua 5.3 with -DLUA_USE_APICHECK=1 and this catches some
-- bugs in lgi. Thus, do not run this test with Lua 5.3 until lgi is fixed.
-- We run into the same bug when doing code-coverage analysis, supposedly
-- because the additional GC activity means that something which is GC-able when
-- it should not gets collected too early.
-- This test also sporadically errors on LuaJIT ("attempt to call a number
-- value"). This might be a different issue, but still, disable the test.
if _VERSION == "Lua 5.3" or debug.gethook() or jit then --luacheck: globals jit
print("Skipping this test since it would just fail.")
runner.run_steps { function() return true end }
return
end
-- Make sure no error messages for non-existing directories are printed. If the
-- word "error" appears in our output, the test is considered to have failed.
do
local gdebug = require("gears.debug")
local orig_warning = gdebug.print_warning
function gdebug.print_warning(msg)
msg = tostring(msg)
if (not msg:match("/dev/null/.local/share/applications")) and
(not msg:match("No such file or directory")) then
orig_warning(msg)
end
end
end
runner.run_steps {
function(count)
-- Just show the menubar and hide it.
-- TODO: Write a proper test. But for the mean time this is better than
-- nothing (and tells us when errors are thrown).
if count == 1 then
menubar.show()
end
-- Test that the async population of the menubar is done
if menubar_refreshed then
menubar.hide()
awesome.sync()
return true
end
end,
function()
return true
end
}
-- vim: filetype=lua:expandtab:shiftwidth=4:tabstop=8:softtabstop=4:textwidth=80
|
