The Drupal test suite has performance and maintainability issues that could be both addressed, together with consistency and readability, via an effort to make it adopt the Test Pyramid approach, as advocated for in this DC Rotterdam Core Conversation.

The Plan

Proposed solution

 E2E, Integration, Unit

A basic rule

Whenever writing a new test, a two-question rule of thumb should used:

  1. Level: what’s the test scope? Unit, integration, or end-to-end
  2. Type: what's the lightest available tool?
    • The default is a vanilla UnitTestCase test, possibly augmented via lightweight helper traits
    • Only move up the ladder if absolutely required
CommentFileSizeAuthor
#5 test-pyramid.png31.23 KBplach
#2 Inside The Pyramid.pdf3.05 MBplach

Comments

plach created an issue. See original summary.

plach’s picture

StatusFileSize
new3.05 MB

The session slides

plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
StatusFileSize
new31.23 KB
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes