search

testdouble / teenytest

A very simple, zero-config test runner for Node.js
MIT License
96 stars 14 forks source link

NOT window compatible #24

Closed ghost closed 8 years ago

ghost commented 8 years ago

Hey bro! A new issue! I switched to windows today! Here is my findings, so I quit this code! Sorry bro! Not so awsome code anymore :(

Running test in "test/nested-select-by-test-name-test.js"
Running test in "test/nested-test.js"
Running test in "test/plugin-configuration-test.js"
Uncaught error:
98 == 42
AssertionError: 98 == 42

Uncaught error:
spawn npm ENOENT
Error: spawn npm ENOENT
    at exports._errnoException (util.js:1008:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
    at onErrorNT (internal/child_process.js:348:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
Uncaught error:
spawn npm ENOENT
Error: spawn npm ENOENT
    at exports._errnoException (util.js:1008:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
    at onErrorNT (internal/child_process.js:348:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
Uncaught error:
spawn npm ENOENT
Error: spawn npm ENOENT
    at exports._errnoException (util.js:1008:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
    at onErrorNT (internal/child_process.js:348:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
Uncaught error:
spawn npm ENOENT
Error: spawn npm ENOENT
    at exports._errnoException (util.js:1008:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
    at onErrorNT (internal/child_process.js:348:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
You fail!

How did I trigger this bro_ This isn't valid in Windows

"test:unit": "./test/support/runner.js",

so I tried with

"test:unit": "node test/support/runner.js",

and

"test:unit": "node ./test/support/runner.js",

Neh! More and more I'm testing your code bro, my feelings are crushed :( :( :(

ghost commented 8 years ago

all async tests, and plugin tests fail on windows bro ! :( More failures bro !!

> cd example && ../bin/teenytest test/lib/**/*.js test/lib/multi-word-names.js:10 | grep "1\.\.1"

'..' is not recognized as an internal or external command,
operable program or batch file.

Dude!!! I will wait too see if you are going to make this code user friendly. If not, I\m gone

ghost commented 8 years ago

Hey, bro! You insult me !! I have seen what you have done! And I read your Twitter feed. Say it simple. "Bro" is short for 'brother'. Surprised? I ended up in a car accident a few years ago. I broke my spine and damaged my brain. It was not my fault. A car ran a red light right into the driver's door. Admitted for 9 months.

Today I'm in a wheelchair and suffers from pain. I am much alone with my pain and then I drink a lot :( :( Sorry for that bro!

In the past, I was just like you. Normal brain. Able to walk around on two legs. Smile and laugh. And do programming. I can't anymore :( :( :(

I spend my time in front of my computer. Sometimes I get swallowed up by things. As was the case with your code. I tried to help despite my pain. I was drinking again :( And I'm sorry for that bro!

But then I discovered the lack of human understanding. Without knowing me, you posted on Twitter. And let everyone else have fun. :/ I'm sad bro! Now you know who I am. Maybe not so funny anyway bro?

ghost commented 8 years ago

No worries bro! I did some research on who you are, and next time you have a conference you will know who the man in the wheelchair is bro!! It's me! And I will bring with me medical journal, hospital bills, police report etc.

Back to your code. Any plans to improve it bro?

searls commented 8 years ago

I've opened #26 to add Windows support, which would require get the build working in Windows, that'll force the resolution of all the failures you indicated.

No worries bro! I did some research on who you are, and next time you have a conference you will know who the man in the wheelchair is bro!! It's me! And I will bring with me medical journal, hospital bills, police report etc.

I think this statement can be interpreted as threatening, and don't think it's appropriate here. Closing and locking as a result.