Sprint Challenge: Testing the Customer Management System
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- backend, documentation, testing-qa
Research direction
Start by locating the listed service implementations, repositories, and interfaces in the Sprint 4 customer management system, then review each public method and the order-placement flow. Done means tests and Javadoc cover the specified types, and logs show order identifiers, placement and final status, order-total debug details, and message-sent confirmation.
Written by the indexing model from the issue text.
Description
Sprint Challenge: Testing the Customer Management System
The code you write for this challenge is mandatory homework and should be completed and sent in a PR for review before class.
Bringing It All Together
Given the customer management system built in sprint 4 build unit tests for the major services and behaviours.
Requirements
Provide tests and javadoc for all the public methods of the following service implementations;
EmailMessageSenderSmsMessageSenderCustomerServiceOrderServiceReportingServiceInMemoryCustomerRepositoryInMemoryOrderRepository
Provide javadoc for all the implementations above and for the following interfaces;
CustomerRepositoryOrderRepositoryMessageSender
Add logging to your system so that;
- an identifier is assigned and recorded consistently in the logs for all parts of the order process
- you can see when an order is being placed and the final status
- debug level information is recorded when the order total is calculated
- the message sender confirms the message is sent
Submission & Review
Fork the coursework repo to your own GitHub account.
Make regular small commits with clear messages.
When you are ready, open a Pull Request to the CYF repo. Make sure you fill in the PR template provided.
A volunteer will review your submission and send you feedback.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Java
-
🎯 Topic Programming Fundamentals 🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
🎯 Topic Programming Fundamentals 🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
🎯 Topic Programming Fundamentals 🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 7 Core
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
🎯 Topic Programming Fundamentals 🏕 Priority Mandatory 📅 Sprint 7 🦑 Size Large Core
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
Sprint 6 Challenge Open🎯 Topic Programming Fundamentals 🏕 Priority Mandatory 📅 Sprint 6 🦑 Size Large Core
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in CodeYourFuture/Module-Java
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
punkpeye/mcp-remote#369 ·
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·
-
bug p:3-mid pydanty:bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
pydantic/pydantic-ai#8643 · 1 comment ·