c9eb84f2a4
Fix deprecation location reporting in spec runner
2015-01-06 11:50:20 -07:00
aa292874ec
Add reload button to specs window
2014-12-05 15:03:16 -08:00
61651db0b0
Render the deprecations as markdown
2014-11-20 11:41:53 -08:00
b958286d22
Click to expand stack traces
2014-09-26 17:31:09 -07:00
cbe5593381
Do not use "-> return" to mark empty function
2014-08-14 19:42:50 +02:00
32e59ce238
Cleanup code according to coffeelint
2014-08-14 19:41:49 +02:00
3de926a1af
Hide when no deprecations
2014-06-17 11:36:07 -07:00
3601aac136
Correct deprecation label
2014-06-17 11:32:53 -07:00
de8b498402
Add deprecations to spec runner
2014-06-17 11:28:01 -07:00
e99996d5b4
Match backslashes in stack traces on Windows
2014-06-04 09:38:13 -07:00
893493960f
Relativize stack trace paths
2014-02-19 11:12:58 -08:00
26121489be
Trim stack traces
2014-02-19 11:07:02 -08:00
0e60d73b10
Use info alert until suite completes or failure occurs
2014-02-11 16:18:43 -08:00
848d77d3eb
Show 0 failures when all pass
2014-02-11 09:23:12 -08:00
069ead6b1c
Show failure count at end
2014-02-11 09:21:21 -08:00
aef3332a09
Set suite description as text
2014-02-11 09:06:14 -08:00
4bfc0e8ea1
Remove ivars assigned in initialize
2014-02-11 09:06:14 -08:00
c19c4a5e27
Remove unused class
2014-02-11 09:06:13 -08:00
0eb874864c
Remove unused specFilter method
2014-02-11 09:06:13 -08:00
830a8ddc03
Use bootstrap tooltips
2014-02-11 09:06:13 -08:00
d9b14dc492
💄 Use Date.now()
2014-02-11 09:06:13 -08:00
4743cf89dc
Ignore lines after the first jasmine line
2014-02-11 09:06:13 -08:00
b6710b54cf
Add comment about package specs label
2014-02-11 09:06:13 -08:00
d9e4b9d199
Remove redundant spec count
2014-02-11 09:06:13 -08:00
4b2e8f8713
Use fold/unfold octicons
2014-02-11 09:06:13 -08:00
c882d73527
Add it prefix to failure descriptions
2014-02-11 09:06:13 -08:00
fd005380b0
Use package name in label
2014-02-11 09:06:12 -08:00
1c51f512ea
Add symbol-area class
2014-02-11 09:06:12 -08:00
0d724bb00d
Drop colon suffix
2014-02-11 09:06:12 -08:00
8b94fef806
Use alert class for status area
2014-02-11 09:06:12 -08:00
919fafc7a4
Trim stack trace lines
2014-02-11 09:06:12 -08:00
89b240cd4f
Use pre element for stack traces
2014-02-11 09:06:12 -08:00
91bd852812
Use hyphen separated class names
2014-02-11 09:06:12 -08:00
99c2c32e1e
Nest styles
2014-02-11 09:06:12 -08:00
ecf4dbefe3
Sanitize duplicate error and [object Object].<anonymous> lines
2014-02-11 09:06:12 -08:00
cf73dd467a
Pad stack traces
2014-02-11 09:06:11 -08:00
6685464229
Treat spec description as text instead of html
2014-02-10 10:56:56 -08:00
713d7332b3
Update jasmine.js filter pattern
2014-02-07 16:09:43 -08:00
9d51d1a143
Use jquery provided by space-pen
2013-10-16 13:34:41 -07:00
e2ecff22c2
Use underscore-plus instead of underscore
2013-10-15 13:57:34 -07:00
2d55c3e1e9
Set textContent when reporting progress
2013-10-03 09:38:42 -07:00
5cecd533ef
Add back durations to spec reporter
2013-09-25 17:36:21 -07:00
96302e1e0d
Add vendor prefix for jasmine path
2013-09-20 10:02:19 -07:00
68a50b196a
Update spec counts when runner completes
...
This ensures 0/0 is displayed even when no specs were ran.
2013-09-03 14:25:42 -07:00
c8b7040144
🐎 Find elements by id in spec reporter
...
Previously classes containing the spec/suite id were used which
caused major amounts of time finding DOM nodes using class selectors
instead of id selectors.
This decreases the Editor spec from ~90s to ~30s.
2013-08-28 14:56:52 -07:00
41268c67d7
Remove internal packages section from spec reporter
2013-08-14 08:48:12 -07:00
599a2ad021
Group specs into four sections
...
1. Core specs located in spec/
2. Internal package specs in src/packages
3. Bundled package specs in node_modules
4. User package specs in ~/.atom/packages
2013-08-09 17:24:07 -07:00
def07344e9
Visually separate core and package specs in reporter
2013-08-07 09:32:29 -07:00
e34d8e4c42
Display CoffeeScript line numbers in stack traces
...
Use coffeestack to convert stack traces to have CoffeeScript
line and column numbers in the output instead of JavaScript line
and column numbers.
2013-07-06 14:27:16 -07:00
adebae6c47
Remove jasmine.js lines from displayed stack trace
...
This removes the noise from the setup and compare lines that occur in
jasmine.js and only displays the lines that are generated from within
the failing spec.
2013-07-06 14:03:13 -07:00
Nathan Sobo