TDD - Revision history

Tim at 18:29, 17 April 2016

2016-04-17T18:29:53Z

← Older revision		Revision as of 14:29, 17 April 2016
Line 8:		Line 8:
	*https://docs.angularjs.org/api/ngMock/service/$httpBackend		*https://docs.angularjs.org/api/ngMock/service/$httpBackend
	*[https://gist.github.com/blesh/8846528 basics on unit testing controller]		*[https://gist.github.com/blesh/8846528 basics on unit testing controller]
			*http://stackoverflow.com/questions/15048132/angularjs-promise-not-being-resolved-in-unit-test

	==testing==		==testing==

Tim at 18:29, 17 April 2016

2016-04-17T18:29:18Z

← Older revision		Revision as of 14:29, 17 April 2016
Line 2:		Line 2:
	Now working out of c://wamp/www where all the packages get installed. To run testing you need to access the karma and its submodules there but you then use the local conf file. (npm scripts do not work)		Now working out of c://wamp/www where all the packages get installed. To run testing you need to access the karma and its submodules there but you then use the local conf file. (npm scripts do not work)

	c://wamp/www/node_modules/karma/bin/karma start karmocha.conf.js		c://wamp/www/node_modules/karma/bin/karma start karmocha.conf.js

			*http://attackofzach.com/setting-up-a-project-using-karma-with-mocha-and-chai/
			*http://www.bradoncode.com/blog/2015/05/19/karma-angularjs-testing/
			*https://docs.angularjs.org/api/ngMock/service/$httpBackend
			*[https://gist.github.com/blesh/8846528 basics on unit testing controller]

	==testing==		==testing==
	====regression testing====		====regression testing====

Tim at 17:50, 15 April 2016

2016-04-15T17:50:09Z

← Older revision		Revision as of 13:50, 15 April 2016
Line 1:		Line 1:
	==front-end testing karma==		==front-end testing karma==
	Now working out of c://wamp/www where all the packages get installed. To run testing you need to access the karma and its submodules there but you then use the local conf file		Now working out of c://wamp/www where all the packages get installed. To run testing you need to access the karma and its submodules there but you then use the local conf file. (npm scripts do not work)

	c://wamp/www/node_modules/karma/bin/karma start karmocha.conf.js		c://wamp/www/node_modules/karma/bin/karma start karmocha.conf.js

Tim at 17:49, 15 April 2016

2016-04-15T17:49:20Z

← Older revision		Revision as of 13:49, 15 April 2016
Line 2:		Line 2:
	Now working out of c://wamp/www where all the packages get installed. To run testing you need to access the karma and its submodules there but you then use the local conf file		Now working out of c://wamp/www where all the packages get installed. To run testing you need to access the karma and its submodules there but you then use the local conf file

	c://wamp/www/node_modules/karma/bin/karma start karmocha.conf.js		c://wamp/www/node_modules/karma/bin/karma start karmocha.conf.js
	==testing==		==testing==
	====regression testing====		====regression testing====

Tim at 17:49, 15 April 2016

2016-04-15T17:49:05Z

← Older revision		Revision as of 13:49, 15 April 2016
Line 1:		Line 1:
	===testing===		==front-end testing karma==
			Now working out of c://wamp/www where all the packages get installed. To run testing you need to access the karma and its submodules there but you then use the local conf file

			c://wamp/www/node_modules/karma/bin/karma start karmocha.conf.js
			==testing==
	====regression testing====		====regression testing====
	Regression testing is a type of software testing that seeks to uncover new software bugs, or regressions, in existing functional and non-functional areas of a system after changes such as enhancements, patches or configuration changes, have been made to them. The purpose of regression testing is to ensure that changes such as those mentioned above have not introduced new faults. One of the main reasons for regression testing is to determine whether a change in one part of the software affects other parts of the software. Regression tests can be broadly categorized as functional tests or unit tests. Functional tests exercise the complete program with various inputs. Unit tests exercise individual functions, subroutines, or object methods		Regression testing is a type of software testing that seeks to uncover new software bugs, or regressions, in existing functional and non-functional areas of a system after changes such as enhancements, patches or configuration changes, have been made to them. The purpose of regression testing is to ensure that changes such as those mentioned above have not introduced new faults. One of the main reasons for regression testing is to determine whether a change in one part of the software affects other parts of the software. Regression tests can be broadly categorized as functional tests or unit tests. Functional tests exercise the complete program with various inputs. Unit tests exercise individual functions, subroutines, or object methods

Tim at 17:45, 15 April 2016

2016-04-15T17:45:44Z

← Older revision		Revision as of 13:45, 15 April 2016
Line 1:		Line 1:
	{{:~~testing}~~}		===testing===
			====regression testing====
			Regression testing is a type of software testing that seeks to uncover new software bugs, or regressions, in existing functional and non-functional areas of a system after changes such as enhancements, patches or configuration changes, have been made to them. The purpose of regression testing is to ensure that changes such as those mentioned above have not introduced new faults. One of the main reasons for regression testing is to determine whether a change in one part of the software affects other parts of the software. Regression tests can be broadly categorized as functional tests or unit tests. Functional tests exercise the complete program with various inputs. Unit tests exercise individual functions, subroutines, or object methods

			Contrast with non-regression testing (usually validation-test for a new issue), which aims to verify whether, after introducing or updating a given software application, the change has had the intended effect.

			http://jsfiddle.net/fdietz/2Ny8x/

			npm install mocha chai --save-dev
			same as
			npm i -D mocha chai

			create a test file src/index.test.js
			var expect = require('chai').expect;
			var starWars = require('./index');
			describe('starwars-names', function() {
			describe('all', function() {
			it('should be an array of strings', function() {
			expect(starWars.all).to.satisfy(isArrayOfStrings);
			function isArrayOfStrings(array) {
			return array.every(function(item) {
			return typeof item === 'string';
			});
			}
			});
			it('should contain `Luke Skywalker`', function() {
			expect(starWars.all).to.include('Luke Skywalker');
			});
			});
			describe('random', function() {
			it('should return a random item from the starWars.all', function() {
			var randomItem = starWars.random();
			expect(starWars.all).to.include(randomItem);
			});
			});
			});

			change package.json to run tests (automatically on update -w)

			"scripts": {
			"test": "mocha src/index.test.js -w"
			},

			npm test


	====[https://github.com/LearnBoost/expect.js/ expect.js syntax]====		====[https://github.com/LearnBoost/expect.js/ expect.js syntax]====

Tim at 17:44, 15 April 2016

2016-04-15T17:44:04Z

← Older revision		Revision as of 13:44, 15 April 2016
Line 1:		Line 1:
			{{:testing}}

	====[https://github.com/LearnBoost/expect.js/ expect.js syntax]====		====[https://github.com/LearnBoost/expect.js/ expect.js syntax]====

Tim at 13:32, 19 March 2014

2014-03-19T13:32:13Z

← Older revision		Revision as of 09:32, 19 March 2014
Line 1:		Line 1:
			====[https://github.com/LearnBoost/expect.js/ expect.js syntax]====


	http://thewayofcode.wordpress.com/2013/04/21/how-to-build-and-test-rest-api-with-nodejs-express-mocha/		http://thewayofcode.wordpress.com/2013/04/21/how-to-build-and-test-rest-api-with-nodejs-express-mocha/

Tim at 16:57, 14 March 2014

2014-03-14T16:57:56Z

← Older revision		Revision as of 12:57, 14 March 2014
Line 18:		Line 18:

	http://visionmedia.github.io/superagent/		http://visionmedia.github.io/superagent/

			http://jsbin.com/wodonuce/1/edit

Tim at 22:01, 12 March 2014

2014-03-12T22:01:55Z

← Older revision		Revision as of 18:01, 12 March 2014
Line 14:		Line 14:

	http://www.wekeroad.com/2012/02/25/testing-your-model-with-mocha-mongo-and-nodejs/		http://www.wekeroad.com/2012/02/25/testing-your-model-with-mocha-mongo-and-nodejs/

			https://github.com/visionmedia/supertest/blob/master/test/supertest.js

			http://visionmedia.github.io/superagent/