Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QUnit.log outputs HTML, but it shouldn't #32

Closed
NV opened this issue Sep 1, 2010 · 3 comments
Closed

QUnit.log outputs HTML, but it shouldn't #32

NV opened this issue Sep 1, 2010 · 3 comments

Comments

@NV
Copy link
Contributor

NV commented Sep 1, 2010

QUnit.log = function(a, msg){
  console.log(msg)
}

test("some test", function(){
  equals(1, 2);
});

Console:

<span class="test-message">undefined</span>, expected: <span class="test-expected">2</span> result: <span class="test-actual">1</span>, diff: <del>2 </del><ins>1 </ins>

I'm using qunit-tap and it outputs HTML into terminal.

@FND
Copy link

FND commented Sep 4, 2010

I've had similar issues with Kopfloss, where I ended up using some hacky string replacements to get rid of that markup.
I agree it would be nice if that wasn't necessary.

@benjaminplee
Copy link
Contributor

I agree. I am working on refactoring out the output formatting to a separate object so that a new one for Ant/JUnit style output (or whatever flavor) can easily be created.

@jzaefferer
Copy link
Member

Pass raw data (result, message, actual, expected) as third argument to QUnit.log. Closed by c2cde34

mgol pushed a commit to mgol/qunit that referenced this issue Mar 24, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants