The "Expected" and "Actual" labels on autograded assertions for ActiveCode exercises are backwards
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- python
- 领域
- frontend, testing-qa
调研方向
Start by reproducing an ActiveCode exercise using self.assertIn and inspect the grader's "Expanding Differences" output. Trace the assertion-result display entry point and add or update a regression test if one exists; done means the expected and actual labels match the operands shown in the grader.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- HTML
- 星标
- 136
- 派生
- 199
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
RunestoneInteractive/thinkcspy 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
RunestoneInteractive/thinkcspy#281 · 1 条评论 ·
-
PythonTutor / CodeLens does not allow "import test"可能已有人在做 @dandrake 于 253 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 35/100
RunestoneInteractive/thinkcspy#279 · 4 条评论 ·
-
bug help wanted
难度 3/5 1-2 天 新手友好度 35/100
RunestoneInteractive/thinkcspy#278 · 6 条评论 ·
-
Hidden prefix visible to students in Active Code Exercises via Code Lens可能重新可做 @morozov-av 于 276 天前认领，目前没有进行中的 PR。 未关闭enhancement
RunestoneInteractive/thinkcspy#277 · 1 条评论 · 已指派 1 人 ·
-
难度 3/5 1-2 天 新手友好度 38/100
查看 RunestoneInteractive/thinkcspy 的全部 Issue
相似的 Issue
-
bug needs triage P3
难度 2/5 1-3 小时 新手友好度 76/100
pbakaus/impeccable#1143 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
status: waiting for maintainer
难度 2/5 1-3 小时 新手友好度 74/100
mui/material-ui#49547 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
rafaelmardojai/firefox-gnome-theme#1156 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
db-ux-design-system/core-web#8613 ·
维护者通常 1 天内回复