[Bugfix:Developer] Cypress test for autograding teams#12347
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12347 +/- ##
=========================================
Coverage 21.66% 21.66%
Complexity 9637 9637
=========================================
Files 268 268
Lines 36222 36222
Branches 487 487
=========================================
Hits 7847 7847
Misses 27892 27892
Partials 483 483
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Team autograding submission cypress tests now checks for the warning/error message to be displayed. Now working on regular solo autograding submissions.
Finished new tests for team and non team submissions, and uncommented older tests
There was a problem hiding this comment.
You should not need to copy frame.cpp and frame_hardcoded.cpp in order to test for autograding. The entire more_autograding_examples is copied into the /fixtures directory. Look at how https://github.com/Submitty/Submitty/blob/2d6d58826819e8165cbc197ce0222e2eced44db4/site/cypress/e2e/Cypress-Autograding-Tutorial/electronic_gradeable_tutorial.spec.js does it.
Tests now use submission files already present.
Thank you for pointing this out. I deleted the files I should not have copied over, and rewrote the tests to use copy_of_more_autograding_examples when checking for the "Something went wrong" banner. |
There was a problem hiding this comment.
This only checks if we can submit files and that nothing immediately went wrong. This is not sufficient to check if there is an actual error in autograding, as we don't get the result from the autograder and check that. The code that should be written should more closely follow https://github.com/Submitty/Submitty/blob/b823c839857cc491f287fc029aa0df809570e402/site/cypress/e2e/Cypress-Autograding-Development/electronic_gradeable_development.spec.js or https://github.com/Submitty/Submitty/blob/b823c839857cc491f287fc029aa0df809570e402/site/cypress/e2e/Cypress-Autograding-Tutorial/electronic_gradeable_tutorial.spec.js, using the functions to submit the files and check the results.
Team Autograding test now checks that all members see the changes made by re-uploads and regrades.
|
Hmmmm it looks like check_refresh is broken for team gradeables. If you get
|
Lowered the timeout time and added reload.
### Why is this Change Important & Necessary? Fixes Submitty#11920 An issue where team submissions would cause an error, resolved by PR Submitty#11919 . Currently there is no cypress test to catch the error in the future. ### What is the New Behavior? This test checks to make sure no such error happens again for team autograding submissions ### What steps should a reviewer take to reproduce or test the bug or new feature? Review the code and make sure the test is passing. ### Automated Testing & Documentation ### Other information This is not a breaking change. --------- Co-authored-by: Rkoester47 <[email protected]>
### Why is this Change Important & Necessary? Fixes Submitty#11920 An issue where team submissions would cause an error, resolved by PR Submitty#11919 . Currently there is no cypress test to catch the error in the future. ### What is the New Behavior? This test checks to make sure no such error happens again for team autograding submissions ### What steps should a reviewer take to reproduce or test the bug or new feature? Review the code and make sure the test is passing. ### Automated Testing & Documentation ### Other information This is not a breaking change. --------- Co-authored-by: Rkoester47 <[email protected]>
### Why is this Change Important & Necessary? Fixes Submitty#11920 An issue where team submissions would cause an error, resolved by PR Submitty#11919 . Currently there is no cypress test to catch the error in the future. ### What is the New Behavior? This test checks to make sure no such error happens again for team autograding submissions ### What steps should a reviewer take to reproduce or test the bug or new feature? Review the code and make sure the test is passing. ### Automated Testing & Documentation ### Other information This is not a breaking change. --------- Co-authored-by: Rkoester47 <[email protected]>
### Why is this Change Important & Necessary? Fixes Submitty#11920 An issue where team submissions would cause an error, resolved by PR Submitty#11919 . Currently there is no cypress test to catch the error in the future. ### What is the New Behavior? This test checks to make sure no such error happens again for team autograding submissions ### What steps should a reviewer take to reproduce or test the bug or new feature? Review the code and make sure the test is passing. ### Automated Testing & Documentation ### Other information This is not a breaking change. --------- Co-authored-by: Rkoester47 <[email protected]>
Why is this Change Important & Necessary?
Fixes #11920
An issue where team submissions would cause an error, resolved by PR #11919 . Currently there is no cypress test to catch the error in the future.
What is the New Behavior?
This test checks to make sure no such error happens again for team autograding submissions
What steps should a reviewer take to reproduce or test the bug or new feature?
Review the code and make sure the test is passing.
Automated Testing & Documentation
Other information
This is not a breaking change.