How do you get test access to privates with the module() function? about busted HOT 5 CLOSED

I am not sure. I think Tieske will need to comment on this as he added the _TEST system I believe.

from busted.

looping in @Tieske

from busted.

will have a look at it, currently travelling and no test system available. Might be a couple of days.

@karlp redesign your modules anyway, as module() has been deprecated in 5.2

from busted.

Just wrote a quick test setup. For a module exporting is done the other way around, always export, delete when not testing;

The module newmod.lua:

module ("newmod", package.seeall)
local privatef = function()
    return 1
end
local list = { "hello", "world" }
publicf = function()
    return privatef() + 1
end
-- export private elements for test purposes
-- in module case revert export:
-- 1) always create test table
test = {
    _privatef = privatef,
    _list = list,
}
-- 2) now remove it when not being tested
if not _TEST then test = nil end

and the testcode;

describe("Testing a module defined using a module keyword", function()
    setup(function()
        require("newmod")
    end)
    it("tests the public function", function()
        assert.is.equal(newmod.publicf(), 2)
    end)
    it("tests the private function", function()
        assert.is.equal(newmod.test._privatef(), 1)
    end)
end)

But be aware; it's intended to test private functions, but due to its nature it works on everything that is passed by reference (functions, tables, etc. but not on numbers or strings, which are passed by value)

HTH

from busted.

Will have a play with that tomorrow. I can't find anything clear about 5.1 to 5.2 migration, so I can only copy the vast amounts of 5.1 code out there that uses module(), sorry.

from busted.