Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

tests fail

See original GitHub issue

this happens after a fresh npm install:

$ npm test

> morphdom@1.3.0 test /Users/julian/dev/juliangruber/morphdom
> npm run test-browser && npm run lint


> morphdom@1.3.0 test-browser /Users/julian/dev/juliangruber/morphdom
> node test/mocha-phantomjs/run.js test

Preparing client-side tests...
Config: { runBenchmarks: false, runTests: true }
/Users/julian/dev/juliangruber/morphdom/test/mocha-phantomjs/test-page.marko.js:13
    lasso_page({
    ^

TypeError: lasso_page is not a function
    at render (/Users/julian/dev/juliangruber/morphdom/test/mocha-phantomjs/test-page.marko.js:13:5)
    at Object.Template.render (/Users/julian/dev/juliangruber/morphdom/node_modules/marko/runtime/marko-runtime.js:192:9)
    at Object.Template.(anonymous function) [as render] (/Users/julian/dev/juliangruber/morphdom/node_modules/marko/hot-reload/index.js:84:34)
    at run (/Users/julian/dev/juliangruber/morphdom/test/mocha-phantomjs/run.js:107:18)
    at Object.<anonymous> (/Users/julian/dev/juliangruber/morphdom/test/mocha-phantomjs/run.js:135:1)
    at Module._compile (module.js:397:26)
    at Object.Module._extensions..js (module.js:404:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:429:10)

Issue Analytics

State:
Created 7 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

patrick-steele-idemcommented, May 25, 2016

I meant to check in a fix for this, but ran out of time. I will restore the tests first thing tomorrow.

0reactions

patrick-steele-idemcommented, May 25, 2016

NOTE: You will need Node.js v4+ to run the tests now

Top Results From Across the Web

What To Do When Tests Fail? - TestProject

Tests usually fail due to server and network issues, an unresponsive application or validation failure, or scripting issues. When failures occur ...

Foresight Blog | Why Are Your Tests Failing?

One reason tests fail is that they depend on uncontrolled contexts. For instance, integration tests could fail due to a lost connection with...

Debugging Failing Tests and Test Pipelines - GitLab

These guidelines are intended to help you to investigate end-to-end test pipeline failures so that they can be properly addressed. This will involve...

How to Fix Flaky Tests - Semaphore CI

Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....

Write Tests That Fail - Ranorex

An entirely different kind of test failure is a unit test confirming that an implementation correctly handles an error. Test frameworks ...