Lesson 1 of 88 min read
Trace one task from browser to database
A full-stack application has a presentation layer, an HTTP boundary, application rules and persistence. In this course the browser uses semantic HTML, CSS and native JavaScript; Spring Boot exposes a REST API; JPA writes synthetic tasks to an in-memory H2 database. The Taskboard is deliberately one shared development board, not a private multi-tenant product. Authentication limits callers but does not implement per-task ownership. It runs only on 127.0.0.1:8091 and resets data on restart. Follow the request: a form creates JSON, the controller validates it, the service applies rules, the repository saves an entity, and a DTO returns a stable shape. Do not treat the starter as production-ready or as a live SoftwareTestPilot service. Testing each boundary gives better diagnosis than one large click-through test.
Key takeaways
- 1Draw the request path and identify the validation and authentication boundaries.
- 2Your diagram separates HTTP, application rules and storage; it explicitly identifies the shared-board and memory-reset limitations.
- 3This is a local learning fixture, not a deployed private product.
Boundary or source example
Browser form -> POST /api/tasks -> TaskInput validation -> TaskService -> TaskRepository -> H2 -> TaskView -> DOM Development contract: title 1–120 characters, complete sets done=true, one shared board Deployment gaps: durable database, task ownership, operational monitoring, credential management
Go deeper
Expert notes beyond the basics
- 01
What to inspect
A full-stack application has a presentation layer, an HTTP boundary, application rules and persistence. In this course the browser uses semantic HTML, CSS and native JavaScript; Spring Boot exposes a REST API; JPA writes synthetic tasks to an in-memory H2 database. The Taskboard is deliberately one shared development board, not a private multi-tenant product. Authentication limits callers but does not implement per-task ownership. It runs only on 127.0.0.1:8091 and resets data on restart. Follow the request: a form creates JSON, the controller validates it, the service applies rules, the repository saves an entity, and a DTO returns a stable shape. Do not treat the starter as production-ready or as a live SoftwareTestPilot service. Testing each boundary gives better diagnosis than one large click-through test.
- 02
What the evidence means
Your diagram separates HTTP, application rules and storage; it explicitly identifies the shared-board and memory-reset limitations. Answer checks on this page do not execute Java.
Common mistakes to avoid
- - Confusing transport input with every database field.
- - Claiming a local snippet proves production security or durability.
Try it yourself
Draw the request path and identify the validation and authentication boundaries.
Write your answer on paper or in a sheet first, then compare.
Interview questions
How to answer like a confident QA engineer
- Q1
Which component receives the HTTP request?
Model answer
Controller. Your diagram separates HTTP, application rules and storage; it explicitly identifies the shared-board and memory-reset limitations.
- Q2
What does this starter not implement?
Model answer
It is one shared authenticated board with in-memory H2 data. It does not provide per-user task ownership, durable deployment, or production operational guarantees.
Knowledge check
+5 points
Which component receives the HTTP request?
