[Bugfix:Forum] Grader upduck message correction#11358
Conversation
…rading() in post upduckers check."
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11358 +/- ##
=========================================
Coverage 22.09% 22.09%
Complexity 8839 8839
=========================================
Files 246 246
Lines 31810 31810
Branches 79 79
=========================================
Hits 7029 7029
Misses 24705 24705
Partials 76 76
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
everything works, would you be able to add cypress tests to test that this functionality does not break? |
|
I verified the issue in main and tested the changes in this PR. Everything is functioning as expected, and I didn't run into any issues. |
you should approve it instead of adding a comment |
JManion32
left a comment
There was a problem hiding this comment.
I verified the issue in main and tested the changes in this PR. Everything is functioning as expected, and I didn't run into any issues.
can you just tell me how exactly I can do that, I am currently not familiar with how to create them, then I could add the cypress tests. |
https://submitty.org/developer/testing/cypress |
williamjallen
left a comment
There was a problem hiding this comment.
@williamschen23 is correct that we should have some Cypress tests for this functionality. Please test with students, limited access graders, full access graders, and instructors to make sure the functionality works, and continues to work, for all access levels.
Okay, will add Cypress tests for this. |
|
@williamjallen I'm doing more upducks refactor so it would make sense to add the grader's test to a new pr after the refactor is done, which I will do. |
williamjallen
left a comment
There was a problem hiding this comment.
Code looks good to me. @williamschen23 will write tests for this as part of the proposed refactor.
### Please check if the PR fulfills these requirements: * [ ] Tests for the changes have been added/updated (if possible) * [ ] Documentation has been updated/added if relevant * [ ] Screenshots are attached to Github PR if visual/UI changes were made ### What is the current behavior? <!-- List issue if it fixes/closes/implements one using the "Fixes #<number>" or "Closes #<number>" syntax --> Closes Submitty#11355 When the Grader upducked any thread or reply, there is the "liked by teaching staff" message but when the page is refreshed the message gets hidden as the accessFullGrading() was getting called, this prevented the message to be displayed when a Grader upducked the post/reply. [Screencast from 24-01-25 01:15:14 PM IST.webm](https://github.com/user-attachments/assets/cc703979-e53f-40ed-8f7b-22fd06e4d728) ### What is the new behavior? Now the accessGrading() is called. This displays the expected message when the Grader upducks the post/reply. [Screencast from 24-01-25 12:42:49 PM IST.webm](https://github.com/user-attachments/assets/71d3e7ea-3b17-43e1-a86b-da59bf6eb83f) ### Other information? <!-- Is this a breaking change? --> <!-- How did you test --> Co-authored-by: Williams Chen <[email protected]>
Please check if the PR fulfills these requirements:
What is the current behavior?
Closes #11355
When the Grader upducked any thread or reply, there is the "liked by teaching staff" message but when the page is refreshed the message gets hidden as the accessFullGrading() was getting called, this prevented the message to be displayed when a Grader upducked the post/reply.
Screencast.from.24-01-25.01.15.14.PM.IST.webm
What is the new behavior?
Now the accessGrading() is called. This displays the expected message when the Grader upducks the post/reply.
Screencast.from.24-01-25.12.42.49.PM.IST.webm
Other information?