1. Use BDD with Protractor for e2e tests and Karma for unit tests.
2. Use Angular to build client code.
3. Build incrementally using SOLID principles

Front-end features:

• Task (text) input form
• Display list of tasks
• Need additional actions
  • to update, click on task and over-write,
  • delete tasks, click on 'x' and remove task from list and
  • click on select box to mark task as complete

1. Set up Karma and Protractor
2. Sketch out html
3. Write e2e and unit tests for first two features
4. Set-up Angular
5. Write code to make tests past and then refactor

• Deadline: submit completed pull request by 9am on Monday
• You may use whatever level of JavaScript you feel comfortable with - pure JS, jQuery, Angular, or whatever weird and wonderful framework you want to try. Extra points for DogeScript

1. Fill out your learning plan self review for the week: https://github.com/makersacademy/learning_plan
2. Fork this repo, and clone to your local machine
3. Complete the following challenge:

Build a Todo list as a mini front-end application. You don't have to use a database, the front-end is more important - you can use an appropriate data structure stored somewhere in your JavaScript (this time only!)

Here are the core user stories:

As a forgetful person
I want to store my tasks
So that I don't forget them

As a person with limited time
I want to instantly be able to update my todo list (adding and changing entries)
So that I have more time to think about other things

As a person who actually gets stuff done
I want to mark my tasks as done
So that I don't do them twice

Here are some other user stories you may choose to implement:

As a person with a lot of tasks
I want to be able to filter my tasks by "All", "Active", "Complete"
So that I only see the relevant tasks

As a person who doesn't like counting by hand
I want to see a total number of tasks
So that I don't have to count

As someone who has done lots of stuff
I want to be able to clear my completed tasks
So I never see them again

As you may imagine, implementing a To-do list is very much a solved problem. However, we are mainly interested in seeing how you approach testing and design. We are looking for:

• well written, well structured acceptance and unit tests
• clear and expressive JavaScript
• good HTML5 markup

Don't worry about deployment, and make sure you read the CONTRIBUTING.md when submitting a pull request.

• Deploy the app
• Create a persistance layer (e.g. MongoDB), or use LocalStorage or the filesystem through Node
• Make it look purdy (CSS) - try a framework like Bootstrap or Foundation

Read the .travis.yml if any of the steps below don't make sense!

• Make sure you have set up npm test in your package.json so that it runs your Karma tests
• Make sure you have your Protractor config file at e2e/conf.js
• Make sure npm start spins up whatever serves up your app - http-server, Sinatra or Node

Good luck!