Change old /archive/* links to /daily/*
This commit is contained in:
parent
661669f2a5
commit
538141466c
406 changed files with 457 additions and 457 deletions
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
title: "Why I mostly write functional and integration tests"
|
||||
pubDate: 2022-09-16
|
||||
permalink: "archive/2022/09/16/why-mostly-write-functional-and-integration-tests"
|
||||
permalink: "daily/2022/09/16/why-mostly-write-functional-and-integration-tests"
|
||||
tags: ["drupal"]
|
||||
---
|
||||
|
||||
In [Wednesday's email]({{site.url}}/archive/2022/09/14/simpletest-drupal-test), I showed how quick it is to get started writing automated tests for a new Drupal module, starting with a functional test.
|
||||
In [Wednesday's email]({{site.url}}/daily/2022/09/14/simpletest-drupal-test), I showed how quick it is to get started writing automated tests for a new Drupal module, starting with a functional test.
|
||||
|
||||
I prefer the outside-in style (or London approach) of test-driven development, where I start with a the highest-level test that I can for a task. If the task needs me to make a HTTP request, then I’ll use a functional test. If not, I’ll use a kernel (or integration) test.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue