f16ea63a95
Export ReactEditorView as EditorView from 'atom' module
...
Also, remove a few early requires of 'exports/atom.coffee' in the spec
suite that were causing failures.
2014-07-21 10:43:30 -07:00
f97db691c3
Add back core spec require
...
This was accidentally deleted in #2462
2014-06-03 17:26:02 -07:00
1704c78eea
Enable core specs when run outside of clone repo
...
The failing specs have been updated so that specs
can now run without the requirement of a Git repository
at the root.
2014-06-02 10:17:13 -07:00
f2e5b480e1
Fix specs on Mac.
2014-03-18 16:32:34 +08:00
8bf1464b64
Fix setting NODE_PATH in specs window.
2014-03-18 15:57:16 +08:00
d6433a67c8
Incluse JavaScript specs when loading suite
...
Closes #1615
2014-03-11 13:01:28 -07:00
1131952a54
Remove stray unicode char
2014-02-23 17:11:38 -08:00
189ebc4476
Remove _/fs from modules directly
2014-02-23 17:09:05 -08:00
2f46fee1ca
Use resource path from load settings
2013-11-21 16:08:27 -08:00
568aa1d396
Remove some package manager shims on atom global
2013-11-20 12:48:05 -08:00
389b2bd8d6
Remove spec suite measuring.
...
This may be a bit aggressive, so we can add it back if people think it
has benifits.
2013-11-14 09:03:58 -08:00
ec37b8abd9
💄 Add helper to set spec field on all specs
2013-10-14 11:22:34 -07:00
0b22d99fad
Store spec directory on required specs
...
This allows the project to be configured based on the spec being
run.
2013-10-14 11:15:40 -07:00
d46891caf0
Rename atom-api require to atom
2013-09-20 10:03:02 -07:00
88ccafa164
Use path.join for fixtures packages path
2013-09-20 10:03:01 -07:00
3c94ca4b9e
Use relative paths in spec requires
2013-09-20 10:02:20 -07:00
c7a0a4bcd9
Use relative require paths in specs
2013-09-20 10:02:19 -07:00
2152004883
Use the ACTUAL spec directory instead of the specs parent
2013-09-13 09:01:22 -07:00
e64119ade2
Rename specPath loadSetting to specDirectory
2013-09-13 09:01:22 -07:00
f9e95c273f
Only run core specs when resource path is the Atom repo
2013-09-03 14:25:42 -07:00
78b9a99f86
Add window:run-package-specs command
...
This will only run specs found in the current projects spec directory
2013-08-23 09:02:22 -07:00
3d5516fad9
Default to empty arrays for user and bundled package paths
2013-08-16 20:52:20 -07:00
fe2baa18ca
Use atom.getAvailablePackageNames() to load package specs
2013-08-16 11:35:43 -07:00
2f4555a16f
Add config.userPackageDirPaths which includes dev packages in dev mode
2013-08-16 11:18:08 -07:00
ad36b2c6a6
Allow user package specs to override bundled package specs
2013-08-14 15:36:45 -07:00
5235114eed
Use fs.readdirSync() for listing package directories
...
Previously fsUtils.listTreeSync() was used which returns every path
in the tree, not just paths directly underneath the root path.
This speeds up the spec suite require time by not stat'ing the entire
node_modules directory.
2013-08-14 11:29:48 -07:00
b7a8e22d82
Set spec type after all specs in the category are required
2013-08-14 10:58:56 -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
d77705a039
Rename listTree() to listTreeSync()
2013-06-12 18:26:44 -07:00
27d9da15dc
Rename list() to listSync()
2013-06-12 18:25:42 -07:00
82013b1970
Use path.join() instead of fsUtils.join()
2013-06-12 16:20:40 -07:00
f03b6207de
Make all requires of 'fs-utils' assign to fsUtils var instead of fs
2013-04-03 12:01:37 -06:00
875fbba024
Measure spec suite require time
2013-03-15 09:09:56 -06:00
96a949983c
Use fs.resolveOnLoadPath() instead of require.resolve()
2013-03-12 13:33:25 -07:00
1d1ba5f6d1
Use node's require instead of internal require
2013-03-12 10:38:05 -07:00
7ff0450379
Don't recurse into packageDirPaths to look for packagePaths
2013-02-13 10:42:22 -08:00
80c506340f
Run specs from all package directory paths
2013-01-10 15:31:18 -08:00
4896302f7e
Run specs for src/packages, not src/extensions
2012-12-18 20:32:24 -07:00
cee3372a87
Look for extension specs in src/extension (more specific) and run the second
2012-10-26 12:25:20 -06:00
2af29c9934
Extensions have a src and specs directory now. Move existing extension specs.
...
Move the extensions spec code inside of the extension's spec directory. Move source code to the extension's src directory
2012-10-25 11:48:13 -07:00
85c37fd652
Move atom.resourcePath to window.resourcePath
...
The resourcePath is now set using a url param. Because resourcePath is needed by require.js, it needs to be on `window` rather than `atom`.
2012-09-10 17:22:21 -07:00
12b06ddf0c
Get spec suite running (lots of failures)
2012-08-27 17:36:36 -05:00
c2c8724ad0
Initial commit
2012-08-10 13:32:19 -06:00
b37b45b4b1
atom variable holds all global state and is shared across contexts.
2012-02-28 13:14:35 -08:00
8cbf4331e4
Remove references to OSX from fs.coffee and make fs specs pass.
2012-02-27 11:38:25 -08:00
b99c4deb49
Fix path to specs. Now spec-suite runs.
2012-02-22 15:08:19 -08:00
c75c3555bb
Meta+s triggers save on Editor.
...
Still can't save buffers that don't have a url.
2011-12-16 16:30:51 -08:00
4ce635d539
Always assign the app to a global in specs console.
2011-12-15 19:11:20 -08:00
Nathan Sobo