Главная
Study mode:
on
1
Introduction
2
Dont do this
3
Not getting the benefits
4
Different phases of testing
5
Where do you learn to test
6
Why move to automated testing
7
Issue tracking system
8
Writing the test first
9
Design implementation first
10
Test suites still brittle
11
Testdriven development
12
Mock queries
13
Example
14
Summary
15
stubs returning stubs
16
notifying users
17
train wreck
18
user object
19
double or stub
20
Validate returns
21
The problem
22
Double the validator
23
Design is important
24
People worry about writing tests
25
What happens with TDD
26
TDD is a way to think about your code
27
TDD is a complicated one
28
Testing thirdparty code
29
Testing objects
30
Testing framework repository
31
Testing user repository
32
Double repository
33
Example of double repository
34
Cloud API
35
Interface
36
Dont Test
Description:
Explore a comprehensive conference talk that delves into common pitfalls of test-driven development (TDD) and how to overcome them. Learn why teams often struggle to reap the promised benefits of TDD despite having seemingly healthy test suites. Discover the different phases of testing, understand the motivations behind automated testing, and gain insights into writing effective tests. Examine practical examples of mocking queries, handling stubs, and dealing with complex object interactions. Uncover the importance of proper design in testing and how TDD influences code thinking. Address concerns about writing tests, testing third-party code, and working with repositories. Gain valuable knowledge to improve your test suite and maximize the benefits of TDD in your development process.

Why Your Test Suite Sucks

PHP UK Conference
Add to list