1.10.2 - 2017-11-30
- Fixed: Should be able to specify package name in syntax test parameter
1.10.1 - 2017-11-23
- Fixed: Workaround sublimehq/sublime_text#2044
1.10.0 - 2017-10-30
- Added #18: Run ColorSchemeUnit when a package name is given
- Added: AppVeyor support
- Fixed: Error running single test
1.9.0 - 2017-10-15
- Added #10: Test output in new tab like BuildView
- Added: Travis CI support
1.8.1 - 2017-10-06
- Fixed: Fallback to hidden-tmLanguage syntax for legacy syntaxes
1.8.0 - 2017-09-25
- Added: Insert Syntax Assertions command
- Added: Allow skipping a test if syntax is not found
- Plugin has been renamed from color_scheme_unit to ColorSchemeUnit
- Fixed: Don't print minimal tests coverage running single test case
- Fixed: Many progress report issues
- Fixed: Several code coverage issues
- Fixed: Several performance issues; more than 50% improvement!
1.7.0 - 2017-09-19
- Added: Insert Assertions command
- Added: Backwards compatability with older builds
<=3083
1.6.0 - 2017-09-12
- Added: Code coverage report
- Added:
build>={NUMBER}
assertion parameter - Added: SQL comment support
1.5.0 - 2017-08-29
- Added: Basic code coverage report
- Added: Performance improvements
- Added: More debug mode messages
1.4.2 - 2017-08-29
- Fixed: Doc: Test support
- Fixed: Update metadata
- Fixed: Update licence year
1.4.1 - 2017-08-27
- Fixed: Can't run single test when package is symlinked
1.4.0 - 2017-08-23
- Fixed: Can't run tests when package is symlinked
-
The default key bindings have been removed, instead add your preferred key bindings:
Menu > Preferences > Key Bindings
[ { "keys": ["ctrl+shift+a"], "command": "color_scheme_unit_test_suite" }, { "keys": ["ctrl+shift+f"], "command": "color_scheme_unit_test_file" }, { "keys": ["ctrl+shift+r"], "command": "color_scheme_unit_test_results" }, { "keys": ["ctrl+shift+alt+p"], "command": "color_scheme_unit_show_scope_name_and_styles" }, ]
The following key bindings remain the same:
Key Description F4
Jump to Next Failure Shift+F4
Jump to Previous Failure
1.3.0 - 2017-06-19
- Added: A percentage indicator has also been added to the end of each progress
- Added: Command "ColorSchemeUnit: Test Results" for opening the test results panel
- Added: Command "ColorSchemeUnit: Show Scope and Colors" for showing the scope name and applied colors of scheme at point under cursor
- Debugging is now enabled via a
color_scheme_unit.debug
setting instead of an environment variable - Debugging messages are now printed in the tests results panel instead of the console
- Copying colors from the "Show Scope and Colors" popup no longer copies the # (hash) character
- Fixed: Several result progress printing issues e.g. progress lines were not wrapping correctly
- Fixed #17: Assertions don't work when prefixed with whitespace
1.2.0 - 2017-06-13
- Auto applying the color scheme when tests are opened is now enabled by default
1.1.0 - 2017-05-17
- Added: Some additional status messages when there are errors
- Added: Debug setting to enable debug messages
- Prepared release
- Fixed #13: Edge case test assertion failures
- Fixed: row:column failure off by 1 row
- Removed #8: Deprecated code
- Fixed #9: IndexError: list index out of range
- Fixed: Show styles popup helper not working
- Deprecated #7: Color scheme tests should use the keyword "COLOR SCHEME TEST" instead of "COLOR TEST"
- Fixed #5: PHP test definition with trailing
?>
does not work - Deprecated #6: Color scheme paths should no longer be prefixed with "Packages/"
- Added: Colors in the Show Scope Name and Styles can now be copied with mouse click
- Changed: Test views are no longer listed in the panel switcher
- Fixed: Keymaps are disabled by default
- Fixed: test output panel syntax tests
- Added: Prints additional runtime information on test runs
- Changed: Run tests timeout uses default
0
- Fixed: Keymaps settings key typo
- Added: allow tests using CSS comments
- Added: Default keymaps (disabled by default)
- Added: Tests are now run in background
- Added: File or Package details is printed in test results output
- Removed: "run_color_scheme_package_tests" command. Use "run_color_scheme_tests" command instead which now runs packages tests.
- Changed: Reworded some run color tests commands
- Changed: "run_color_scheme_tests" command now runs the current package tests by default. Previously it ran all tests including tests from other packages. Color scheme tests are slow and it doesn't make sense to run all test.
- Fixed: Set Color Scheme On Load development helper
- Fixed: allow trailing HTML comment tag on first line i.e.
COLOR TEST ... -->
- Added: improved error handling; prints error information in test results
- Added: allow tests to begin with comments and tags e.g.
<?php // COLOR TEST ...
- Added: ColorSchemeUnit - Run package tests command which only runs current package tests
- Added: test results are now displayed in color
- Added: tests are now run asynchronously
- Added: timer; prints the time it took to run the tests
- Removed
SUBLIME-COLOR-SCHEME-UNIT_DEV_TOOLS
environment variable, useSUBLIME-COLOR-SCHEME-UNIT_DEBUG
instead.
- Fixed: environment debug variable
- Added: assertions can now be written with html style comments
- Fixed: COLOR TEST does not fallback tmLanguage syntaxes
- Fixed: incorrect style when styles have the same score
- Added: run single test command
- Added: run a single test file
- Fixed: assertion fail when a scope inherits from another scope
- Added: debug messages
- Fixed: assertions now work for # comments
- Initial import