Skip to content
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

Programming exercise: Instructor not informed that test case visibility changes do not take effect immediately #9013

Open
BBesrour opened this issue Jul 10, 2024 · 3 comments
Labels
client Pull requests that update TypeScript code. (Added Automatically!) discussion

Comments

@BBesrour
Copy link
Member

Describe the bug

As instructor, when you change the test cases visibility, you get a toast (notification) that the visibility of the test cases was successfully updated. This is misleading since students who submitted before this change can still see the test cases. The instructor should be informed that they have to re-trigger or re-evaluate the submissions

To Reproduce

Prerequisites:

  • Programming exercise with test case visibility set to always (can be changed under Grading)
  • 1 Student
  • 1 Instructor
  1. As student, submit something in the programming exercise
  2. Wait for the result and make sure that you can see the test cases
  3. As instructor, change the test case visibility to after due date
  4. As student, reload the page. you should still see the test cases even after the visibility was changed

Expected behavior

The instructor should be warned that students who already submitted can still see the test cases and that they have to re-evaluate or re-trigger the submissions

Screenshots

No response

Which version of Artemis are you seeing the problem on?

7.4.1 (4c5382b)

What browsers are you seeing the problem on?

Microsoft Edge

Additional context

No response

Relevant log output

No response

@BBesrour BBesrour added bug client Pull requests that update TypeScript code. (Added Automatically!) labels Jul 10, 2024
@Strohgelaender
Copy link
Contributor

There already is such an indicator on the top of the page that shows an exclamation mark if the changes are not in effect. Do you think that should be larger?

@BBesrour
Copy link
Member Author

@Strohgelaender Oh, I didn't notice it. Yes, I believe the warning should be more noticeable. Or to mention it in the notification you get after saving the changes. This is debatable though.

@BBesrour BBesrour added discussion and removed bug labels Jul 10, 2024
@JohannesStoehr
Copy link
Contributor

Re-evaluate will not help to hide feedback afterwards. While the new result will no longer show the feedback for that particular test case, the old results that are also accessible to the students still show the feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Pull requests that update TypeScript code. (Added Automatically!) discussion
Projects
None yet
Development

No branches or pull requests

3 participants