urbanairship drive.js issues - Githubissues

urbanairship / drive.js

Drive.js makes testing JavaScript applications easy, wherever they live

MIT License

43 stars 6 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Adds deprecation notice

#44 fardog closed 9 years ago
3
don't use this.

#43 AWinterman closed 9 years ago
0
Can't use absolute urls in files under tests

#42 AWinterman opened 9 years ago
0
added some notes

#41 AWinterman closed 9 years ago
0
It's impossible to require a file within an `endpoints` specification

#40 AWinterman opened 9 years ago
1
Drive uses the same http server and host/port pair to communicate between its client and server, and for supporting test endpoints

#39 AWinterman opened 9 years ago
0
Needs tests

#38 AWinterman opened 9 years ago
0
Needs developer docs describing the organizing principles, supported feature set, implementation at a hight level

#37 AWinterman opened 9 years ago
2
added a tentative summary

#36 AWinterman closed 10 years ago
2
bail if you see an error

#35 AWinterman closed 10 years ago
3
Add window.onclick = null to better match real browsers

#34 essdot closed 10 years ago
8
Fix a problem with slowness by reducing speed

#33 chrisdickinson closed 10 years ago
2
defer browserify opt-parsing to browserify

#32 chrisdickinson closed 10 years ago
2
Read browserify transforms from package.json in cwd

#31 jarofghosts closed 10 years ago
2
peg all of the deps; fix for jsdom not pegging its deps

#30 chrisdickinson closed 10 years ago
2
added a workaround for jsdom only giving valid location objects after se...

#29 hayes closed 10 years ago
3
Actual fix for config problem

#28 jarofghosts closed 10 years ago
2
Put config object in a more logical place

#27 jarofghosts closed 10 years ago
3
Fix stack trace befuddlement

#26 jarofghosts closed 11 years ago
2
Write config to test suite rather than using XHR

#25 jarofghosts closed 11 years ago
4
Don't conflict with existing bound ports.

#24 jarofghosts closed 11 years ago
3
Use `stdout` for test output rather than `stderr`

#23 jarofghosts closed 11 years ago
4
Fix issues with previous changes

#22 jarofghosts closed 11 years ago
3
Fix accidental global

#21 jarofghosts closed 11 years ago
4
Adding support for --failfast

#20 jarofghosts closed 11 years ago
3
New docs and version bump

#19 jarofghosts closed 11 years ago
2
Adding TAP output support

#18 jarofghosts closed 11 years ago
3
Fix typo in property name

#17 jarofghosts closed 11 years ago
2
Adding browserify support

#16 jarofghosts closed 11 years ago
9
Add a note specifying that paths are relative to the target files.

#15 AWinterman closed 11 years ago
0
Added a note saying the paths to the target files is relative.

#14 AWinterman closed 11 years ago
0
found the issue

#13 AWinterman closed 11 years ago
0
allow use of requires in endpoints specification

#12 AWinterman closed 11 years ago
0
Add a --failfast flag

#10 chrisdickinson closed 11 years ago
1
Add JSLint/JSHint preprocessing filter

#9 chrisdickinson opened 12 years ago
0
Allow custom preprocessing filters

#8 chrisdickinson opened 12 years ago
0
Statically detect global var leakage

#7 chrisdickinson opened 12 years ago
0
issue requiring a file in a previous directory

#6 narcisoguillen opened 12 years ago
8
We should ignore node_modules

#5 mintchaos closed 12 years ago
1
Default error messages for deepEqual asserts show the json stringification

#4 mintchaos closed 12 years ago
1
Drive deserves some pretty.

#3 mintchaos closed 12 years ago
1
deepEqual error messages should show the objects in question.

#2 mintchaos closed 12 years ago
1
Adding installation instructions. So it's easier to not accidentally...

#1 mintchaos closed 12 years ago
1