At this level of analysis, we may consider a test case as the representation in code of all scenarios that pertain to a certain feature. Each test, in turn, represents a specific scenario. The term use case comes from Alistair Cockburn's classic Writing Effective Use Cases. In our context, you can consider a use case as the system-level description of a feature, a set of instructions that have as an outcome the user story's success or failure, depending on the given preconditions (the current system state).
As we started our feature enumeration by working on check available groceries, we will begin adding tests for that.
Each test case requires its own subproject to be run as an executable. This means that ...
