{"id":22014,"date":"2023-02-21T08:27:22","date_gmt":"2023-02-21T08:27:22","guid":{"rendered":"https:\/\/www.booksofall.com\/pl\/?post_type=product&p=22014"},"modified":"2023-02-21T08:27:23","modified_gmt":"2023-02-21T08:27:23","slug":"phpunit-manual","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/pl\/phpunit-manual\/","title":{"rendered":"PHPUnit Manual"},"content":{"rendered":"

PHPUnit<\/b>\u00a0is a\u00a0unit testing<\/a>\u00a0framework<\/a>\u00a0for the\u00a0PHP programming language<\/a>. It is an instance of the\u00a0xUnit<\/a>\u00a0architecture for unit testing frameworks that originated with\u00a0SUnit<\/a>\u00a0and became popular with\u00a0JUnit<\/a>. PHPUnit was created by Sebastian Bergmann and its development is hosted on\u00a0GitHub<\/a>.<\/p>\n

PHPUnit is based on the idea that developers should be able to find mistakes in their newly committed code quickly and assert that no code regression has occurred in other parts of the code base. Much like other unit testing frameworks, PHPUnit uses assertions to verify that the behavior of the specific component – or “unit” – being tested behaves as expected.<\/p>\n

The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a result, unit tests find problems early in the development cycle.<\/p>\n

PHPUnit can output test results in a number of different formats, including JUnit XML and TestDox.<\/p>\n","protected":false},"excerpt":{"rendered":"