Testing/PHPUnit - Revision history

Brandon CS Sanders: PHPUnit moved to Testing/PHPUnit: Adding a little hierarchy to the the flat organizational structure. That way PHPUnit can turn into a disambiguation page in the future.

2007-10-30T02:38:46Z

PHPUnit moved to Testing/PHPUnit: Adding a little hierarchy to the the flat organizational structure. That way PHPUnit can turn into a disambiguation page in the future.

Brandon CS Sanders: Adding :Category:Testing

2007-10-30T02:37:36Z

Adding Category:Testing

Brandon CS Sanders: Adding :Category:DevelopmentTeam

2007-10-30T02:34:09Z

Adding Category:DevelopmentTeam

Brandon CS Sanders: Promoting a couple of sections to h2 from h3

2007-10-30T02:33:31Z

Promoting a couple of sections to h2 from h3

Brandon CS Sanders: Including the bits about how to run the phpunit tests

2007-10-30T02:32:42Z

Including the bits about how to run the phpunit tests

Brandon CS Sanders: Articulating and standardizing our testing frameworks

2007-10-30T02:30:39Z

Articulating and standardizing our testing frameworks

New page

<noinclude><big>[[DevelopmentTeam]] < [[Testing]] < [[PHPUnit]]</big></noinclude>
__NOTOC__

[[phpunit.de]]

=== Installation ===
To install via pear (http://pear.php.net):
<pre>
$ pear channel-discover pear.phpunit.de
$ pear install phpunit/PHPUnit
</pre>

=== Xdebug extension ===
http://xdebug.org

To do code-coverage analysis, you need to install:
<pre>$ pecl install xdebug-beta</pre>

Also need to add this line to your php.ini (change path to the correct one):
<pre>
zend_extension="/usr/local/php/modules/xdebug.so"
</pre>

@@ Line 45: / Line 45: @@
 # We can write tests for existing AboutUs customizations.
 # We can start writing tests before we write code for new customizations.
 [[Category:DevelopmentTeam]]

← Older revision		Revision as of 02:34, 30 October 2007
Line 45:		Line 45:
	# We can write tests for existing AboutUs customizations.		# We can write tests for existing AboutUs customizations.
	# We can start writing tests before we write code for new customizations.		# We can start writing tests before we write code for new customizations.
		+
		+	[[Category:DevelopmentTeam]]

@@ Line 4: / Line 4: @@
 [[phpunit.de]]
-=== Installation ===
+== Installation ==
 To install via pear (http://pear.php.net):
 <pre>
@@ Line 22: / Line 22: @@
 </pre>
-=== Running the tests ===
+== Running the tests ==
 Then, in the /tests directory:
@@ Line 30: / Line 30: @@
 will run all the working tests we have at the moment (just a few).
-=== Code coverage analysis ===
+== Code coverage analysis ==
 Currently these have to be done manually for each file (change the name of the test class):
 <pre>

← Older revision		Revision as of 02:32, 30 October 2007
Line 21:		Line 21:
	zend_extension="/usr/local/php/modules/xdebug.so"		zend_extension="/usr/local/php/modules/xdebug.so"
	</pre>		</pre>
		+
		+	=== Running the tests ===
		+
		+	Then, in the /tests directory:
		+	<pre>
		+	$ php RunTests.php
		+	</pre>
		+	will run all the working tests we have at the moment (just a few).
		+
		+	=== Code coverage analysis ===
		+	Currently these have to be done manually for each file (change the name of the test class):
		+	<pre>
		+	$ phpunit --report /report BankAccountTest
		+	</pre>
		+	Code coverage reports are then in the /tests/report directory.
		+
		+	== next steps and how things should be done ==
		+	We have several options:
		+	# We can continue to write tests for standard mediawiki installation.
		+	## Extending code coverage for test classes that are working now.
		+	## Fixing test classes that are not working now.
		+	## Starting on new classes.
		+	# We can write tests for existing AboutUs customizations.
		+	# We can start writing tests before we write code for new customizations.

← Older revision	Revision as of 02:38, 30 October 2007
(No difference)