Webpage Testing

Risks
hoisting
unintentional creation of global variables

Best Practices seems unimportant but we need structured guidelines for our code
camelCase
all names start with letters
spaces around operators
4 spaces to indent code blocks No Tabs
lines < 80 characters
never declare numbers/strings/or booleans as objects it will slow down the website

Building and Testing
NodeJs: allows for a scalable website that lets sections of the website to sleep while not in use
facilitates multiple thread functionality
http://nodejs.org/about/

GruntJs: automates compilation and unit testing through a gruntfile
the task runner takes over and does our repetitive work for us
(will be part of the smoke test likely)
http://gruntjs.com/

Manual testing
testing how the program handles all types input at any stage
testing all links
test website on Firefox, Safari, and Chrome

Improving Speed
minimize DOM access
keep DOM small
ensure scripts are at the bottom of the page body
webpage analyzer to analyze the load speed
http://tools.pingdom.com/fpt/