Using a test database - Revision history

Bahati at 10:00, 11 March 2011

2011-03-11T10:00:06Z

← Older revision		Revision as of 10:00, 11 March 2011
Line 1:		Line 1:
	{{howto\|Intermediate\|[[Peter C. Verhage]] ~~<peter@ibuildings.nl>~~}}		{{howto\|Intermediate\|[[Peter C. Verhage]] }}

	== Preface ==		== Preface ==

bahtiar: /* Using fixtures in your test-case */ Use new select api

2010-02-10T06:47:11Z

Using fixtures in your test-case: Use new select api

← Older revision		Revision as of 06:47, 10 February 2010
Line 188:		Line 188:
	$record['email'] = 'nobody@example.com';		$record['email'] = 'nobody@example.com';

	$this->assertEqual(2, $node->~~countDb~~());		$this->assertEqual(2, $node->select()->rowCount());
	$this->assertTrue($node->addDb($record));		$this->assertTrue($node->addDb($record));
	$this->assertFalse(isset($record['atkerror']));		$this->assertFalse(isset($record['atkerror']));
	$this->assertEqual(3, $node->~~countDb~~());		$this->assertEqual(3, $node->select()->rowCount());
	$this->assertTrue($record['id'] > 2);		$this->assertTrue($record['id'] > 2);
	}		}
Line 216:		Line 216:
	$node = atkGetNode('example.employee');		$node = atkGetNode('example.employee');
	$selector = sprintf("employee.email = '%s'", $node->getDb()->escapeSQL($employee['email']));		$selector = sprintf("employee.email = '%s'", $node->getDb()->escapeSQL($employee['email']));
	~~list(~~$row) = $node->~~selectDb~~($selector);		$row = $node->select($selector)->getFirstRow();

	$this->assertNotNull($row);		$this->assertNotNull($row);

Boy: /* Preface */

2008-01-09T10:11:43Z

Preface

← Older revision		Revision as of 10:11, 9 January 2008
Line 2:		Line 2:

	== Preface ==		== Preface ==
	ATK has built-in test support for a while now. But until now this didn't include support for adding, updating and/or removing test data in such a way that the development/production database isn't littered with test data. You can make use of the mock database class, but then you can't really test if the query you wrote actually works the way it's supposed to work. And you can ofcourse remove the test data in your test by writing the necessary code to do so, but this means a lot of extra work.		ATK has [[ATK_Testing\|built-in test support]] for a while now. But until now this didn't include support for adding, updating and/or removing test data in such a way that the development/production database isn't littered with test data. You can make use of [[Using_atkMockDb\|the mock database class]], but then you can't really test if the query you wrote actually works the way it's supposed to work. And you can ofcourse remove the test data in your test by writing the necessary code to do so, but this means a lot of extra work.

	Fortunately there's a third option, you can make use of ATK's built-in test database support. This feature has been heavily inspired by Ruby On Rails (http://www.rubyonrails.org) test database support and makes setting up test databases a breeze.		Fortunately there's a third option, you can make use of ATK's built-in test database support. This feature has been heavily inspired by Ruby On Rails (http://www.rubyonrails.org) test database support and makes setting up test databases a breeze.

	== How it works ==		== How it works ==

Peter: /* Summary */

2007-04-18T07:51:15Z

Summary

← Older revision		Revision as of 07:51, 18 April 2007
Line 255:		Line 255:

	== Summary ==		== Summary ==
	This ~~how to~~ has given you an overview of ATK's built-in test database support. Using a test database gives you a powerful way of testing your code without messing up your development or, even worse, production database.		This howto has given you an overview of ATK's built-in test database support. Using a test database gives you a powerful way of testing your code without messing up your development or, even worse, production database.

	Fixtures are a way to ease the insertion of test data in your test database. Using fixtures you can quickly create a (large) set of test data which can be used inside your test-cases. Because fixtures are separated from your test-cases you can reuse them in different test-cases.		Fixtures are a way to ease the insertion of test data in your test database. Using fixtures you can quickly create a (large) set of test data which can be used inside your test-cases. Because fixtures are separated from your test-cases you can reuse them in different test-cases.

	Because ATK makes sure before each test method your test database is cleaned-up and all fixtured registered for your test-case are (re-)inserted in the database you always know exactly what data is available in your test database.		Because ATK makes sure before each test method your test database is cleaned-up and all fixtured registered for your test-case are (re-)inserted in the database you always know exactly what data is available in your test database.

Peter: /* Using fixtures in your test-case */

2007-04-18T07:50:42Z

Using fixtures in your test-case

← Older revision		Revision as of 07:50, 18 April 2007
Line 189:		Line 189:

	$this->assertEqual(2, $node->countDb());		$this->assertEqual(2, $node->countDb());
	$this->~~assertEqual~~($node->addDb($record));		$this->assertTrue($node->addDb($record));
	$this->assertFalse(isset($record['atkerror']));		$this->assertFalse(isset($record['atkerror']));
	$this->assertEqual(3, $node->countDb());		$this->assertEqual(3, $node->countDb());
Line 211:		Line 211:

	$this->assertNotNull($employee);		$this->assertNotNull($employee);
	$this->~~assertTrue~~('John', $employee['firstname']);		$this->assertEqual('John', $employee['firstname']);

	// Use the node to retrieve the employee row.		// Use the node to retrieve the employee row.
Line 219:		Line 219:

	$this->assertNotNull($row);		$this->assertNotNull($row);
	$this->~~assertTrue~~($employee['id'], $row['id']);		$this->assertEqual($employee['id'], $row['id']);
	$this->~~assertTrue~~($employee['firstname'], $row['firstname']);		$this->assertEqual($employee['firstname'], $row['firstname']);
	$this->~~assertTrue~~($employee['lastname'], $row['lastname']);		$this->assertEqual($employee['lastname'], $row['lastname']);
	$this->assertNotNull($row['email']);		$this->assertNotNull($row['email']);
	}		}

Peter: /* Summary */

2007-04-18T07:49:28Z

Summary

← Older revision		Revision as of 07:49, 18 April 2007
Line 255:		Line 255:

	== Summary ==		== Summary ==
	This how to has given you an overview of ATK's built-in test database support. Using a test database gives you a powerful way ~~to test~~ your code without messing up your development or production database. Fixtures are a way to ease the insertion of test data in your test database. Using fixtures you can quickly create a (large) set of test data which can be used inside your test-cases. Because fixtures are separated from your test-cases you can reuse them in different test-cases. Because ATK makes sure before each test method your test database is cleaned-up and all fixtured registered for your test-case are (re-)inserted in the database you always know exactly what data is available in your test database.		This how to has given you an overview of ATK's built-in test database support. Using a test database gives you a powerful way of testing your code without messing up your development or, even worse, production database.

			Fixtures are a way to ease the insertion of test data in your test database. Using fixtures you can quickly create a (large) set of test data which can be used inside your test-cases. Because fixtures are separated from your test-cases you can reuse them in different test-cases.

			Because ATK makes sure before each test method your test database is cleaned-up and all fixtured registered for your test-case are (re-)inserted in the database you always know exactly what data is available in your test database.

Peter: /* Dynamic fixtures */

2007-04-18T07:47:19Z

Dynamic fixtures

← Older revision		Revision as of 07:47, 18 April 2007
Line 253:		Line 253:

	Inside your PHP code you have all of ATK at your disposal, so you can use the complete library just like your normally would. Using PHP inside your fixtures is supported out of the box, so you don't need to do anything special.		Inside your PHP code you have all of ATK at your disposal, so you can use the complete library just like your normally would. Using PHP inside your fixtures is supported out of the box, so you don't need to do anything special.

			== Summary ==
			This how to has given you an overview of ATK's built-in test database support. Using a test database gives you a powerful way to test your code without messing up your development or production database. Fixtures are a way to ease the insertion of test data in your test database. Using fixtures you can quickly create a (large) set of test data which can be used inside your test-cases. Because fixtures are separated from your test-cases you can reuse them in different test-cases. Because ATK makes sure before each test method your test database is cleaned-up and all fixtured registered for your test-case are (re-)inserted in the database you always know exactly what data is available in your test database.

Peter: /* Dynamic fixtures */

2007-04-18T07:35:36Z

Dynamic fixtures

← Older revision		Revision as of 07:35, 18 April 2007
Line 231:		Line 231:

	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">
	John Doe:		John Doe:
	id: 1		id: 1
	firstname: John		firstname: John
Line 237:		Line 237:
	email: john.doe@example.com		email: john.doe@example.com
	created_at: <?php echo date('Y-m-d'); ?>		created_at: <?php echo date('Y-m-d'); ?>
	<?php		<?php
	for ($i = 2; $i <= 100; $i++)		for ($i = 2; $i <= 100; $i++)
	{		{
	?>		?>
	Employee <?php echo $i; ?>:		Employee <?php echo $i; ?>:
	id: <?php echo $i; ?>		id: <?php echo $i; ?>
	firstname: Employee <?php echo $i; ?>		firstname: Employee <?php echo $i; ?>
	lastname: Dummy		lastname: Dummy
	email: dummy<?php echo $i; ?>@example.com		email: dummy<?php echo $i; ?>@example.com
	created_at: <?php echo date('Y-m-d'); ?>		created_at: <?php echo date('Y-m-d'); ?>
	<?php } ?>		<?php
			}
			?>
	</syntaxhighlight>		</syntaxhighlight>

			Inside your PHP code you have all of ATK at your disposal, so you can use the complete library just like your normally would. Using PHP inside your fixtures is supported out of the box, so you don't need to do anything special.

Peter: /* Dynamic fixtures */

2007-04-18T07:24:38Z

Dynamic fixtures

← Older revision		Revision as of 07:24, 18 April 2007
Line 236:		Line 236:
	lastname: Doe		lastname: Doe
	email: john.doe@example.com		email: john.doe@example.com
			created_at: <?php echo date('Y-m-d'); ?>
	<?php		<?php
	for ($i = 2; $i <= 100; $i++)		for ($i = 2; $i <= 100; $i++)
Line 245:		Line 246:
	lastname: Dummy		lastname: Dummy
	email: dummy<?php echo $i; ?>@example.com		email: dummy<?php echo $i; ?>@example.com
			created_at: <?php echo date('Y-m-d'); ?>
	<?php } ?>		<?php } ?>
	</syntaxhighlight>		</syntaxhighlight>

Peter: /* Using fixtures in your test-case */

2007-04-18T07:23:27Z

Using fixtures in your test-case

← Older revision		Revision as of 07:23, 18 April 2007
Line 153:		Line 153:
	// not your test database. This way it's easier to switch test databases.		// not your test database. This way it's easier to switch test databases.
	$this->addFixture('example.department', 'default');		$this->addFixture('example.department', 'default');

			// The order in which you register fixtures is important. This is the same
			// order as they will be inserted in the database. So if you are using foreign
			// keys in your tables then records that are referenced by others records
			// should be inserted first.
	$this->addFixture('example.department_employee', 'default');		$this->addFixture('example.department_employee', 'default');
	}		}