test: Implement Tests for Edge Cases in Password Hashing and User Data

[benoit-bremaud]

Summary

This issue involves creating tests for edge cases related to password hashing and user data during the signup process. These tests are designed to ensure the robustness and security of the system under unusual or extreme conditions.

Context

Edge cases often reveal vulnerabilities or unexpected behavior in an application. By testing these scenarios, we can ensure that the password hashing mechanism and user data handling are resilient and secure. This includes handling maximum length constraints, special characters, and other unusual inputs.

Objectives

• Develop tests for edge cases related to password hashing and user data.
• Ensure the application handles these cases without storing passwords in plain text.
• Verify that user data is processed correctly, even with edge case inputs.

Acceptance Criteria

• The application must hash passwords correctly, even when they contain special characters or are at maximum length.
• User data should be validated and stored correctly, handling unusual inputs appropriately.
• Tests should ensure no security vulnerabilities are introduced through these edge cases.

Tasks

• [ ] Create and initialize a new working branch
  • Use the branch name following the conventions specified in the CONTRIBUTING.md guide.
  • Branch name format: test/issue-number-edge-cases
• [ ] Implement tests for the following edge cases:
  • [ ] Maximum password length (e.g., testing limits of the bcrypt algorithm)
  • [ ] Passwords with special characters (e.g., @#$%^&*)
  • [ ] Emails with uncommon formats (e.g., emails with multiple subdomains)
  • [ ] Usernames with special characters or spaces
  • [ ] Handling of very long usernames or email addresses
  • [ ] Passwords that are similar to common patterns (e.g., 123456, password1)
  • [ ] Signups with incomplete or missing optional data
• [ ] Verify that these edge cases do not result in plain text password storage.
• [ ] Ensure proper validation and error handling for unusual inputs.
• [ ] Write the commit message
  • Ensure the commit message follows the naming conventions as specified in the CONTRIBUTING.md guide.
• [ ] Create the Pull Request
  • Ensure the Pull Request follows the naming and description conventions as specified in the CONTRIBUTING.md guide.

Resources

• bcrypt Documentation
• Validation Best Practices

UML Diagrams References

• Use Case Diagram: To illustrate scenarios involving edge cases in user signup.
• Class Diagram: To reflect any necessary updates to the user model or related components.

Branch Name

test/issue-number-edge-cases

Complementary Suggested Tasks

• [ ] Update the user data validation logic if necessary to handle edge cases.
• [ ] Review the security implications of handling these edge cases.
• [ ] Update documentation to include information about supported input formats and validation rules.
• [ ] Perform additional testing to ensure no regressions occur due to these changes.