Karnavati University Design Students: Usability Testing as a Software Testing Internship Entry

Yes, usability testing is a credible way into a software testing internship, and design students are well placed for it. You already know how to observe users, spot friction and justify a judgement; what you add is the testers’ habit of writing findings that a developer can reproduce, rank and fix. This article gives you a moderated test script, a heuristic evaluation scorecard, a reporting template and a 14-day plan.

Why usability testing counts as software testing

Software testing is not only about checking that a button triggers the right function. It also asks whether a real person can finish a task with the product. A checkout that works technically but hides the “Apply coupon” field still fails the user. Teams therefore run functional testing, regression testing, performance testing and usability testing side by side, and the last one is where design training transfers most directly.

The skills overlap more than most design students expect:

• Observation: watching where a participant hesitates is the same skill as noticing where a build misbehaves.
• Task analysis: breaking a journey into steps is how testers design test cases.
• Critique: explaining why something is a problem, not just that you dislike it.
• Documentation: annotated screens and clear sequences are exactly what a good bug report needs.

The gap is mostly vocabulary and format. Designers say “this feels confusing”; testers write “On step 3, a first-time user could not find the Submit control; 4 of 5 participants hesitated for more than ten seconds.” This article closes that gap.

What Karnavati University design students should know first

The university homepage describes Karnavati as a private university offering programmes across design, law, business management, liberal arts, mass communication, computer science, dentistry and commerce, and lists Unitedworld Institute of Design and Unitedworld Institute of Technology (UIT) among its institutes. That mix is useful for you. A design student sits close to a technology institute, so you can find classmates who build software and who need exactly the usability feedback you can give. Treat them as your first test participants and your first “development team”.

The Placement Cell page (last updated around 2024, so check the current version) lists career guidance, skill development, internship opportunities and industry connect among its objectives, and says it keeps partnerships with organisations for internship experiences. It does not publish internship rules, named recruiters or contact details.

What this means in practice: nothing public tells you whether an online internship in software testing fits your programme’s requirements, how it is recorded, or whether it carries credit. Do not assume either way. Use the verification steps near the end of this article before you plan around it.

A 14-day plan from usability tester to testing intern

The free two-week online internship from CareerSwami runs 14 days, offers a free offer letter and a free completion certificate after successful completion, and has 26 tracks. If you choose a software testing track, the plan below shows how to spend the time on usability work. It is a suggested structure, not the official curriculum of any track.

Moderated usability test script you can read aloud

Run each session in about 20 to 25 minutes. Use the same wording every time so results can be compared. Bracketed text is for you to fill in.

Before the session

• Choose a product you do not own, or one a classmate has agreed to share, so nobody is defensive.
• Write 3 or 4 tasks as goals, not instructions. “Find out whether the library is open on Sunday” is a goal; “Click Contact” is an instruction.
• Prepare a notes sheet with columns for task, time, errors, quotes and your severity guess.
• Test on the device participants actually use, usually a phone.

Spoken script

1. Welcome: “Thanks for helping. We are testing the [product], not you. Nothing you do is wrong, and the more honestly you react, the more useful it is.”
2. Consent: “I will take notes on what you do and say. Your name will not appear in the report. Is that fine? You can stop at any time.”
3. Think aloud: “Please say out loud what you are looking at and what you expect to happen. I may stay quiet, because I want to see what you would do alone.”
4. Warm-up question: “How often do you use apps or sites like this?”
5. Task prompt: “Imagine you want to [goal]. Please start here and show me how you would do it.”
6. Neutral nudges only: if they pause, ask “What are you thinking now?” Never say “try the menu”.
7. After each task: “How easy or difficult was that, from 1 (very difficult) to 5 (very easy)? Why?”
8. Close: “What was the most frustrating part? What worked well? Anything you expected that was missing?”
9. Thank them and note anything said after the recording or notes stopped.

What to record for every task

• Completed unaided, completed with a hint, or failed.
• Time taken, using a phone timer.
• Wrong taps, backtracking and moments of hesitation.
• Exact quotes in the participant’s words.

Heuristic evaluation scorecard based on Nielsen’s ten principles

A heuristic evaluation is an expert review where you inspect an interface against recognised principles. The ten heuristics below are the widely used set from Jakob Nielsen. Score each from 0 to 4 for the severity of problems you found (0 means no problem, 4 means a usability catastrophe), and write the screen where you saw it.

Add one more column set if you want to go beyond design critique: accessibility checks such as text contrast, tap-target size and whether form fields have visible labels. Those are concrete, testable and welcomed by development teams.

Severity ratings that developers will not argue with

Developers push back on vague severity. Tie every rating to user impact and frequency, and keep the scale short.

• Critical: users cannot complete a core task (cannot pay, cannot log in).
• Major: users complete the task but only after serious struggle or with help.
• Minor: noticeable friction that most users recover from quickly.
• Cosmetic: polish issue with no effect on task success.

Keep severity (how bad for the user) separate from priority (what the team fixes first). Testers recommend severity; the product owner usually decides priority.

Worked illustrative example: a college event registration page

The following example is invented for teaching. No real product was tested and no results were measured.

Imagine a student-run fest registration page. The task is “Register for the poster-design workshop and confirm your place.” Five hypothetical participants attempt it on phones.

The double tap in row two is the interesting one. A designer sees confusion; a tester asks whether the double tap created two registrations. That follow-up question is what turns a usability note into a functional defect, and it is the mindset interviewers look for.

Reporting usability findings to developers

A finding is useful only if someone else can reproduce it and understand why it matters. Use one report per issue with this structure.

1. Title: specific and short. “No loading feedback after tapping Register on slow network.”
2. Environment: device, operating system, browser or app version, network, date.
3. Steps to reproduce: numbered, starting from a known state.
4. Expected result: what a user would reasonably anticipate.
5. Actual result: what happened, with a screenshot or short screen recording.
6. User impact: how many participants, and what it cost them (time, errors, abandonment).
7. Severity: from the scale above.
8. Suggested direction (optional): an idea, clearly framed as a suggestion, since the developer owns the fix.

Illustrative report

Title: No feedback after tapping Register; users tap twice
Environment: Android phone, Chrome, mobile data, [date]
Steps:
1. Open the workshop page
2. Select "Poster Design"
3. Tap Register
Expected: Button shows a loading state or confirmation within 1 second
Actual: No visible change for about 3 seconds
Impact: 2 of 5 participants tapped again; check for duplicate entries
Severity: Major
Evidence: screen recording attached

Tone that gets bugs fixed

• Describe behaviour, not people or the quality of the work.
• Lead with evidence, then opinion.
• Group related items so a developer sees five themes, not fifty lines.
• Say what you did not test, so nobody assumes full coverage.

How to present this work to a testing internship or interviewer

A two-page case study beats a long list of claims. Include the product and tasks, your method, the number of participants, a ranked findings table, two or three full defect reports, and a short reflection on what you would retest. Be honest about scale: five informal sessions are a small sample, and saying so reads as maturity, not weakness.

Learn a few testing terms well enough to use them correctly: test case, regression, smoke test, reproducibility, severity and priority. Then try one basic skill beyond usability, such as writing five functional test cases for the same page. That shows you can move from design critique into general testing.

Karnavati University and your testing internship: steps to verify before you commit

Public pages do not state the rules for online internships, so settle these in writing before you plan your semester around one. The checklist below is a practical order of enquiry.

1. Open the Placement Cell page and note any current contact details or notices, since the page may be out of date.
2. Email or visit the Placement Cell and ask: “Do you accept self-arranged online internships, and what documents do you need?”
3. Ask your programme coordinator in the Unitedworld Institute of Design (or your own institute) whether internship or industrial training rules apply to your batch, and request the current scheme or regulation document.
4. Ask whether an offer letter and completion certificate from an online internship are recorded, and in what format.
5. Ask whether credit, evaluation or a report submission is attached to internships. Do not assume credit from any internship unless the university confirms it.
6. Check with a faculty member at the Unitedworld Institute of Technology whether any project needs a usability tester; a real project makes a stronger portfolio piece.

Frequently Asked Questions

Can a design student really get a software testing internship through usability testing?

It is a legitimate starting point, especially for roles in UX testing, QA support and product teams. It works best when you pair it with basic testing vocabulary and well-written defect reports, so you are not seen as only a visual critic.

How many participants do I need for a usability test?

Small tests of around five people often surface the most obvious problems, which suits a 14-day plan. Treat the results as qualitative evidence, not statistics, and say so in your report.

What is the difference between a heuristic evaluation and a usability test?

A heuristic evaluation is an expert inspection against known principles, done without users. A usability test watches real people attempt tasks. Using both gives you opinion backed by observed behaviour.

How do I decide whether a usability problem is a bug?

Ask whether the product behaves differently from what was intended or documented. If it works as designed but confuses users, report it as a usability issue and say so. If it breaks, duplicates data or blocks a task, report it as a defect.

Do I need coding skills to start usability testing?

No. You need a clear method, careful notes and reproducible reports. Basic familiarity with browser developer tools helps later but is not required to begin.

Which tools can a beginner use to record sessions?

The built-in screen recorder on your phone or laptop, a spreadsheet for scoring and a shared document for reports are enough. Always get a participant’s consent before recording.

Can I use the CareerSwami internship to practise this workflow?

Yes, if you pick a software testing track, you can build your usability testing case study during the free 14-day online internship. Confirm separately with your university how it is treated, as the internship does not itself promise credit, placement or a stipend.

How do I handle a developer who says a finding is just my opinion?

Return to evidence: show the recording, the number of participants affected and the reproduction steps. Then link the issue to a named heuristic or an accessibility check, so the discussion is about the user’s task, not taste.