-
Notifications
You must be signed in to change notification settings - Fork 4
Improve testing #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve testing #59
Conversation
Test Results355 tests +14 318 ✅ +14 10s ⏱️ ±0s For more details on these failures, see this check. Results for commit 521bc3f. ± Comparison against base commit 6ee1efc. This pull request removes 19 and adds 32 tests. Note that renamed tests count towards both. |
|
❌ Test or Coverage checks failed! Please check the workflow run for details. |
Qodana Community for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2024.3.4
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
Ahmedsayed0895
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job
This pull request introduces several new test cases and updates to improve test coverage and maintainability across the codebase. The changes include adding unit tests for subtask-related use cases, renaming a test class for consistency, and enhancing the
MapperKtTestto cover additional scenarios.New test cases for subtask-related use cases:
CreateSubTaskUseCaseTestto verify the creation of subtasks, including success, failure, and validation of the passedSubTaskobject. (src/test/kotlin/domain/usecases/sub_task/CreateSubTaskUseCaseTest.kt)DeleteSubTaskUseCaseTestto test the deletion of subtasks, ensuring correct behavior when the repository succeeds or fails, and validating the passed subtask ID. (src/test/kotlin/domain/usecases/sub_task/DeleteSubTaskUseCaseTest.kt)GetSubTasksByTaskIdUseCaseTestto test fetching subtasks by task ID, covering scenarios where the repository returns data, no data, and validating the task ID passed to the repository. (src/test/kotlin/domain/usecases/sub_task/GetSubTasksByTaskIdUseCaseTest.kt)UpdateSubTaskUseCaseTestto validate the update functionality for subtasks, including success, failure, and ensuring the correctSubTaskobject is passed to the repository. (src/test/kotlin/domain/usecases/sub_task/UpdateSubTaskUseCaseTest.kt)Enhancements to existing tests:
MapperKtTestby adding tests for converting aStringto aSubTaskand converting aTaskDtoto aTaskwith subtasks, improving coverage for mapping logic. (src/test/kotlin/data/mappers/MapperKtTest.kt)Test class renaming for consistency:
TaskStateDataSourceImplTesttoTaskStateRepositoryImplTestto align with the updated naming conventions of the repository layer. (src/test/kotlin/data/repositories/TaskStateRepositoryImplTest.kt)