-
Notifications
You must be signed in to change notification settings - Fork 18
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
The problem of easy problems #62
Comments
What are the kind of mistakes you see students do? I can think of several possible errors:
I can see how to catch 1&2 with a reference implementation. To check for the 3rd one a standard unit test can be used or using pybryt by adding to the reference implementation the line: and when running students solutions wrapping their function with |
Note to self: As discussed in the tech meeting, pre-processing footprints depending on whether values come from the variable with the same name could be one way forward. @rolotumazi has possibly an even better solution and he will summarise it in this issue soon. |
So, I'll briefly outline what me and @marijanbeg discussed after a good tech meeting. |
Is your feature request related to a problem? Please describe.
We demonstrate the problem we encounter in example
01-easy-problems
in https://github.com/marijanbeg/pybryt-examplesSummary
A student has an exercise to write a function with signature
maximum(a)
, which finds and returns the largest element in a lista
. The solution we expect in a beginner-level Python course is:The reference solution would be:
However, whatever the solution of the student's code is, we are not able to validate it because all elements of the input list are in the footprint anyway because of the
for i in a
loop, which validates any PyBryt annotation from the reference solution. Exercises like this are very common in beginner-level coding exercises where feedback on the student's implementation (PyBryt's main power) is essential.The text was updated successfully, but these errors were encountered: