Khangchendzonga State University: Presenting Testing Internship Findings in a Viva

To present testing internship findings in a viva, tell a short, evidence-backed story: what you tested, how you tested it, what you found, and what you would do next. Examiners rarely want a tour of every test you ran; they want to see that you understand why each test existed and can defend your conclusions. The outline, question bank and answer framework below are built for a 14-day internship and for students of Khangchendzonga State University, though they work for any viva.

What a viva examiner is really checking in a testing project

A testing internship is easy to inflate. Anyone can say “I found 25 bugs.” An examiner listening to you is usually probing three things:

• Ownership: did you design and execute the work, or copy it from a template?
• Reasoning: can you explain why you picked a test technique, a priority or a severity?
• Honesty about limits: do you know what you did not cover and why?

Prepare for these three, and most individual questions become variations on a theme.

Turn 14 days of testing into a defensible story

A two-week internship is short, so scope your claims to match. A realistic body of work might be one small application or feature, a set of test scenarios, a batch of executed test cases, a handful of well-written defect reports and a short summary. Claiming a full regression suite for a large product invites hard questions you cannot answer.

Before the viva, collect your evidence in one folder:

1. The requirement or feature description you tested against.
2. Your test scenarios and test cases, with IDs.
3. Execution results (pass, fail, blocked) with dates.
4. Defect reports with steps, expected result, actual result, and screenshots where useful.
5. A one-page summary of coverage, open defects and learnings.

If you joined the free two-week online internship at CareerSwami, keep your offer letter and completion certificate in the same folder, since examiners may ask for proof of the period and nature of the work. Do not describe the certificate as academic credit or a placement benefit unless your department has told you so in writing.

Five-minute viva presentation outline for a software testing internship

Five minutes is about 600 to 700 spoken words, or five to six slides. Use this timing table and rehearse with a timer.

Opening and closing lines you can adapt

• Opening: “Over 14 days I tested the login and registration flow of a sample web application, designed 30 test cases, and logged 6 defects.”
• Closing: “The main lesson was that most of my useful defects came from boundary inputs, so with more time I would extend data-driven testing to the remaining forms.”

Replace the numbers with your own. Never quote figures you cannot trace to your records.

An answer framework for defending any testing finding

Use a four-step structure for nearly every technical question: Claim, Evidence, Reason, Limit.

1. Claim: answer the question in one sentence.
2. Evidence: point to a specific test case ID, defect ID or screenshot.
3. Reason: explain the testing principle behind your choice.
4. Limit: mention what the finding does not prove.

The Limit step is what separates a confident tester from a defensive one. It shows you understand that testing reveals defects but cannot prove their absence.

Question bank for a software testing internship viva

Scope and planning questions

Technique and design questions

Defect and judgement questions

Reflection and limitation questions

• What would you do differently with another 14 days?
• What did you not test, and what risk does that leave?
• Could any of this be automated? Which part first, and why?
• What did you learn that a textbook did not teach you?

Worked example: defending one defect under follow-up questions

This example is illustrative. The application, defect and numbers are invented to show the method, and no tests were run for this article.

Suppose a student tested a registration form that accepts an age between 18 and 60. The student reports a defect: the form accepts 17.

Examiner: Tell me about your most serious defect.

Student (Claim): “The age field accepted 17 even though the requirement says the minimum is 18.”

Evidence: “This is test case TC-12, defect D-03. I entered 17, 18 and 19 as boundary values. 18 and 19 behaved correctly, 17 was accepted, and I have the screenshot.”

Reason: “I rated severity medium because invalid data enters the system, and priority high because the rule is a stated requirement.”

Limit: “I did not test the upper boundary of 60 on every browser, so I cannot say the maximum is enforced everywhere.”

Examiner: Why not severity high?

Student: “The application did not crash and no existing data was corrupted. If the age were used for a legal eligibility check, I would raise it.”

Notice that the student never bluffs, ties every statement to a record, and shows judgement rather than memorised definitions.

Preparing for a viva as a Khangchendzonga State University student

According to a Wikipedia summary of the university, Khangchendzonga State University is a state university at Tadong, Gangtok, established in 2018 as Sikkim State University and renamed in 2021. That description is an excerpt, so treat it as background and check the official site, which Wikipedia lists as ksus.ac.in, for current details.

What matters for your viva is something no public summary settles: how your own department treats internship and project work. Rules on duration, evaluation, documents required, and whether an online internship is acceptable can differ between programmes, and they may be set at university or college level. Do not assume that a viva format, a report template or a marking scheme from a friend in another course applies to you.

The practical consequence is that your five-minute outline is a preparation tool, not a guaranteed format. Your examiner may ask for a written report first, allow ten minutes, or expect a demonstration. Find out early so you can adjust the outline rather than rewrite it the night before.

Verification steps before you finalise your viva preparation

1. Ask your department coordinator in writing whether an online internship of 14 days is acceptable for your programme and semester.
2. Request the current internship, training or project-work regulation or guideline document, and note its year.
3. Ask what the viva format is: duration, panel, whether slides are allowed, and whether a report must be submitted beforehand.
4. Ask which documents to bring, such as the offer letter, completion certificate, report and mentor feedback.
5. Ask how the work is evaluated and whether the viva is internal or has an external examiner.
6. Check the official ksus.ac.in notices or your department notice board for submission dates, since the academic calendar was not confirmed here.

Rehearsal plan for the final three days before the viva

1. Day 1: build slides and the evidence folder; trace every number to a record.
2. Day 2: rehearse aloud with a timer; record yourself once and cut anything that runs over five minutes.
3. Day 3: have a friend ask questions from the bank above, interrupting with “why?” after each answer.

Self-check table: is your testing story ready to defend?

Phrases that keep you credible when you do not know the answer

• “I did not test that, but I would approach it by…”
• “In my 14 days I did not cover that area, and it is a gap in my results.”
• “I am not sure of the exact term, but the idea is…”

Examiners generally respond better to a clear admission followed by sound reasoning than to a confident guess that collapses on the next question.

Frequently Asked Questions

How long should a testing internship viva presentation be?

Aim for about five minutes unless your department states otherwise. Leave the rest of the time for questions, and confirm the exact format in writing beforehand.

How many test cases should I claim from a 14-day internship?

Claim only what your records show. A small, well-documented set with clear defects is more defensible than a large number you cannot explain. There is no universal target.

Should I show live testing or only slides?

Ask the panel in advance. If a demo is allowed, prepare one short reproduction of a single defect and keep screenshots as a backup in case the environment fails.

What if I found very few defects?

Present that honestly. Explain your coverage, techniques and what the absence of defects does and does not show. A low defect count is acceptable if your reasoning and limits are clear.

How do I explain severity versus priority simply?

Severity describes how badly a defect affects the system; priority describes how soon it should be fixed. Use one example from your own work where the two differed.

Do I need to mention automation if I only tested manually?

No, but be ready for the question. Say your work was manual, then name one repetitive part, such as boundary checks on a form, that could be automated and why.

Can I use my CareerSwami internship work as my viva project?

Whether it is accepted for your viva is your department’s decision, so ask your coordinator in writing before building your presentation around it. If accepted, bring the offer letter, completion certificate and your test records.

What should I bring to the viva?

Bring a printed or digital report, your evidence folder, the offer letter and completion certificate, and any mentor feedback. Confirm with your department whether additional documents are required.