TutorFlow's assessment builder handles formats that go well beyond simple recall. For STEM subjects, technical courses, and any program where explanation matters as much as the answer, this means you can build rigorous assessments without assembling different tools.
Open-ended questions
Open-ended questions measure thinking, not just memory. They are the right choice when you want to know whether a learner can explain a concept, walk through a reasoning process, or apply knowledge to a new situation.
TutorFlow helps you generate open-ended questions that are scoped to a specific learning objective. Rather than broad prompts like "explain photosynthesis," use targeted questions like "explain why the rate of photosynthesis decreases at temperatures above 40°C."
The difference between a well-scoped open-ended question and a vague one is gradeability. A specific question has a clear set of elements that a good answer should include, which makes it much faster to evaluate.
STEM-specific formats
STEM assessments often need formats that recall questions cannot cover well. Here is how each maps onto TutorFlow:
| Need | How to build it |
|---|---|
| Formula and notation | Questions and answers render LaTeX, so equations appear as typeset math |
| Diagram or graph reading | Question text is Markdown, so place the figure in it and ask a multiple-choice or open-ended question about it |
| Show-your-work problems | An open-ended question; list the expected steps in its explanation and award the score by hand |
| Numerical answers | A fill-in-the-blank question for the final value, paired with an open-ended question for the method |
| Coding | A Coding Test lesson in the course, checked automatically against expected results |
Coding is the one case that leaves the test builder. A standalone test holds the five question types in the Tests overview; code is graded in a Coding Test lesson, where learners get a live editor and TutorFlow runs their solution. See Create Coding Courses.
Mixing question types in one assessment
The most effective STEM and technical assessments combine formats. A strong exam might include:
- A few multiple-choice and true/false questions for efficient coverage of factual knowledge
- Fill-in-the-blank items for key values and terms, graded automatically
- A diagram question with the figure in the prompt
- One or two open-ended questions asking learners to explain their reasoning
- For programming courses, a Coding Test lesson alongside the exam
This mix tests different layers of understanding and avoids the weakness of any single format. Recall questions miss reasoning, open-ended alone is slow to grade, and code alone misses conceptual understanding.
Best practices
- Align every question to a learning objective. If you cannot name the learning outcome a question tests, reconsider whether it belongs in the assessment.
- Avoid vague wording. "Discuss X" produces inconsistent responses. "Explain why X happens when Y increases" produces responses you can evaluate.
- Use coding tests for verification, not discovery. Learners should be able to write the solution based on what was taught, not figure out a new concept during the test.
- Mix objective and open-ended items. Objective questions give you consistent data across the cohort; open-ended questions give you depth on individual understanding.