The "Expected" and "Actual" labels on autograded assertions for ActiveCode exercises are backwards

[norkish]

Please check the current issues Many bug reports are duplicates, this just creates more work for us. Searching the issues first may give you your answer or a workaround! If not adding new information to an existing report is much more helpful than a new report.

What Course are you in
Knowing the course will help us a lot

hhtlacs

What Page were you on

What is your username
norkish

Describe the bug
A clear and concise description of what what you were trying to accomplish and what went wrong. Vague statements like X does not work are not helpful. Imagine if one of your students sent you an email that said, "My program doesn't work, whats wrong with it?" Could you help them with only that to go on?

When I create ActiveCode exercises and use the self.assertIn, the order of operands seems to want "expected" first and then "actual" second. But when the grader reports the test results and allows "Expanding Differences", these two labels are swapped (i.e., it shows the submission derived from the student's solution as the "expected" and the part that my test checks should be "in" as the "actual")

Traceback
If you got here through the Bug Report page and there was a stack trace, please paste it here

Javascript Errors
Many many errors can be quickly diagnosed from the Javascript Console error log. On Chrome this is View --> Developer --> Javascript Console, on Safari ⌥⌘i or Develop --> Show Web Inspector on Firefox Tools --> Web Developer --> Toggle Tools

[bnmnetp]

Hmm, This is the code for assertIn

def assertIn(self, a, b, feedback=""):
        res = a in b
        if not res and feedback == "":
            feedback = "Expected %s to be in %s" % (str(a),str(b))
        self.appendResult(res, a, b, feedback)

It looks fine to me. The language of expected and actual feel a little odd to me for assertIn. But its served us well for 12 years.