Introduced forsetiJs wrapper for debug / case reporting. closes #27

Console outputs everything when running in the browser, otherwise defaults to standard behaviour w/ output to Envjs
introduced the forseti.framework and a different way of loading specs for testing (requirejs)
implemented the forseti.framework for jasmine
instead of rendering script tags, pushing script-paths into the system and case-queues to be tested
We now have the correct descriptionfilename when reporting a case result.
removed commented code from the harness view
#54  Reporting of test cases are now working as it should! Problem now is the runner is quite slow
fixes #31 the work was done, nut just not in use :)
ah, forgot to save the project file
Created baseline specs for handling added and deleted systems and descriptions- Now for some edge cases
Some basic refactoring for clarity
Reproduced the (a) bug in specs
Using the file to identify Sute or Description.  Should fix #54

Its the only way to be sure we're taking actions for the correct file.
Clearing cases before running, so that reporting is done correctly. Shouldnt have to do it tthis way though
Merge branch 'master' into CorrectResultReporting

Conflicts:
	Source/Forseti/Harnesses/HarnessCaseReporter.cs
	Source/Forseti/Pages/Spark/PageGenerator.cs
printing out the system name, description and expectations in a more BDD-style. resolves #53
Using a local copy of require within forseti, so it doesn't get affected by specs
fixed failing specs that were related to dummycase refactor
Added the concept of inconclusive results.

This is for descriptions that dont get reported on
Added option for ouputing only errors. Also ouputing inconclusive totals and dot-summary