What is the difference between "verification of correctness" and "validation of value" when assessing automated test suites in an Agile environment, and how can teams avoid a suite that is "green but useless"?

A A passing ("green") suite only confirms tests didn't fail — it doesn't confirm the tests assert meaningful, business-relevant behavior; mutation testing, code review of tests, and mapping tests to requirements help validate their value B A green suite always guarantees the software delivers business value with no further checks needed C Tests can never be reviewed for usefulness, only for syntax errors D Validation of value is identical to checking compile-time type safety