Project Tooling · interview question

If you wrote a test around project metadata, what should the test prove first?

Multiple choiceMediumchapter-6-curatedpremiumproject-toolingproject-metadata

toml

[project]
name = "order-ops"
version = "0.1.0"
dependencies = ["httpx", "pydantic"]

That the rule behaves correctly at the boundary cases the lesson is trying to make explicit.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Keep project metadata implicit so the script stays short and hope the next engineer infers the rule.Solve the symptom with comments only and avoid changing the code shape around project metadata.

Answer and explanation

Correct answer

A. That the rule behaves correctly at the boundary cases the lesson is trying to make explicit.

Why

Good tests make the design safer to change because they lock in the meaningful behavior rather than surface-level implementation details.

Test yourself on Project Tooling

A free test with instant, explained results. No account needed.

Start free test

All Project Tooling questions →

If you wrote a test around project metadata, what should the test prove first?

Correct answer

Why

More Project Tooling questions