mirroar/wowunit

A unit testing framework to test AddOns from within World of Warcraft

Hi there 👋

wowunit's Issues

2 very small patches

• Make the testframe a bit bigger for those really long messages

File name: frame.lua
http://www.2shared.com/file/RQU261xE/framelua20110917.html

• Bring a little more clarity to the asynch event

File name: README.md
http://www.2shared.com/file/wFxahqQb/READMEmd20110917.html

Feature request: When failing a test, return the value returned

To illustrate here is some code:

-- in file: Core.lua
function addon_obj:to_be_tested(name)
      if name == "TEST" then
             return "TEST"
      else
             return nil
      end
end

-- in file: test_suite.lua
wowUnit:assert(addon_obj:to_be_tested("TEST"),"Will succeed")
wowUnit:assert(addon_obj:to_be_tested("BLAH"),"This should now display (in frame.lua) this text +"..the_returned_variable)

I looked through the code, but wasn't all clear to me :)

Test ordering patch + the 2 mini patches

http://www.2shared.com/file/stR15Nh-/wowUnit.html

That link contains the following changes:

Core.lua

• Categories and subcategories test ordering [The code sitting at the top of core.lua should be put in a diff file, loaded from the .toc first. My addons all sport usefull_functions.lua that contain improvements to LUA)
• Made the test window bigger [TODO: Resizable window...]

Readme.md

• More commenting on the Sample code

Added: assertNonEquals() i.e. value1 ~= value2

Hi,

• assertNonEquals() added to asserts.lua.
• Documentation updated.

Patches from Issue #3 included.

Cheers,
Alex

The whole package: http://www.2shared.com/file/S1esfOob/wowUnit.html

Tests ordering,simple asynch timebased tests, AceEvents and repeating tests.

Hey,
I just wanted to say big thanks for this, it is very valuable for me! :D

Now to business (feature requests):

1. I noticed you do pairs when iterating test categories and sub categories. All tests need more order! :D
2. A simpler way to do Asynchronous Testing. Something like wowUnit:asynch(function() end,function() end,<time interval say 5 secs>) should suffice.
3. More documentation is needed, like how do I do asynch testing on AceEvents?
4. A way to repeat the tests X amount of times, so that I can see if something goes broke after running the tests a few time.

Thats all I have for now, I will try to send you some code when I can muster up the spirit to make a mess of other peoples code.

Thanks yet again, and sorry for the lengthy post,
Fulg