Software Quality Plan

Software Quality Plan

Prepared by: Tuluyhan Sozen

Date: 19/11/2024

1.⁠ ⁠Code Review Process

Process:

• Codes are reviewed by different developers to maintain quality and consistency.
• If someone is working on a similar area of the code, they will take responsibility for reviewing related code changes. This approach helps team members become familiar with the methods and logic in those areas, improving collective understanding and collaboration.

Purpose of Reviews:

• Share knowledge and expertise among team members.
• Ensure adherence to coding standards and alignment with project goals.
• Identify and resolve potential bugs or inconsistencies early.

2.⁠ ⁠Unit Testing

Tools and Approach:

• We use Spring Boot tools to write and run unit tests.
• We design tests to validate the functionality of individual methods and components in isolation.
• We regularly calculate and monitor test coverage using IntelliJ tools to ensure completeness.

Timeline:

• Focus on developing unit tests until Milestone 2 to ensure all core functionalities are thoroughly validated.

3.⁠ ⁠Integration Testing

Approach:

• Conduct integration tests to validate the interaction between components and overall system workflows.
• Base these tests on user stories to ensure alignment with user requirements.

Timeline:

• Integration testing will start after the Customer Milestone #2.

4.⁠ ⁠API Testing with Postman

Process:

• Both the writer and the reviewer of a code segment will test the corresponding APIs using Postman.

5.⁠ ⁠Test Coverage and Quality Monitoring

Process:

• We use IntelliJ tools to calculate test coverage and identify areas requiring additional testing.
• Aim for comprehensive coverage of critical features and scenarios.
• Refine tests based on coverage insights to eliminate gaps and ensure robust validation.