https://github.com/temilaj/tasky
simple MEAN stack to-do list
https://github.com/temilaj/tasky
angular2 expressjs mean-stack mlab nodejs tasky
Last synced: about 2 months ago
JSON representation
simple MEAN stack to-do list
- Host: GitHub
- URL: https://github.com/temilaj/tasky
- Owner: temilaj
- Created: 2017-01-11T22:54:05.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2017-02-23T16:49:04.000Z (about 8 years ago)
- Last Synced: 2025-01-11T20:32:29.560Z (3 months ago)
- Topics: angular2, expressjs, mean-stack, mlab, nodejs, tasky
- Language: JavaScript
- Homepage:
- Size: 1.94 MB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Tasky
[![Build Status][travis-badge]][travis-badge-url]
Tasky is a simple MEAN stack application to keep track of tasks
This repository holds the TypeScript source code of the [angular.io quickstart](https://angular.io/docs/ts/latest/quickstart.html),
It's been extended with testing support so you can start writing tests immediately.
## Prerequisites
Node.js and npm are essential to Angular development.
Get it now if it's not already installed on your machine.
**Verify that you are running at least node `v4.x.x` and npm `3.x.x`**
by running `node -v` and `npm -v` in a terminal/console window.
Older versions produce errors.
## Create a new project based on the QuickStart
Clone this repo into new project folder (e.g., `my-proj`).
```bash
git clone https://github.com/angular/quickstart my-proj
cd my-proj
```
## Install npm packages
> See npm and nvm version notes above
Install the npm packages described in the `package.json` and verify that it works:
```bash
npm install
npm start
```
The `npm start` command first compiles the application,
then simultaneously re-compiles and runs the `lite-server`.
Both the compiler and the server watch for file changes.
## Testing
This repo adds both karma/jasmine unit test and protractor end-to-end testing support.
These tools are configured for specific conventions described below.
*It is unwise and rarely possible to run the application, the unit tests, and the e2e tests at the same time.
We recommend that you shut down one before starting another.*
### Unit Tests
TypeScript unit-tests are usually in the `app` folder. Their filenames must end in `.spec`.
Look for the example `app/app.component.spec.ts`.
Add more `.spec.ts` files as you wish; we configured karma to find them.
Run it with `npm test`
That command first compiles the application, then simultaneously re-compiles and runs the karma test-runner.
Both the compiler and the karma watch for (different) file changes.
Shut it down manually with `Ctrl-C`.
Test-runner output appears in the terminal window.
We can update our app and our tests in real-time, keeping a weather eye on the console for broken tests.
Karma is occasionally confused and it is often necessary to shut down its browser or even shut the command down (`Ctrl-C`) and
restart it. No worries; it's pretty quick.
### End-to-end (E2E) Tests
E2E tests are in the `e2e` directory, side by side with the `app` folder.
Their filenames must end in `.e2e-spec.ts`.
Look for the example `e2e/app.e2e-spec.ts`.
Add more `.e2e-spec.js` files as you wish (although one usually suffices for small projects);
we configured protractor to find them.
Thereafter, run them with `npm run e2e`.
That command first compiles, then simultaneously starts the Http-Server at `localhost:8080`
and launches protractor.
The pass/fail test results appear at the bottom of the terminal window.
A custom reporter (see `protractor.config.js`) generates a `./_test-output/protractor-results.txt` file
which is easier to read; this file is excluded from source control.
Shut it down manually with `Ctrl-C`.
[travis-badge]: https://travis-ci.org/angular/quickstart.svg?branch=master
[travis-badge-url]: https://travis-ci.org/angular/quickstart