- Assuming we are working on the frontend.
    - We have the ability to load the mocha tests.
    - what we need?
        - Ability to refresh changes to files.
        - Ability to refresh changes to ps content.
        - Display AST from ps content.
        - Display transpiled result.
        - Test the transpiled
    - Go back to the frontend mocha js tests.
        - Make changes to a ps files.
        - Run the js and c transpilers (look to live files)
        - Run the mocha tests.

    - NOTE: For future
        - Move running of code 

- NOTE:
    - I need a local prototype that runs on my machine setup first. Later I can address how to make this distributable.
    - Essentially we need a prototype.

- Assuming we have a way to inject the environment in? What do we do next?
    - We setup the test suite on the server side?
        - It holds the testing state.
            - Which test is run
            - Test stats
            - Error handling / logging.
        - Reports when tests are done.

- What do I have now?
    - Server runs with express-tamed.

- We may need to use a proxy tool that will inject the browser stuff.
    - http://anyproxy.io/en/
    - https://github.com/joeferner/node-http-mitm-proxy

- What are we wanting?
    - A way to test code in browsers with just Mocha, jQuery, and TamedJs.
    - How to have code follow standard?
    - Tests should be able to be run seperate of the project or in the project.
        - Something like Swift Platfrom, I won't be able to commit the tests while in early stages of dev.
        - Maybe in the future when this test system is more stable, a case can be made to include it in Swift.
    - Can a browser include the tests?
        - We are not using foreign sites...
    - Let's assume all of this what would be the process?
        - We need to load mochajs.
        - We need to load chaijs
        - We need to load jQuery.
        - We need to load Tamed.
    - Maybe our testing could follow a pawscript type of system.