Have you noticed the "v1" type of small code tests next to your test questions in the Task Bank or Test module? This is not a mysterious enigma or a system error. On the contrary, it is a useful feature that can greatly simplify your work with tests and their long-term management.

Each time you edit a test question in ELF, a new version with a higher number is automatically created. The second edit is marked as "v2," the next as "v3," and so on. This allows you to always see what has changed in the question and return to previous versions at any time. And you can, for example, prepare questions for next year without confusing current students.

However, sometimes the versioning of test questions can confuse teachers a little—typically when you edit a question but the change does not appear in the test. Why does this happen?

A specific version of the question is set manually in the test.

1. Sometimes, a test may be set to use a specific older version. If changes are not reflected in such a situation, it is necessary to switch to "always latest" in the test settings.
2. ELF protects ongoing attempts.
   If a student has already started the test, they are "locked" to the version of the questions that was current at the time the attempt began. The same behavior applies to the preview for teachers. To see the changes, you need to start a new attempt or preview.

But what if I need to reflect the test changes in a completed test attempt? Don't worry. ELF has a solution even for situations where you need to correct an incorrect test – the "recalculate grades" button, which updates the version of the question used and recalculates the results accordingly.

You can read more about how to work with test tasks in the user documentation.