From 4e29f15340efbbb930a0c7cf05ae8f8101f2847e Mon Sep 17 00:00:00 2001 From: Bob Remeika Date: Thu, 16 Jun 2011 03:14:50 -0700 Subject: [PATCH] Added more of the site --- site/www/src/documents/about.html | 29 +++++++++ site/www/src/documents/documentation.html | 14 +++++ site/www/src/documents/download.html | 9 +++ site/www/src/documents/get-started.html | 64 ++++++++++++++++++-- site/www/src/documents/support.html | 12 ++++ site/www/src/layouts/home.html | 74 +++-------------------- 6 files changed, 129 insertions(+), 73 deletions(-) create mode 100644 site/www/src/documents/about.html create mode 100644 site/www/src/documents/documentation.html create mode 100644 site/www/src/documents/download.html create mode 100644 site/www/src/documents/support.html diff --git a/site/www/src/documents/about.html b/site/www/src/documents/about.html new file mode 100644 index 0000000..e5669b9 --- /dev/null +++ b/site/www/src/documents/about.html @@ -0,0 +1,29 @@ +--- +layout: home +--- + +

About

+ +

+foounit is an asynchronous BDD-style javascript test framework aimed at making cross-environment javascript testing simple. foounit is designed to make testing code that is shared between the server and the client less of a chore. It supports both commonjs loading and global scope loading of script files for immediate test dependencies in all environments. Test files are loaded in a functionally scoped environment to help minimize test pollution when running your suite. Test syntax is influenced heavily by Screw Unit, Jasmine and rspec.

+ +

+ foounit is the love child of Bob Remeika (me). It was written out of spite while consuming large amounts of alcohol. If you notice some bad code within foounit, it's definitely due to alcohol abuse. I'm not even going to try to pretend that I *meant* to do that. If you want to help with code quality then patches are accepted. +

+ +

+ A common question that I get is why didn't I just use Jasmine. See the FAQ. +

+ +

+ foounit is currently used at Yammer Inc. as the primary test harness for a core component of our client/server side architecture called yamjs. +

+ +

+ foounit is a Dojo Foundation project and is licensed under the Dojo Foundation License. This basically means that no One Company owns the project and the code is gauranteed to be IP Free (free as in beer). This is another reason why I didn't want to use Jasmine. +

+ +

+ This website was created by Heather Phillips (Yammer) and the logo was created by James Kang (Yammer). +

+ diff --git a/site/www/src/documents/documentation.html b/site/www/src/documents/documentation.html new file mode 100644 index 0000000..d6c1d8e --- /dev/null +++ b/site/www/src/documents/documentation.html @@ -0,0 +1,14 @@ +--- +layout: home +--- + +

Documentation

+ + + diff --git a/site/www/src/documents/download.html b/site/www/src/documents/download.html new file mode 100644 index 0000000..1d07e0b --- /dev/null +++ b/site/www/src/documents/download.html @@ -0,0 +1,9 @@ +--- +layout: home +--- + +

Download

+ +foounit-browser.js + + diff --git a/site/www/src/documents/get-started.html b/site/www/src/documents/get-started.html index c04d75b..630300a 100644 --- a/site/www/src/documents/get-started.html +++ b/site/www/src/documents/get-started.html @@ -1,10 +1,62 @@ --- layout: home -title: blah blah --- + +

Getting Started

- -
-

About

-

My life story

-
+

+ First install foounit with npm: + 

$ npm install foounit
+

+
+ +

Then follow these steps to run tests...

+ + + + +

In nodejs

+ +

+ Generate a sample suite in the spec directory: + 

$ foounit generate --type=node spec
+

+ +

+ Run the test: + 

$ node spec/example_spec.js
+

+ +

In the browser

+ +

+ Generate a sample suite in the spec directory: + 

$ foounit generate --type=browser spec
+

+ +

+ Start a web server in the directory where the suite was created: + 

$ foounit-server --spec=spec
+

+ +

+ Open a web browser at http://localhost:5057/spec/suite.html +

+ + +

Shared client and server code

+ +

+ Generate a sample suite in the spec directory: + 

$ foounit generate --type=browser,node spec
+ foounit is smart enough to know that when multiple environments are specified that it should create a shared directory for multi-environment testing +

+ +

+ Run the tests for each environment by following the directions in the previous steps. +

+ diff --git a/site/www/src/documents/support.html b/site/www/src/documents/support.html new file mode 100644 index 0000000..64b43b9 --- /dev/null +++ b/site/www/src/documents/support.html @@ -0,0 +1,12 @@ +--- +layout: home +--- + +

Support

+ + + diff --git a/site/www/src/layouts/home.html b/site/www/src/layouts/home.html index 6c6dadd..3edc9d2 100644 --- a/site/www/src/layouts/home.html +++ b/site/www/src/layouts/home.html @@ -11,11 +11,11 @@
@@ -23,7 +23,7 @@ Version 0.0.7
Updated: Today - Download + Download
@@ -78,67 +78,7 @@

{More Features}

- - -

Getting Started

- -

- First install foounit with npm: - 

$ npm install foounit
-

-
- -

Then follow these steps to run tests...

- - - - -

In nodejs

- -

- Generate a sample suite in the spec directory: - 

$ foounit generate --type=node spec
-

- -

- Run the test: - 

$ node spec/example_spec.js
-

- -

In the browser

- -

- Generate a sample suite in the spec directory: - 

$ foounit generate --type=browser spec
-

- -

- Start a web server in the directory where the suite was created: - 

$ foounit-server --spec=spec
-

- -

- Open a web browser at http://localhost:5057/spec/suite.html -

- - -

Shared client and server code

- -

- Generate a sample suite in the spec directory: - 

$ foounit generate --type=browser,node spec
- foounit is smart enough to know that when multiple environments are specified that it should create a shared directory for multi-environment testing -

- -

- Run the tests for each environment by following the directions in the previous steps. -

- - + <%- @content %>