Understanding core definitions in an online exam system is essential for institutions, administrators, and decision makers. Below is a clear and concise glossary of terms you’ll commonly encounter in exam software settings.
User
A “User” is any member registered in the online exam system who is granted login access. They may or may not log in, or attempt any test. The number of users does not directly correlate with system load.
Test
A “Test” refers to the static question paper(s) created in the system. Tests alone generate no real-time load. They are separate from active use.
Test Attempt
A “Test Attempt” is when a user engages with a test in real time—submitting answers, navigating pages, etc. This is when resources are actually consumed. Test Attempts are considered the chargeable activity.
Login
A “Login” is when a user accesses the system. Logging in does not necessarily mean starting a test. Multiple logins (due to reconnection, etc.) in the same test session are not counted as additional Test Attempts.
Test Token
A “Test Token” is a unit of value assigned per test attempt. Some tests may cost more tokens depending on complexity, allowed bandwidth, or concurrent access. (Note: in newer cloud pricing models, the token concept may not apply.)
Load planning & scaling: Understanding that only Test Attempts (not Users or Tests) drive system load helps in infrastructure and capacity planning.
Cost & billing clarity: Charging models often rely on Test Attempts or Tokens rather than on user counts or number of created tests.
Fair usage & policy: Differentiating between logins, tests, and attempts helps set clearer usage policies, limits, or proctoring rules.
Reporting & analytics: Accurate reports depend on correct interpretation of these terms (e.g. How many users attempted vs how many users existed).
You may have 10,000 registered users in the system, but if only 2,000 ever take a test, then load and billing relate to 2,000 Test Attempts, not all 10,000 Users.
A teacher might create 50 distinct test papers—but if none of them are ever taken, they generate no traffic or cost.
A user logs in, loses connectivity, logs in again, and resumes the same test. The system should treat this as a single Test Attempt, not multiple.
Addmen Group Copyright 2024. All Rights Reserved.
