If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

jssanity is actually insane

RESOLVED FIXED

Status

Testing Graveyard
Mozmill
RESOLVED FIXED
6 years ago
a year ago

People

(Reporter: Jeff Hammel, Unassigned)

Tracking

Details

(Reporter)

Description

6 years ago
https://github.com/mozautomation/mozmill/blob/master/mutt/mutt/tests/js/jssanity.js

You'd think that this would have a pass or two, right?  Instead the
output is:

> mozmill -t mutt/mutt/tests/js/jssanity.js
Xlib:  extension "GLX" missing on display ":0.0".
TEST-START | mutt/mutt/tests/js/jssanity.js | setupModule
TEST-START | mutt/mutt/tests/js/jssanity.js | testSanity
ERROR | Test Failure: {"function": "jum.assertEquals", "comment":
"This should fail", "value2": false, "value1": true}
INFO | Xlib:  extension "GLX" missing on display ":0.0".
INFO | 
INFO | Passed: 0
INFO | Failed: 0
INFO | Skipped: 0

While this doesn't cause mutt to fail, it should probably be fixed.
(Reporter)

Comment 1

6 years ago
From irc:

10:18 <@ctalbert> jssanity was old
10:18 <@ctalbert> it was for mutt itself as I recall
10:18 <@ctalbert> since it pre-dates the assertions module the way it does it 
                  is likely wrong
10:18 < jhammel> ctalbert: mv -> /dev/null ?
10:20 <@ctalbert> sure, it's just to make sure htat mutt was working when I 
                  first wrote it
10:20 < jhammel> ctalbert: coolz, will do

So I will remove this
(Reporter)

Comment 2

6 years ago
pushed to master: https://github.com/mozautomation/mozmill/commit/267e69817d2aa6ea1a90f927c95ea8f7c57025dd
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

a year ago
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.