⚡
How Points Work
Every test you complete earns you points. Here's exactly how your score is calculated — step by step.
Step 1 — Test Case Difficulty
📋
Each test case has a difficulty level
The harder the test, the more base points you earn just for completing it.
1 pt
Level 1 — Simple
Straightforward steps, one expected outcome. Like checking if a button opens a form.
3 pts
Level 2 — Moderate
Multiple steps, some validation checks. Like filling a form with required fields.
5 pts
Level 3 — Complex
Cross-module checks, business rules involved. Like payroll integration with employee grades.
10 pts
Level 4 — Expert
Multi-system validation, compliance rules, or security edge cases. Requires deep knowledge.
Step 2 — Bug Discovered (optional)
🐛
Found a bug? Report it and earn bonus points
When a test fails because something in the system is broken, you classify how serious the bug is. Extra points are added on top of your difficulty points.
🎨
UI Bug
+2 pts
Visual issues — wrong colour, misaligned button, label typo. The system still works but looks broken.
⚙️
Functional Bug
+10 pts
A feature does the wrong thing — form saves with missing data, filter returns wrong results.
🚨
Critical Bug
+25 pts
System crashes, data is lost, security is broken, or payroll calculates incorrectly.
💡 If a test simply passes — no bug found — no bonus points are added. That's fine! Passing tests are just as valuable.
Step 3 — Your Raw Score
➕
Difficulty points + Bug points = Raw score
These two numbers are added together the moment you submit your result. This is called your Auto Points.
Difficulty
3 pts
Level 2 test
+
Bug Found
10 pts
Functional bug
=
Raw Score
13 pts
Pending approval
Step 4 — Quality Multiplier
✖
Your raw score is multiplied based on evidence quality
When you report a Fail or Blocked result, the system checks: did you upload a screenshot?
Good evidence = higher score. Missing evidence = lower score.
0.5×
⚠ Missing Evidence
You reported a Fail or Blocked result but did not attach a screenshot. Your score is halved as a reminder that evidence matters.
1.0×
Standard
All your results are Pass or Skipped — no failures to prove. Score stays as-is. No penalty, no bonus.
1.2×
⭐ Full Evidence
Every Fail or Blocked result has a screenshot attached. You went the extra mile — your score is boosted by 20%.
💡 The multiplier looks at all your submissions together — not just one test at a time.
Step 5 — Admin Review
👁
Admin checks your work before points are confirmed
Your score is not final until an admin reviews and approves it. They may adjust the points up or down if needed.
✅
You submit your result
Auto Points are calculated instantly and sit in Pending state.
🔍
Admin reviews your submission
They check your actual result, comments, screenshots, and bug reference.
⚙
Admin may adjust points
If the admin disagrees with the auto score, they can set a custom value and leave a reason.
🏆
Points confirmed — leaderboard updates
Your final score appears on the Contributions page and leaderboard.
✗
Or — Rejected
If the submission doesn't meet quality standards, the admin rejects it with a reason. 0 points awarded.
The Full Formula
Admin Bonus Points
🎁
Starting Balance — Granted by Admin
When your account is created, the admin can grant you a bonus starting balance.
These points are added directly to your total score on top of everything you earn through testing.
They never expire and don't require approval — they're yours immediately.
Think of it like a head-start reward for joining the testing team.
Tips to Maximise Your Score
📸
Always attach a screenshot for failures
This alone is the difference between 0.5× and 1.2× — a 2.4× swing in your final score. Never skip it.
🐛
Classify bugs accurately
Don't over-claim Critical for a UI glitch. Honest reporting builds trust and admin is less likely to override your score downward.
📝
Write a clear Actual Result
Admin approves faster when your comments explain exactly what you saw. Vague submissions get reviewed more carefully.
⭐
Pick harder test cases
Level 4 cases give 10 pts just for completion — 10× more than a Level 1. If you have the knowledge, tackle the hard ones.
⏱
Meet your due dates
Overdue assignments are flagged to the admin. Consistent, on-time delivery reflects well during the review process.
🔗
Always add a bug reference
A JIRA/DevOps ticket number in the Bug Reference field shows you've gone beyond just marking something as failed.
Quick Reference
| What |
Value |
When |
| Level 1 test completed |
+1 pt |
Always |
| Level 2 test completed |
+3 pts |
Always |
| Level 3 test completed |
+5 pts |
Always |
| Level 4 test completed |
+10 pts |
Always |
| UI bug reported |
+2 pts |
On Fail / Blocked |
| Functional bug reported |
+10 pts |
On Fail / Blocked |
| Critical bug reported |
+25 pts |
On Fail / Blocked |
| Missing screenshot on failure |
× 0.5 |
Penalty |
| All failures have screenshots |
× 1.2 |
Bonus |
| Admin bonus (starting balance) |
Admin set |
Immediate |
| Admin override (up or down) |
Custom |
On approval |