fssa-batch3 / fssa-batch3/sec_a_utchikanna.neelakandan__corejava_project_2
User module | Log in Feature
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
User Story
I want to access my account securely. If I need to log in, I should be able to do so. If my account information is incorrect, the system should let me know that I can't log in.
DAO:
- checkUserLogin()
Service:
- logInUser()
Service Test:
TestLoginFeature
- testLoginSuccess()
- testLoginFail()
Estimation:
2 hours
Flow Chart
graph TD
A[[Start]] --> B([Validate User])
B --> |Valid| C[(Retrieve User from Database)]
B --> |Invalid| E{{Validation Exception}}
C --> |User Not Found| F{{ServiceException}}
C --> |User Found| D([Check Password Match])
D --> |Returns User| I([Login Successful])
E --> G([Login Failed])
F --> G
D --> |Password Mismatch| G
G --> H[[End]]
I --> H
style I fill:#dfd,stroke:#333
style G fill:#fdd,stroke:#333
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Locate the DAO method checkUserLogin(), the service method logInUser(), and the TestLoginFeature test class. Start by tracing the login flow from validation through user retrieval and password matching. Done means testLoginSuccess() covers valid credentials and testLoginFail() covers invalid account information, including the stated validation and service failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100