• Use jQuery to render to the DOM
• Use jQuery to handle human interaction events
• See how separation of concerns works
• Understand limitations of local storage

Fork this repository on GitHub, clone it and work on your local machine to get the specs to pass and build a usable app.

When you run the specs, follow the failure messages to find out what needs to be coded.

The spec should give you a clue about which file you will need to write code in - JavaScript files are in the /src directory and html is in the /web. Once you find that file, there will generally be some instructions in the comments as to what needs to be coded up. Write an implementation to get the specs passing. Ask for help if you get stuck.

In these exercises you'll write real code and run real specs.

npm test

The specs are already written and given as part of the exercise. You can find the specs in the /spec directory but they test code that is in the /src directory.

Don't have to worry about reading the files in /spec folder or understanding how they work, but your free to check them out.

You'll be able to see the output of the specs in a browser - the failure messages should guide you towards what you need to code. The failure messages are not always obvious or human readable, so it might take a little getting used to. (Sometimes you have to try and think like a computer to understand them :)

You can expect that the given specs are correct; however they will be in a failing state since the code they are testing still needs to be written.

The exercise has many failing tests and these are sequenced in a way to help you learn concepts that build on each other. Work on the 1st failing spec, once you get that passing, move on to the next one that is failing...

npm start

When you first launch it will not be working sinc you still have to implement the code. As you start to get the specs to pass, the app may start to have some functionality. Feel free to incrementally test the app as you incrementall add code. The app should be fully functional once all the specs are passing.

• Take the first failing spec
• Read what the failure message is all about
• Find the source file you need to write code in (based on the failure message)
• Focus on writing the code that you need to get the spec passing
• run webpack to rebuild your new code (or use the --watch option)
• re-run the spec (by refreshing the browser) and see if the test now passes
• If the test is still failing, rework your implementation until it passes
• Once the test passes, move on to the next failing spec and get it to pass
• After you get a spec tp pass, commit your code and push it up to GitHub

• src: The JavaScript source code is in the /src folder - This is where you will write your code.
• web: The HTML files for the application are in the /web folder
• style: The CSS for the application are in /style
• spec: The specs are described in the /spec folder
• dist: The final packaged up bundle(s) are in /dist - HTML files can include these
• node_modules: The npm install command downloads JavaScript modules into this directory

First Fork this repository on GitHub so you have your own copy. Also:

• install node
• install webpack

• Install the app
• Launch the app to see what it looks like in its broken state
• Run the tests and see what the failures are
• Write code to implement the WarmUp functions
• Rerun the tests to make sure they are passing
• Refresh the app to make sure it is no longer broken
• Commit your code and push it back up to your fork on GitHub

cd warm-up
npm install
webpack

This will open up the application in the browser.

npm start

Remember that the app won't work until you complete the exercise and implement the missing methods.

This will launch and run the specs in your browser:

npm test

Both the app and the specs start the webpack development server and open a webpage to http://localhost:8080. When you make a change to your code, the page should automatically reload and your changes will take effect. If you find that your changes are not getting reloaded, simple ^c to quit the server and run it again.