Skip to main content

​
What happens after you finish a test

When you finish a custom test, LearnTerms sends you to a results flow instead of simply telling you a score and stopping there. That design choice matters. The test is not just a checkpoint. It is supposed to generate your next review session.

​
The two main result views

The results page is built around two modes:
  1. Summary
  2. Review
You should use both.

​
What the summary is for

The summary view tells you how the attempt went at a glance. Depending on the attempt, that includes things like:
  • attempt status
  • timing or duration
  • pass threshold context
  • overall result signals
This is the right view for answering, “How did I do?” It is not the right view for answering, “What should I study next?”

​
What the review view is for

The review tab is where LearnTerms becomes useful again. Instead of flattening the attempt into one number, it lets you walk back through the questions and inspect what happened. This is where you can turn a test into a study plan.

​
Review filters that matter

The results flow includes filters for:
  • all
  • flagged
  • unanswered
  • incorrect
Each filter supports a different kind of cleanup.

​
flagged

Use this when you want to revisit the questions you already identified as shaky while taking the test.

​
unanswered

Use this when you ran out of time, skipped hard items, or mentally blanked on specific questions.

​
incorrect

Use this when you want the bluntest possible review set: what you actually missed.

​
Why unanswered questions deserve their own filter

Unanswered is not the same thing as incorrect. An unanswered question often means:
  • time pressure
  • uncertainty
  • poor pacing
  • weak confidence under exam conditions
That is a different problem from choosing the wrong answer after careful thought. LearnTerms separates them because they need different fixes.

​
What review shows for different question types

The review screen is not one-size-fits-all. It adapts to the question type:
  • multiple choice can show selected answers and correct answers
  • matching can show pair-by-pair review
  • fill in the blank can show response text and the accepted answer context
That makes the review usable instead of reducing everything to “right” or “wrong.”

​
Attachments and rationale during review

Review mode is also where solution-only attachments make more sense. If an image was held back during the live attempt, this is the moment where you should expect it to help rather than spoil the question. Rationales matter more after the test than during it. During the test, you are trying to perform. During review, you are trying to fix the model in your head.

​
How to use results well

​
If you barely passed

  • Review incorrect first.
  • Then review flagged.
  • Build a smaller second custom test from those weak areas.

​
If you ran out of time

  • Review unanswered first.
  • Check whether the issue was content knowledge or pacing.
  • Reduce question count or adjust timing on the next attempt.

​
If you scored well but felt shaky

  • Review flagged.
  • Look for patterns in why you flagged those items.
  • Use a second pass to convert uncertain wins into confident wins.

​
What the recent attempts list is for

The test builder page can also show recent attempts for the class. Those attempt records are useful when you want to:
  • resume an in-progress attempt
  • compare how several attempts felt
  • avoid rebuilding the same test mindset from scratch
Statuses like in_progress, submitted, timed_out, and abandoned tell you what happened without making you open every attempt.

​
Best habits after a test

  • Do not stop at the score.
  • Review the questions that changed your confidence, not just your percentage.
  • Treat unanswered as a pacing signal.
  • Treat flagged as an honesty signal.
  • Use the review flow to choose the next module or next custom test.