• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

n1tehawk / luaunit / 223 / 3
100%
nitehawk: 100%

Build:
DEFAULT BRANCH: nitehawk
Ran 22 Apr 2016 04:06PM UTC
Files 1
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

22 Apr 2016 04:03PM UTC coverage: 99.213%. Remained the same
LUA=lua5.3

push

travis-ci

n1tehawk
Allow zero margin again for almostEquals()

Also see the previous discussion at
https://github.com/bluebird75/luaunit/issues/33

I've reconsidered this and come to the conclusion that there
might be valid reasons for using a zero margin parameter with
assertAlmostEquals() or assertNotAlmostEquals(). E.g. if the
user has to deal with rounding errors within our "boost" interval
(EPSILON), but doesn't want (to add) any additional "margin",
then passing 0 actually makes sense.

assertEquals() and assertNotEquals() do not provide an adequate
replacement in that particular case.

1009 of 1017 relevant lines covered (99.21%)

248.62 hits per line

Source Files on job 223.3 (LUA=lua5.3)
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 223
  • Travis Job 223.3
  • 05edc753 on github
  • Prev Job for LUA=lua5.3 on nitehawk (#222.3)
  • Next Job for LUA=lua5.3 on nitehawk (#226.3)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc