Which level exercises an assembled application from choosing a book through checkout to receipt?

• End-to-end journey tests
• Isolated totals-function tests
• Payment-adapter integration tests

Using this lesson's terms, which level checks a small piece of logic in isolation from external services?

• Journey tests
• Integration tests
• Isolated unit tests

An integration test can exercise a real exchange that an isolated test using a dependency double does not exercise.

Every arithmetic check runs through a slow browser checkout. What problem can this strategy create?

• Delayed feedback and harder fault location
• Reduced need to choose arithmetic inputs
• More precise failure messages from spanning more components

A payment adapter sends a request format the provider rejects. Which focused check exercises that real boundary without charging live customers?

• An adapter test using a hand-written response stub
• An integration check using the provider's test environment
• A contract check using a local provider imitation

The suspected defect is entirely in a totals function's arithmetic. Which check most directly exercises that calculation?

• A browser test of checkout's displayed total
• An integration check of totals and payment
• An isolated test of the totals function

A team deletes focused tests and moves every check into slow journey tests. Which revision better matches checks to risks?

• Replace the journeys with unit checks on their component functions
• Restore focused checks and retain journeys for workflow risks
• Speed up the browser suite and keep arithmetic checks there

You run the real discount, refund and receipt components together without a browser to check their combination. Using this lesson's terms, what is this?

• An integration test of selected components
• A unit test with dependency doubles
• A unit test of discount logic