Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#276 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
python
Ambito
frontend, testing-qa

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
HTML
Stelle
136
Fork
199
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di RunestoneInteractive/thinkcspy

Tutte le issue di RunestoneInteractive/thinkcspy

Issue simili

Altre issue su Web Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.