Root at 16:28, 22 October 2025

2025-10-22T16:28:39Z

← Older revision		Revision as of 17:28, 22 October 2025
Line 21:		Line 21:
	Before writing the function, you write a test for it. You can use PHP's built-in PHPUnit framework for this.		Before writing the function, you write a test for it. You can use PHP's built-in PHPUnit framework for this.

	<syntaxhighlight>// tests/AdderTest.php		<syntaxhighlight lang="php">// tests/AdderTest.php

	use PHPUnit\Framework\TestCase;		use PHPUnit\Framework\TestCase;
Line 30:		Line 30:
	{		{
	$adder = new Adder();		$adder = new Adder();
	$result = $adder-~~>~~add(1, 2);		$result = $adder->add(1, 2);

	$this-~~>~~assertEquals(3, $result);		$this->assertEquals(3, $result);
	}		}
	}</syntaxhighlight>		}</syntaxhighlight>
Line 42:		Line 42:
	Now, you'll write just enough code to make the test pass.		Now, you'll write just enough code to make the test pass.

	<syntaxhighlight>// src/Adder.php		<syntaxhighlight lang="php">// src/Adder.php

	class Adder		class Adder
Line 74:		Line 74:
	= Behaviour Driven Design =		= Behaviour Driven Design =

	BDD is a software development approach that extends Test-Driven Development (TDD) by using natural language descriptions (often following the format ~~"~~Given-When-Then~~"~~) to define the behavior of an application. BDD encourages collaboration between developers, QA, and non-technical participants in a software project.		BDD is a software development approach that extends Test-Driven Development (TDD) by using natural language descriptions (often following the format "Given-When-Then") to define the behavior of an application. BDD encourages collaboration between developers, QA, and non-technical participants in a software project.

	<span id="rundown-of-the-bdd-process"></span>		<span id="rundown-of-the-bdd-process"></span>
Line 80:		Line 80:

	* Use natural language to describe a feature of the application.		* Use natural language to describe a feature of the application.
	* Write scenarios for the feature using the ~~"~~Given-When-Then~~"~~ format.		* Write scenarios for the feature using the "Given-When-Then" format.
	* Implement test cases based on those scenarios.		* Implement test cases based on those scenarios.
	* Run the tests (they should initially fail since there's no implementation yet).		* Run the tests (they should initially fail since there's no implementation yet).
Line 92:		Line 92:
	* '''Feature Description''':		* '''Feature Description''':

	<syntaxhighlight>Feature: Add two numbers		<syntaxhighlight lang="php">Feature: Add two numbers
	In order to perform quick calculations		In order to perform quick calculations
	As a user of the calculator app		As a user of the calculator app
Line 98:		Line 98:
	Scenario:		Scenario:

	<syntaxhighlight>Scenario: Adding two positive numbers		<syntaxhighlight lang="php">Scenario: Adding two positive numbers
	Given I have a number 5		Given I have a number 5
	And I have another number 3		And I have another number 3
Line 105:		Line 105:
	Now, we can write a test for this scenario using Behat (a popular BDD tool for PHP):		Now, we can write a test for this scenario using Behat (a popular BDD tool for PHP):

	<syntaxhighlight>// features/bootstrap/FeatureContext.php		<syntaxhighlight lang="php">// features/bootstrap/FeatureContext.php

	use Behat\Behat\Context\Context;		use Behat\Behat\Context\Context;
Line 120:		Line 120:
	public function iHaveANumber($arg1)		public function iHaveANumber($arg1)
	{		{
	$this-~~>~~num1 = $arg1;		$this->num1 = $arg1;
	}		}

Line 128:		Line 128:
	public function iHaveAnotherNumber($arg1)		public function iHaveAnotherNumber($arg1)
	{		{
	$this-~~>~~num2 = $arg1;		$this->num2 = $arg1;
	}		}

Line 136:		Line 136:
	public function iAddTheTwoNumbers()		public function iAddTheTwoNumbers()
	{		{
	$this-~~>~~result = $this-~~>~~num1 + $this-~~>~~num2;		$this->result = $this->num1 + $this->num2;
	}		}

Line 144:		Line 144:
	public function iShouldGetAsTheResult($arg1)		public function iShouldGetAsTheResult($arg1)
	{		{
	if ($this-~~>~~result !== (int)$arg1) {		if ($this->result !== (int)$arg1) {
	throw new \Exception(~~"~~Expected $arg1, but got {$this-~~>~~result}~~"~~);		throw new \Exception("Expected $arg1, but got {$this->result}");
	}		}
	}		}
Line 152:		Line 152:

	Using BDD tools like Behat, combined with Mink (a web acceptance testing framework), you can also test web applications by simulating browser interactions, checking page contents, clicking links, and filling out forms. This brings BDD from simple unit tests to full-fledged feature tests, ensuring that the software behaves correctly from the user's perspective.		Using BDD tools like Behat, combined with Mink (a web acceptance testing framework), you can also test web applications by simulating browser interactions, checking page contents, clicking links, and filling out forms. This brings BDD from simple unit tests to full-fledged feature tests, ensuring that the software behaves correctly from the user's perspective.
	~~<!-- From bodyContent 1543108.mraw -->~~

	[[Category:IT backend patterns]]		[[Category:IT backend patterns]]

Maintenance script: Added category IT backend patterns

2025-10-19T17:51:20Z

Added category IT backend patterns

← Older revision		Revision as of 18:51, 19 October 2025
Line 154:		Line 154:
	<!-- From bodyContent 1543108.mraw -->		<!-- From bodyContent 1543108.mraw -->

			[[Category:IT backend patterns]]

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/IT backend team/IT backend policies/IT backend patterns/Test Driven Design to Test Driven Design: Cleaned title and categorized

2025-10-19T17:51:20Z

Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/IT backend team/IT backend policies/IT backend patterns/Test Driven Design to Test Driven Design: Cleaned title and categorized

← Older revision	Revision as of 18:51, 19 October 2025
(No difference)

imported>Unknown user at 10:31, 19 April 2025

2025-04-19T10:31:02Z

Show changes

imported>Unknown user at 10:31, 19 April 2025

2025-04-19T10:31:02Z

← Older revision	Revision as of 11:31, 19 April 2025
(No difference)

imported>Unknown user at 10:31, 19 April 2025

2025-04-19T10:31:02Z

New page

Test Driven Design - Revision history

Root at 16:28, 22 October 2025

Maintenance script: Added category IT backend patterns

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/IT backend team/IT backend policies/IT backend patterns/Test Driven Design to Test Driven Design: Cleaned title and categorized

imported>Unknown user at 10:31, 19 April 2025

imported>Unknown user at 10:31, 19 April 2025

imported>Unknown user at 10:31, 19 April 2025