Organizing the Code
Before we finish this session, let’s be kind to our future selves and tidy up a little. As we worked, we just created everything we needed inline in our src/test/java/nicebank/Steps.java file. We’ll move most of that stuff out of there, and put it into a more conventional place. Here’s a list of what we’d like to fix:
-
The application’s domain model classes should move into the src/main/java tree.
-
The KnowsTheDomain class can move into its own file.
-
The Steps file can be split to organize the step definitions better. This is arguably unnecessary for a project with only three step definitions, but we’ll do it anyway to illustrate how we’d do this on a bigger project.
Separating the Application Code
It’s conventional ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access