This is a backend http server to collect results of the web-testsuite (https://github.com/vf/web-testsuite) written in node.js. This project is in a very early state of development. If there are any questions, design issues or bugs, file them on github or contact me ([email protected], @browserlove or @ranzwertig).
- Node 0.4+ (tested with node 0.4.5)
-
Download and compile nodejs (http://nodejs.org/).
-
Clone or Download the web-testsuite-backend source from Github.
-
Modify the config.js file.
-
do sth, like
$ node backend.js
Modify the config.js file to set the port and host you server should run. Therefore edit following section:
exports.httpSettings = {
port: 8080,
host: '127.0.0.1'
};
If you like to run more instances of the backend.js server you are able to configure the server using command line arguments. Just do sth. like:
$ node backend.js host=127.0.0.1 port=8080
The command line args will overwrite the configuration defined in the config.js.
The web-testsuite-backend is designed to support multiple modules where the requests are processed. All modules are stored in the modules folder. To enable a module, just go to the config.js File and add the module to the following section:
exports.modulesEnabled = [
'toFile'
,'toMongo'
];
The request handlers inside the modules are called in the order they are enabled.
A module for example looks like:
exports.onpost = function(req, res){
res.write('hello from post handler');
res.end();
};
exports.onget = function(req, res){
res.write('hello from get handler');
res.end();
};
In this example a handler for GET and POST requests is defined. Possible handlers are:
exports.onget = function(request, response) { ...; response.end(); };
exports.onpost = function(request, response) { ...; response.end(); };
exports.onput = function(request, response) { ...; response.end(); };
exports.ondelete = function(request, response) { ...; response.end(); };
When the function response.end() is called inside a module request handler, the response isn't ended! It just sends a signal to the backend which ends the response after all modules finished. So it is necessary to call response.end() inside a module after all the processing happened!
If you really need to end the response inside a module handler use response.seriouslyEnd(). But be careful with this, the following modules might fail!!!
Copyright (c) 2011 Christian Ranz [email protected]
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.