- Overview
- Transcript
3.3 Code Coverage
Simply put, code coverage is a tool which will determine if you have more code than you need. It can even describe which code in your application is no longer need. Best of all, this can be done automatically! I will show you how it works in this episode.
Resources1.Introduction
1.1Why Test Driven Development (TDD)?04:09
1.1
Why Test Driven Development (TDD)?
04:09
1.2Installing PHPUnit07:29
1.2
Installing PHPUnit
07:29
2.Writing Tests
2.1Conventions06:49
2.1
Conventions
06:49
2.2Assertions08:01
2.2
Assertions
08:01
2.3Exceptions03:59
2.3
Exceptions
03:59
2.4PHP Errors, Warning and Notices02:59
2.4
PHP Errors, Warning and Notices
02:59
2.5Testing Output03:56
2.5
Testing Output
03:56
2.6Incomplete and Skipped Tests02:44
2.6
Incomplete and Skipped Tests
02:44
2.7Fixtures04:48
2.7
Fixtures
04:48
2.8File System Testing09:28
2.8
File System Testing
09:28
2.9Stubs15:53
2.9
Stubs
15:53
2.10Mocks09:13
2.10
Mocks
09:13
2.11Database Testing05:28
2.11
Database Testing
05:28
3.Running Tests
3.1The Command Line Test Runner08:12
3.1
The Command Line Test Runner
08:12
3.2Bootstrapping and the phpunit.xml File08:33
3.2
Bootstrapping and the phpunit.xml File
08:33
3.3Code Coverage06:51
3.3
Code Coverage
06:51
4.Miscellaneous
4.1Annotations11:30
4.1
Annotations
11:30
4.2Skeleton Generator03:54
4.2
Skeleton Generator
03:54
4.3Testing Web Services07:45
4.3
Testing Web Services
07:45
5.Finishing Up: Hands-On Example
5.1Enlog - A Simple Logger Using TDD33:43
5.1
Enlog - A Simple Logger Using TDD
33:43
