What’s new?

1. ✨ E2E Backend Demos — Watch the demos here and the Q&A here
2. ✨ E2E Frontend / Walking Skeleton Demos
   1. Watch them here and the Q&A here (incoming August 1, 2023)

Why does this matter?

There are several forms of tests we’re learning to write, but perhaps the most important one for us to begin with is the Acceptance Test, and to learn how to apply it from End to End.

Why?

Because this is the test that helps us answer the following questions:

• Are we building what the customer has asked us for?
• How will this help the users achieve some valuable outcome?
• How do we know when we’re done a “feature” — what’s the Definition of Done?

<aside> ⚡ A messy drawing from our Q&A on the 27th. You can see the entire Q&A notes here. Link to watch is coming tomorrow.

</aside>

*The acceptance test, that Given-When-Then feature written in Gherkin — represents the exact moment we go from the highest form of what to how; from theoretical to physical, from declarative to imperative, from plan to implementation.

Before this test, we discuss the theoretical problem, solution, and the potential architecture we’ll use.

Only after we’ve formulated this test, we can shift our focus to minimum requirements of the physical system which must make this test pass. That minimal system is called The Walking Skeleton, from UI to Database**.***

And that’s what we’ve been able to build out!

What can you do with this?

Throughout the demonstrations, we cover a lot of different techniques from the 12 Essentials.

For example:

• Subject Verification — we’re verifying the most important thing; does our code do what the customer wants?
• Composition — we use this to make sense of dependencies so that we can start and stop the server (on the backend) in a clean way, where it was previously impossible
• The Walking Skeleton — we take the quickest path we possibly can to get to the end of the test

This is what I mean by concept of the Straight Line.

We could have just done: