A city team adds a new OCI Queue subscription to an existing case-intake service. Which test investment is the cheapest that would catch publish/consume/delete bugs?
Select an answer to reveal the explanation.
Short Explanation
Put the cheap spotlight where the change lives. A new Queue subscription wants an integration exercise of publish/consume/delete—not a pyramid-percentage flash card.
Full Explanation
Test methodology is choosing the cheapest test that would have caught the bug. Pure logic changes want a thick unit layer and a contract check if the interface moved. A new Queue subscription wants integration coverage of publish/consume/delete. A new API Gateway route wants a thin journey through that route—not a fixed percentage slogan.