Jesse Gibson 79cb4485ab Add test stack interface, add test event emitter & UIDs
When a test finishes configuration, it's piped through the new stack interface. The stack controls what tests are being served to the client, maintaining a list of queued and completed tests. As soon as a test finishes, the next one is selected.

Now each test has it's own event emitter. This'll be useful for extensions and syntactic sugar, such as when a runner is ready to run the test, or when a test finishes on a client, or when it finishes on all clients, fail events, progress events, etc...

Instead of the Response constructor creating the test ID, that's been delegated to the test itself.
2016-03-09 23:57:12 -07:00
2016-03-04 15:36:12 -07:00
2016-03-09 14:01:00 -07:00

Panic

A distributed testing framework designed for and built by the team at gunDB.

under development

Rough API draft

test('Client/server sync', function () {
	// set env variables
	this.env({
		url: 'http://localhost/gun'
	})

	// on every platform
	this.use(function () {
		this.env.db = new Gun(
			this.env.url
		)
	})

	// only on browsers
	this.client(function (client) {
		client.env.db.get('update').put({
			data: true
		})
	})
	
	// only on node clients
	this.server(function (server) {
		this.env.db.get('update').val(this.done)
	}, 15000)
	// 15 second timeout, run on the server
})

More sketches in notes.js

Description
No description provided
Readme 349 KiB
Languages
JavaScript 100%