What's new in JsTestDriver 1.3.4a
Dec 17, 2014
- Bugs and Fixes:
- fixed the reset on syntax error bug.
- Better error reporting when --preloadFiles is passed in.
- Fixed issue 302 : The parameter --dryRunFor TestCase name does not work properly
- Fixed issue 145 : assets are served with content type "text/plain" (may be missing your exact content type. If so, file a new bug)
- Fixed capturing with more than 50 test cases with --preloadFiles
- Fixed --browserTimeout not being respected with the --browsers flag.
- Features:
- --basePath and base_path now accept multiple base paths.
- News:
- We'll be moving to Git on Google Code in the next two weeks.
- The eclipse plugin is back!
- Finally, it was inevitable, JsTestDriver has a Google plus page
New in JsTestDriver 1.3.3d (Dec 17, 2014)
- Fixed issue 273, Invalid JSON is being sent to the browser with Windows paths
- Improved queuing for simultaneous clients
New in JsTestDriver 1.3.3c (Dec 17, 2014)
- Fixed issue 278, Noisy output when using --captureConsole
- Fixed issue 276, Absolute Paths on Windows fail
- Fixed issue 273, Invalid JSON is being sent to the browser with Windows paths
New in JsTestDriver 1.3.3b (Dec 17, 2014)
- Fixed issue 223 for the last time.
New in JsTestDriver 1.3.3a (Dec 17, 2014)
- New test isolation plugin, documentation forthcoming: issue 272
- Fix for issue 223 , which was real pain without a windows box
- Add test step description to expired callback error messages in the asynch tests.
- Fix issue 234 by failing fast when tests throw exceptions during test steps instead of waiting for all outstanding callbacks to expire.
- Fixes issue 226 by adding HEAD to the HttpMethod enum.
- SSL support to the jstd server, there are some certificate issues.
- Proxy is now a custom Gateway, see documentation for details: http://code.google.com/p/js-test-driver/wiki/Gateway
- Now inlines preloaded files on initial capture or reset. Loading should be faster.
- New --captureAddress flag for to customize the way a browser is captured. (experimental)
New in JsTestDriver 1.3.2 (Dec 17, 2014)
- Fixed issue 199 , starting a browser with the server
- Improved failure handling, now displays multiple errors from AsyncTestCase correctly
- Fixed coverage handling "empty" files
- Fixed multiple path handling issues including the paths used in LOCV files.
- Upon loading the UTF-8 DOM will not be considered data (I hope). Issue 85 related.
- Improved error reporting for relative path resolution in files and plugins.
New in JsTestDriver 1.3.1 (Dec 17, 2014)
- Fixed error reporting for Asynch tests
- Fixed issue 197 , requiring a configuration file to start the server
- Fixed NPE when instrumenting an empty file
New in JsTestDriver 1.3.0 (Dec 17, 2014)
- Increased stability of the server during refreshes and multiple test runs
- Escapes xml result file names to work on Os X, Ubuntu and Windows
- Handling for errors thrown in both the test and the teardown
- Correct formatting for errors in Asynch tests
- Added the "test" attribute to the config file, allowing the separation of tests and dependencies. (See http://code.google.com/p/js-test-driver/source/browse/trunk/JsTestDriver/jsTestDriver.conf for an example)
- Added the "timeout" attribute to the config file, for indicating the total amount of time of a test run. (See http://code.google.com/p/js-test-driver/source/browse/trunk/JsTestDriver/jsTestDriver.conf for an example)
- Added "basepath" attribute to the config file, for declaring the base directory for all file resolutions. (Docs forthcoming.)
- Removed the basepath for inbrowser debugging. (shorter filenames while debugging)
- Fixed issue 159 to speed up server start time
- Upgrade to Gson 1.6
- Fixed dependency ordering on file change: Now, jstd will reload the changed file and all files that are loaded after that file with a persistent server
- fixed issue of losing tests when uploading takes longer than 2 seconds
- issue 145 fixed the mimetype handling
- Browser ids are now unique, no more recapture the browser by accident
- Changed the js execution break to happen between tests, not test suites. Should result in fewer browser panics with heavy tests
- issue 154 , null pointer while running tests
- issue 190 , relative paths are in properly handled (regression introduced between 1.2.2 and 1.3.0)
- Introduced --handlerPathPrefix to prefix all jstd urls on the server with a given prefix
- New proxy feature for running asynch tests against production server. Documentation forthcoming from Robert Dionne
- HTMLDOC now strips html comments due to browser insertion issues
- quit now causes the jstd server to stop (in case you lost the process)
- Asserts patches by Christian Johanson, vastly improved asserts
- Asynchronous testing api now matches documentation
- Lots of internal refactoring and further tweaks to plugin architecture (still very alpha.)