Guru Kashi University Students: Preparing for a Practical Test Round in Intern Selection

You prepare for a practical test round in software testing by practising the exact things it measures: turning a vague requirement into test cases, finding defects in a small application, and writing a bug report someone else can reproduce. Fourteen focused days is enough to get comfortable, provided you work against a clock and a rubric rather than just reading theory. This guide gives you a timed mock assignment, a marking rubric, the traps that cost candidates marks, and a day-by-day schedule.

What a software testing practical round usually checks

Formats differ between organisations, and no single format can be assumed. Still, practical rounds for testing interns tend to combine a few tasks. Treat the list below as a preparation model, not a description of any specific employer.

• Test design: given a short requirement (a login page, a form, a cart), write test cases covering valid, invalid and boundary inputs.
• Exploratory testing: use a small web page or app for 20 to 30 minutes and report what breaks.
• Bug reporting: write clear reports with steps, expected result, actual result and severity.
• Reasoning aloud: explain why you chose a case, or how you would prioritise limited time.
• Basic tooling: browser developer tools, a spreadsheet for test cases, sometimes a simple SQL query or API call in a tool such as Postman.

Evaluators generally want evidence of thinking. A shorter set of well-chosen, well-explained cases beats a long list of near-duplicates.

A 90-minute mock testing assignment you can run at home

This assignment is illustrative: it was written for practice, and nothing here has been executed against a real application. Set a timer, work alone, and do not look anything up until the time ends.

The scenario

A small college club is launching a “Event Registration” page. The requirement reads:

• The form has Full Name, Email, Mobile Number (10 digits), Year of Study (dropdown: 1 to 4) and a “Register” button.
• Name is mandatory, 2 to 50 characters, letters and spaces only.
• Email is mandatory and must be valid.
• Mobile number is mandatory, exactly 10 digits, starting with 6, 7, 8 or 9.
• One registration is allowed per email address.
• After success, the page shows “Registration confirmed” and a reference number.

The timed tasks

Sample cases to show the expected depth

Illustrative rows for the mobile number field:

A sample bug report format

Title: Duplicate email accepted when letter case differs
Environment: Chrome (latest), Windows 11, practice build
Steps:
1. Register with riya@example.com
2. Open the form again
3. Register with RIYA@example.com
Expected: "Email already registered" message
Actual: Second registration confirmed with a new reference number
Severity: Medium (breaks one-registration-per-email rule)
Attachment: screenshot of both confirmations

This report is invented for practice. Notice that it states a single problem, gives exact data, and links the defect to a stated rule.

Marking rubric for scoring your own mock attempt

Score yourself honestly, or swap papers with a friend. The weights are a practice device of our own design, not an official scheme from any recruiter.

A score of 70 or more suggests you are ready for a real round. Below 50, repeat the same scenario with a different feature (a password reset form works well) before moving on.

Traps that cost marks in testing practical rounds

• Writing only happy-path cases. Evaluators expect negative and boundary thinking.
• Duplicate cases. Ten cases that all check “valid name” show padding, not skill. Group inputs into equivalence classes.
• Vague expected results. “Works properly” cannot be marked pass or fail.
• Bundled bugs. One report with four problems is hard to triage. Split them.
• Confusing severity and priority. Severity is impact on the system; priority is how soon it should be fixed. A spelling error on the home page can be low severity but high priority.
• Silent assumptions. If the requirement is unclear, write your assumption down instead of guessing in silence.
• Ignoring the clock. An unfinished bug report scores less than a finished, shorter one.
• Reporting a feature that was never specified as a defect. Frame it as an observation or a question when the requirement is silent.
• Skipping environment details. Browser, device and build matter for reproduction.

Guru Kashi University students: testing practice and the internship window

The university’s homepage describes it as a UGC-recognised private university in Punjab offering undergraduate, postgraduate and doctoral courses. Its Department of Training and Placement runs soft-skills and aptitude-test training (page dated 2025), which is useful for the reasoning and communication side of a selection round. That page gives no figures, so do not assume anything about outcomes from it.

For B.Tech CSE students, the 2024-25 scheme (BCS24) lists a 2-credit Institutional Training course (BCS308) in Semester III and an Industrial Training course (BCS719) in Semester VII. In that booklet the Semester VII entry shows 4 credits in the scheme table but 2 credits and 60 hours in the course detail, so the two entries conflict. The text of that booklet gives learning outcomes only; it does not state evaluation rules, required documents or whether an online internship is accepted. Newer 2026-27 booklets exist, so your own batch may differ.

Timing matters as well. The 2026-27 academic calendar shows the odd semester’s last instruction day on 23 November 2026 and end-semester theory exams from 2 to 30 December 2026. The even semester starts on 4 January 2027. A 14-day practice plan started now would therefore collide with exam preparation unless you keep sessions short.

The helpline page names the Assistant Director, Training and Placement, as the contact for placement queries and internship coordination (this comes from a page excerpt, so check it is current).

Verification steps for GKU students before you rely on a testing internship

1. Open the booklet for your exact admission year and programme, and note the internship or training course code, credits and semester.
2. Email your department coordinator asking in writing whether an online, self-arranged internship of 14 days can be used for that course, and what duration is required.
3. Ask which documents are needed (certificate, report, mentor letter) and the evaluation format.
4. Contact the Training and Placement office through the helpline page and ask whether offer letters from outside programmes need prior approval.
5. Keep the reply emails; they are your evidence if a rule is questioned later.

A 14-day preparation schedule for the testing practical round

If you plan to apply for the free two-week online internship at CareerSwami, which offers a free offer letter and a free completion certificate after successful completion, you can use this schedule as your pre-application practice. It assumes 1.5 to 2 hours a day, reduced on exam-heavy days.

Worked scoring example for one mock attempt

This is an illustrative scenario, not a real student. Aman completes the Event Registration mock. He writes 24 cases, but 15 cover name and email only and none cover the one-registration-per-email rule. He prioritises with reasons, finds one exploratory issue (the Register button can be double-clicked), and writes two reports, one of which combines two defects.

His next step is clear: build a field-by-rule checklist so no requirement line goes untested, and split every bundled report. A repeat mock on a different form should show whether the fix worked.

How to prepare on the day of the round

• Have a spreadsheet template ready with columns for ID, title, steps, data, expected result and type.
• Keep a bug report template saved in a notes file.
• Check your internet, browser version and screen-sharing setup an hour earlier.
• Read the whole brief once before writing anything, and note the time limit.
• Reserve the last five minutes to re-read your expected results and reports.

Frequently Asked Questions

How many test cases should I write in a timed practical round?

Quality and coverage matter more than count. For a small form, 15 to 25 well-differentiated cases across valid, invalid, boundary and duplicate scenarios is a sensible target in 30 minutes. If the brief gives a number, follow it exactly.

Do I need to know automation tools like Selenium for an intern selection round?

Not necessarily. Many intern rounds focus on manual testing: test design, exploration and bug reports. If the brief mentions automation, learn the basics, but do not neglect manual fundamentals to chase it.

What if the requirement is unclear or contradictory?

Write the question down, state the assumption you will use, and continue. Showing that you noticed the gap is often credited, while silently guessing is not.

How do I choose which test cases to run first?

Rank by risk: features that affect the most users, handle money or personal data, or are most likely to fail. Add a one-line reason beside each. Core flows such as registration success and mandatory-field checks usually come first.

What is the difference between severity and priority in a bug report as a Guru Kashi University student?

Severity describes the technical impact of the defect. Priority describes how urgently the business wants it fixed. They often agree, but not always, so state them separately.

Can I use a practice website for exploratory testing during preparation?

Yes, provided the site is meant for practice or you own it. Do not test live systems you have no permission to test, and avoid anything resembling security probing without authorisation.

Will a short online testing internship be accepted by my GKU department for training credit?

That cannot be assumed. The booklets reviewed list training courses but do not state rules on online internships or documents, so ask your department coordinator in writing and keep the reply.

How should a free two-week internship fit alongside December exams at GKU?

Check the dates of the academic calendar and your own timetable first. Because theory exams run from 2 to 30 December 2026, many students may prefer the lighter schedule above or a start after their papers.

Related Software Testing guides

• Dr. B.R. Ambedkar University Agra: Applying for Testing Internships in Small Local Firms
• Apeejay Stya University Students: Test Automation Framework Basics for Interns
• SR University Students: Reading Logs and Debugging Evidence as a Test Intern
• All Software Testing internship guides