- Removes velocity:source-map-support dependency It breaks file links in Chrome for stack traces.
- Improves mirror caching
- New mirrors now get the complete hot cache of the app. -> Same start speed for mirrors as for the already cached app.
- Mirrors are cached in .meteor/local/mirrors.
-> Mirrors never need to be built from scratch after the first start.
This is also nice for CI mirror caching.
Just cache
.meteor/local/mirrors, and you get cached mirrors on CI.
- Update for Meteor 1.2.1
- Adds extra logging to mirror starting
- Adds Velocity.startup to mirrors
- Fixes debugging with Webstorm
- Removes deprecated CI logic
- Runs mirror with --once flag on CI
- Performance improvements
- A way to specify a different Meteor release for mirrors See: https://velocity.readme.io/v1.0/docs/use-with-older-meteor-release
- Use Meteor 1.2.0.2 for mirrors
- Compatibility with Meteor 1.2
- Reverts breaking change from velocity:METEOR (.meteor/packages file was no longer available in the mirror folder)
- Updates Velocity Meteor command line tool and some packages. This fixes some edge case issues and improves error logging in CI.
- Source maps support for server stack traces
- Source maps support for client stack traces
- Support for remote databases and multiple apps running at the same time (Documentation)
- Added Function.bind polyfill for PhantomJS
- Parallel execution support
- Fix for windows paths
- Don't print errors when a test frameworks hasn't implemented the experimental lifecycle hooks.
- Unblock longer running Velocity method calls for improved performance.
- Fixes performance issue when you have node_modules in your tests folder.
- Use velocity:METEOR@1.1.0.2_3 to spawn mirrors.
- Remove terminated mirrors from previous runs.
Fixes that
meteor --testis not exiting after first run.
- Support for Windows
- Improved mirrors
- Debugging mirrors
Make sure you read https://github.com/meteor-velocity/velocity/wiki/Changes-in-0.6.0.
- Prototype of testing lifecycle (run, reset, etc.)
- First cut of distributable support
- Removed default port of 5000 for mirrors and replaced with freeport.
- Fixed client side error with VELOCITY enabling
- Mirror initializing and being ready are now part of the explicit logs so that users are aware of the existence of mirrors.
- Removed mirrorId and replaced with framework name. If frameworks wish to use multiple mirrors, they can manage this themselves
- Fixed mirror killing mechanism in node-soft-mirror by removing idomptency logic into mirror implementation
- Increased logging around mirror start/ready
- Fixes connection errors with old mirrors (#195)
- Adds missing checks to pass audit-argument-checks
- decoupled mirrors
- added Velocity.startup
- Decoupled mirrors from the core so now mirrors can be authored as packages
- Updated chokidar and now file watching only synced once
- Makes FileCopier more robust
- temporarily move off of rc track while issue meteor/meteor#3147 is resolved
- Decoupled mirrors from the core so now mirrors can be authored as packages
- Updated chokidar and now file watching only synced once
??
- Fixed bug in de-bouncing rsync
- Added NPM shrink
- Bumped npm dependency versions for chokadir, glob and freeport
- Increased mirror logging
- Mirror output is now visible by default
- Mirrors now use DDP to notify frameworks of up-ness
- Fixed mirror dying on server restarts (YAY!)
???
- Updated to use Meteor 1.0
- mirror is disabled by default
- Rewrite mirroring approach
- Mirrors no longer startup by default and have to be requested by frameworks using requestMirror
- requestMirror now checks for existing mirrors by port and reuses them if they already exist
- velocityMirrors can contain multiple entries even if the entries share the same port
- frameworks can provide rootUrl when requesting mirrors
- Support for Meteor >= 0.9.1
- Added Velocity.registerTestingFramework as the new preferred way to register the testing framework to Velocity.
- velocityIsMirror now available as a Meteor method for clients to know where they are running
- Fixtures added through _addFixtures are now copied to the mirror
- Added a VelocityMirrors collection that contains mirror metadata
- Added preProcessors that run after an rsync but before starting a mirror
- Added postProcessors which run after all frameworks have finished
- add option to FileCopier to control when files are copied
- Improved error handling when the mirror cannot be started. Velocity will retry to start the mirror for 10 seconds before an error is shown.
- The mirror urls are now based on the parent ROOT_URL and MONGO_URL
- Velocity will now output the mirror log when the environment variable
VELOCITY_DEBUG_MIRRORis set to a truey value
- FileCopier: Updated fs-extra dependency
- optimize searching for test packages
- FileCopier: Correctly handle when a file already exists in the mirror
- Passes audit-argument-checks now
- Added API for requesting mirrors
- Added API for resetting the database of the mirror
- Added FileCopier utility that can be used for copying test files into the mirror
- Added Velocity.getMirrorPath for getting the absolute mirror directoy path
- Added Velocity.getTestsPath for getting the absolute tests directory path
- remove example submodule; instruct how to use external repo instead
- update repo so users can ref velocity repo directly in smart.json
- Remove ref to unused mirror package
- Add copySampleTests Meteor method
- Use rsync mirroring
- Removed HTML reporter from
- Erroneous release!
Added show/hide visibility toggle for every each report section with browser state persistence using amplify
Frameworks can now let Velocity know when they are complete, and the results will update on the UI.
Fix for report overlay when used in conjunction with accounts-*
Auto-detect velocity-compatible packages via testPackages:true in their smart.json files.
Murky ancient history...