Closed diananova closed 3 years ago
I'm not sure why the build/coverage report is failing. It doesn't seem related to my changes.
I'm also getting a different error locally.
Local:
FAILED tests/mentorship_relation/test_dao_creation.py::TestMentorshipRelationCreationDAO::test_dao_create_mentorship_relation_with_good_args_but_invalid_timestamp
Github:
FAILED tests/task_comments/test_api_get_task_comments.py::TestGetTaskCommentsApi::test_task_comment_listing_api_with_task_not_existing
I think you need to make a change to the existing test.
Merging #1134 (8d4fe3b) into develop (4193589) will not change coverage. The diff coverage is
100.00%
.
@@ Coverage Diff @@
## develop #1134 +/- ##
========================================
Coverage 92.91% 92.91%
========================================
Files 38 38
Lines 2062 2062
========================================
Hits 1916 1916
Misses 146 146
Impacted Files | Coverage Δ | |
---|---|---|
app/api/dao/user.py | 85.82% <100.00%> (ø) |
@epicadk @isabelcosta Ready for review. I didn't make any changes, the tests are flaky.
@epicadk @isabelcosta Ready for review. I didn't make any changes, the tests are flaky.
Which one exactly? This seems to be the first time it's happened.
@epicadk @isabelcosta Ready for review. I didn't make any changes, the tests are flaky.
Which one exactly? This seems to be the first time it's happened.
tests/task_comments/test_api_get_task_comments.py::TestGetTaskCommentsApi::test_task_comment_listing_api_with_task_not_existing.
It's an assertion error (we get code 403 instead of 404). Might have been a one time problem.
Interesting 🤔 I saw your changes yesterday, and thought you fixed the tests when you added str(i) while concatenating a string. The coverage report steps have been failing at times. So I would not worry about that, this should be an issue to fix aside from your PR @diananova :)
The changes made in this PR were tested locally. Following are the results:
Code review - Done
All possible responses (positive and negative tests) were tested as below:
GET /home
endpoint
Screenshot/gif: left (this branch deployed) / right (develop
branch deployed)
Expected Result: tasks returned are the oldest ones Actual Result: tasks returned are the most recent ones
Additional Comments: Tested on https://ms-backend-review-pr-1134.herokuapp.com/
Status of PR Changed to: Ready to Merge.
I'm not sure why the build/coverage report is failing. It doesn't seem related to my changes. I'm also getting a different error locally. Local:
FAILED tests/mentorship_relation/test_dao_creation.py::TestMentorshipRelationCreationDAO::test_dao_create_mentorship_relation_with_good_args_but_invalid_timestamp
Github:FAILED tests/task_comments/test_api_get_task_comments.py::TestGetTaskCommentsApi::test_task_comment_listing_api_with_task_not_existing
@diananova consider opening an issue for both errors including the build id in which they occur. If tests are flaky, we need to fix them too. :thinking:
Description
The achievements list retrieved from /home endpoint retrieves the latest three achievements, instead of the first three.
Fixes #393
Type of Change:
Code/Quality Assurance Only
How Has This Been Tested?
Checklist:
Code/Quality Assurance Only