mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
0ab298dd34
Since tests themselves already keep track of their failure, and the test list (i.e. the `TestList` class) tracks other concepts of grouped tests, such as "all tests", "filtered tests", etc. (like a `TestList` class would!) I believe it makes sense for it to also maintain a collection of "failed tests"... (in list form, of course!) This will allow the `Run.runTest` logic to move into `run.js` file without needing to pass back a separate `failed` variable in the event of a failure, since that is already being tracked through the `notifyFailed` facility.
Meteor is an ultra-simple environment for building modern web applications.
With Meteor you write apps:
- in modern JavaScript
- that send data over the wire, rather than HTML
- using your choice of popular open-source libraries
Try a getting started tutorial:
Next, read the guide and the documentation.
Quick Start
On Windows, the installer can be found at https://www.meteor.com/install.
On Linux/macOS, use this line:
curl https://install.meteor.com/ | sh
Create a project:
meteor create try-meteor
Run it:
cd try-meteor
meteor
Developer Resources
Building an application with Meteor?
- Announcement list: sign up at http://www.meteor.com/
- Having problems? Ask for help at: http://stackoverflow.com/questions/tagged/meteor
- Discussion forums: https://forums.meteor.com/
Interested in helping or contributing to Meteor? These resources will help:
We are hiring! Visit meteor.io/jobs to learn more about working full-time on the Meteor project.
Uninstalling Meteor
Aside from a short launcher shell script, Meteor installs itself inside your home directory. To uninstall Meteor, run:
rm -rf ~/.meteor/
sudo rm /usr/local/bin/meteor
On Windows, just run the uninstaller from your Control Panel.