Better (or even the best?) browser support for Nodeunit!

Or rather, why not the best?

I'm getting fed up with some sillinesses of QUnit. I'm currently considering my options for good front end test framework, and since I'm using Nodueinit for my back end code, I thought, why not use it for the client side as well? I gave it a try, and liked the fact that it worked, but I didn't like it's report output.

So, I thought why not improve upon it, and it could easily be the best FE unittesting framework out there.

I'm writing to you because I'd like to hear you thoughts about it, discuss our ideas, so that you'll be able to pull it back happily not resulting in us branching out to 2 separate projects.

Here are my initial thoughts:
- Be AMD (Asynchronous Module Definition) compatible, but provide functional fall back code if one wants to load it with `` tags.
- Have wonderful reporting UI, both in terms of functionality and look!

**What do you think? Ever thought about improving the FE reporter/support? What ideas do you have?**

Comienza revisando la compatibilidad existente de Nodeunit con el navegador y su reporter de frontend, y después investiga cómo encajarían la carga mediante AMD y un fallback de script-tag en el proyecto actual. El issue también solicita una UI de reporting considerablemente mejorada, pero no identifica archivos, pruebas ni criterios de aceptación concretos; para darlo por terminado sería necesario acordar el alcance y demostrar el comportamiento de carga y reporting en el navegador.

Escrito por el modelo de indexación a partir del texto del issue.