This repository is made for realtime testing of WebRTC JS API code with node-jet api and mocha. WebRTC JS API is an API between server and client javascript code, provides calls between peers on browsers. Test code is be able to:
- Create calls and share information between peers
- Create conversation and share messages between peers
- Manipulate Calls (Hold, Unhold, Mute, Join, Forward etc)
- Work simultaneously with multiple clients (Multiple clients can edit the call state at the same time and every client sees each other clients state in real time.)
To build and run this project run:
git clone git@github.com:rasimavci/sdk-test.git
cd sdk-test
npm install
npm link Kandy-js
npm run build
npm start 8090Open some browser tab on your localhost and start a call and realtime state changes.
KATE as its name implies is an framework for test automation. Can be used as core for REST API Apps.
However KATE is more than that:
- Self-hostable
- Fully moduler approach, UAT (Unit Under Test) is customizable
- Flexible realtime APIs
- Real Time RPC with Node-Jet
- Flexible third party test/assertion library
Self-hosted means that running Jet does not involve any 3rd party servers where your data passes through. In standard way Node-Jet Daemon runs on pc but can be easily embedded into any Node.js based webserver.
Realtime colloboration between test clients can save you a lot of time. Imagine you have hundreds of tests, and every test needs to be verified in real environment. Standard time for a test to be run on a UI takes 3-4 minutes each. We do it real time withoout mocking.
KATE helps you run your API tests without user interface and without mocking anything. By this way, KATE stands between unit test and UI test. Since inline used node-jet library updates states in realtime, all you need is to instruct your test clients to make API calls and get results. You don't have to check any UI message and filter them at the client level ! API testing was never been easy.
KATE uses Node-Jet , a Javascript framework for realtime communication. It is an open protocol with compatible implementation.a
Both Node-Jet, Mocha and Chair are free and open source libraries.
For this project all you need:
- A browser
- Node-Jet webserver
- An API to test
A webserver is required for serving clients. Node.js https server handles this. -Creating node.js https server explained below. For Kandy.js testing, secure webserver is used.
-If you have licensing issues for a secure server on your pc, please creat ssl license with cygwin or some other tools.
Inside src folder, you will see these files:
- sdktest-server.js (Node.js Webserver + Node-Jet Daemon + Node-Jet Peer as Kandy Client.)
- sdktest-client.js (Kandy client which uses Jet Peer)
- instructor.html (Instructor peer to control overall test running and clients.)
The sdktest-server.js will provide a webserver for serving call and conversation objects besides providing Jet Daemon as communication center.
A Jet Peer will finally add the Call Server-App logic be providing means for:
- create Calls & Conversations
- delete Calls & Conversations
- update Call state
- send message
- send API request (addressbook, contacts, voicemail etc.)
- update information by listening events
First you need to setup the webserver for call objects and create a Jet Daemon:
var jet = require('node-jet');
...
// Serve this dir as static content
var serve = serveStatic('./');
var httpServer = http.createServer(function(req, res){
var done = finalhandler(req, res)
serve(req, res, done)
})
httpServer.listen(port);
// Create jet daemon and embed into httpServer
var daemon = new jet.Daemon();
daemon.listen({
server: httpServer
});The Daemon uses Websocket for communication and is hooked up to the webserver so that both listen on the same port. Daemon may run on any pc. Currently first client peer also run on server pc. If required, the Daemon may run on a totally different pc or different port.
Next comes the Call-App service, by creating a [Peer] and connecting it to the Daemon you are ready for it. But first it is necessary to understand the basics of KATE's core components inside Node-Jet: States and Methods.
For defining actions Node-Jet library provides Methods. They are defined by a unique path and a function, which gets invoked when the Method is called by another Peer. This snippet adds a Method which prints two arguments to the console:
var log = new jet.Method('log');
log.on('call', function(a, b) {
console.log(a, b);
});
peer.add(log);Another Client Peer may now consume the "log" service like this:
otherPeer.call('log', ['Call', 'Started']);Methods may have any JSON-compatible argument type and may return any JSON-compatible value.
A Call object in State is similar to a JSL API call object. It has a unique path and an associated value, which can be of any JSON-compatible type. A set callback can be specified, which allows the State to react on change requests. If the set function does not throw, a State-Change is posted automatically.
var burak = new jet.State('contacts/#12342',{name: 'Burak', age: 25, mailaddress: bkocak@netas.com.tr, firstname: burak, lastname: kocak});
burak.on('set', function(requestedValue) {
if (requestedValue.age < this.value().age) {
throw new Error('Sorry, this is not possible');
}
});
peer.add(jean-luc);Another Peer may try to modify States:
peer.set('persons/#52A92d', {name: 'Burak U.', age: 34});
peer.set('persons/#52A92d', {name: 'Burak U.', age: 20})
.then(function() {
console.log('Burak just unaged');
}).catch(function(err) {
console.log('Damn', err);
});This is just a simple uncomplete example to show custom validation for change requests. KATE allows you to do anything appropriate inside the set callback, like:
- interpolating the requested value (partial changes)
- custom validation
- adapting the requested value
No matter what you do, all Test Peers will have the actual value of the State and stay in sync all the time !
The following implementation also goes to the sdktest-server.js file. To group the Call-App functionality in a "namespace" , all State and Method related to call has paths start with "call/".
Create a Peer which connects to the local Daemon, an Object to store all Call States and a simple Call class.
var peer = new jet.Peer({
url: 'ws://localhost:' + port
});
var callStates = {};
var callId = 0;
var Call = function(title) {
if (typeof title !== 'string') {
throw new Error('title must be a string');
}
this.id = callId++;
this.title = title;
this.completed = false;
};
Call.prototype.merge = function(other) {
if (other.completed !== undefined) {
this.completed = other.completed;
}
if (other.title !== undefined) {
this.title = other.title;
}
};
Call.prototype.id = function() {
return this.id;
};Provided call/add Method, which will create a new Call Object in state when called.
var addCall = new jet.Method('call/add');
addCall.on('call', function (args) {
var title = args[0];
var call = new Call(title);
// create a new call state and store ref.
var callState = new jet.State('call/#' + call.id, call);
callState.on('set', function (requestedCall) {
call.merge(requestedCall);
return {
value: call
};
});
callStates[call.id] = callState;
peer.add(callState);
});The call/remove Method will remove the Call with specified id.
var removeCall = new jet.Method('call/remove');
removeCall.on('call', function (args) {
var callId = args[0];
if (callStates[callId]) {
callStates[callId].remove();
delete callStates[callId];
}
});The Peer running in the Browser will act as a "consumer" of the Methods and States the Call-Server Peer provides. It will:
- fetch the Call States to display them in browser. This allow testers to easy follow the tests during test running.
- call the call/add Method to create Calls
- call the call/remove Method to delete Calls
- edit States by calling set
Fetching is like having a realtime query. It provides you with initial values of States and keeps track of events. These events include:
- a new Call Object has been added
- a Call Object has been removed
- a Call State's value has changed
The Jet Daemon is able to filter and sort your fetch query based on paths and/or values. A callback must be provided that will be invoked everytime something relevant happens. A fetch for getting the active calls could look like this:
var activeCalls = new jet.Fetcher()
.path('startsWith', 'call/')
.key('state', 'equals', 'IN_CALL')
.sortByKey('id', 'number')
.range(1, 10)
.descending()
.on('data', function(topFemalePlayersArray) {});
peer.fetch(activeCalls);Fetch is very powerful and is used during tests. There is also get method which being called for check result during tests.
The Call-Client implementation is straight forward:
var peer = new jet.Peer({url: 'ws://' + window.location.host});
var addCall = function(title) {
peer.call('call/add', [title]);
};
var removeCall = function(id) {
peer.call('call/remove', [id]);
};
var removeAllCallss = function() {
peer.call('call/remove', []);
};
var setCallTitle = function(id, title) {
peer.set('call/#' + id, {title: title});
};
var setCallCompleted = function(id, completed) {
peer.set('call/#' + id, {completed: completed});
};
var renderCalls = function(calls) {
...
};
var Callss = new jet.Fetcher()
.path('startsWith', 'call/#')
.sortByKey('id', 'number')
.range(1, 30)
.on('data', renderCalls);
peer.fetch(calls);The implementation for conversation object in sdktest-server.js
// Declare Conversation function constructor
var messageId = 0
var Message = function (title) {
this.id = messageId++
if (typeof title !== 'string') {
throw new Error('title must be a string')
}
this.title = title
this.sender = ''
this.id_orig = ''
this.id_term = ''
this.conversation_orig = false
this.conversation_term = false
this.messages_orig = []
this.messages_term = []
this.message = ''
this.participants = []
this.participant = ''
}Declare fecther for Message Object
var msgObj = new jet.Fetcher()
.path('startsWith', 'msg/#')
.sortByKey('id', 'number')
.range(1, 30)
.on('data', function (msgObj) {
var msgArray = msgObj[0].value.messages_orig;
if (msgArray) { //[l - 1].timestamp
chatObj.innerHTML = ''
msgArray.forEach(function (msg) {
var msgLabel = document.createElement('label');
msgLabel.className = 'chatMessage' + (loginId == msg.sender ? '1' : '2');
msgLabel.innerHTML = '<i>' + msg.sender + '</i><br>' + msg.parts[0].text
chatObj.appendChild(msgLabel);
})
}
})Class Constructor
class Peer_kandy1 {
constructor() {
this.peer = new jet.Peer({
url: (window.location.protocol === 'http:' ? 'ws://' : 'wss://') + window.location.host
});
var self = this;Declare all call methods inside the constructor
this.loginMethod = new jet.Method('call/login1');
this.loginMethod.on('call', function (args) {
console.log('Peer: login method called with credentials..', + args);
self.login(args)
});
this.logoutMethod = new jet.Method('call/logout1');
this.logoutMethod.on('call', function (args) {
console.log('Peer: logout method called..');
self.logout()
});
.... Connect peer and add methods to peer
this.peer.connect().then(function () {
console.log('Peer1: connection to Daemon established');
//console.log('Peer Daemon Info: ', this.peer.daemonInfo);
});
this.peer.add(this.loginMethod).then(function () {
console.log('Peer: login method added')
}).catch(function (err) {
console.log('Peer: add login method failed', err);
});
this.peer.add(this.logoutMethod).then(function () {
console.log('Peer: logout method added')
}).catch(function (err) {
console.log('Peer: add logout method failed', err);
});Write call state to node-jet state whenever a stateChange event fired
kandy.on('call:stateChange',function (data) {
if (call.to === 'hguner@genband.com' ) {
firstCallId = call.id;
self.peer.set('call/#' + 0, {
state_orig: call.state
})
}
} peer3.fetch(msgObj)
Mocha is used as test framework and Chai used as assertion library. Mocha and Chai libraries are choosed because they can be used in a Node.js environment as well as within the browser. Since Instructor and peers must run in browser you'll have to setup a test html page and use builds of these libraries:
<body>
<div id="mocha"><p><a href=".">Index</a></p></div>
<div id="messages"></div>
<div id="fixtures"></div>
<script src="node_modules/moch/bin/mocha.js"></script>
<script src="node_modules/chai/chai.js"></script>
<script src="kandy.js"></script>
<script>mocha.setup('bdd')</script>
<script src="bundle.js"></script>
<script>mocha.run();</script>
</body>describe("On Prem Test Suite", function () {
describe("Basic Call Test", function () {
this.timeout(1500000);
it("Orig side Call Status should be IN_CALL", function (done) {
peer3.call('login/add', ['login1'])
.then(() => peer3.call('call/login1', [user1[0], user1[1]]))
.then(() => checkLogin('isConnected1', true))
.then((interval) => clearInterval(interval))
.then(() => peer3.call('call/login2', [user2[0], user2[1]]))
.then(() => checkLogin('isConnected2', true))
.then((interval) => clearInterval(interval))
.then(() => peer3.call('call/add', ['call1']))
.then(() => peer3.call('call/makeCall1', [user2[0]]))
.then(() => checkResult('call_term', 'incoming'))
.then((interval) => { clearInterval(interval); peer3.call('call/answerCall2', ['empty']) })
.then(() => checkResult('state_orig', 'IN_CALL'))
.then((interval) => clearInterval(interval))
.then(() => {
// returnResult('state_term', 'IN_CALL').then((result) => expect(result).to.equal("IN_CALL"))
done(); //dont use .then(done) or things may break due to extra
})
.catch(err => {
console.log(err);
done(err); //passing a parameter to done makes the test fail.
})
});Test Code for Call Status Check.
it("Term side Call Status should be IN_CALL", function (done) {
checkResult('state_term', 'IN_CALL')
.then((interval) => clearInterval(interval))
.then(() => {
returnResult('state_term', 'IN_CALL').then((result) => expect(result).to.equal("IN_CALL"))
done(); //dont use .then(done) or things may break due to extra
})
.catch(err => {
console.log(err);
done(err); //passing a parameter to done makes the test fail.
})
});Code For Call End
it("Call Should end properly", function (done) {
peer3.call('call/end1', [''])
.then(() => checkResult('state_term', 'ENDED'))
.then((interval) => clearInterval(interval))
.then(() => checkResult('state_orig', 'ENDED'))
.then((interval) => clearInterval(interval))
.then(() => checkResult('mediaState_orig', 'CLOSED'))
.then((interval) => clearInterval(interval))
.then(() => peer3.call('call/clearCompleted', [0]))
.then(() => {
returnResult('state_term', 'IN_CALL').then((result) => expect(result).to.equal("IN_CALL"))
done(); //dont use .then(done) or things may break due to extra
})
.catch(err => {
console.log(err);
done(err); //passing a parameter to done makes the test fail.
})
});
});In this article I showed you how to create a simple realtime collaborative Call-App with Node.js and Jet. The call list can be edited by multiple clients simultaneously and always stays in sync. The KATE node-jet embedded webserver performs server-side custom validation, which enables you to keep your Tested Application integre and flexible at the same time.
You **don't need any third party server and you always keep complete control over your servers and your data.
At HBM the Jet protocol is used in production code of medium- and embedded-class devices and we are constantly working to improve it.
If you want to read more, checkout the Kandy.js Homepage or its github repository: