Software Testing Internship Preparation for Chandigarh University Students: Skills Roadmap

Yes, a Chandigarh University student can prepare for a software testing internship in about eight to ten weeks, alongside regular classes. Build skills in this order: testing fundamentals, SQL, API basics, then a small automation project. Each stage ends with something you can show: a bug report, a query set, a Postman collection, a working script.

What a testing internship expects from you

Interns in testing are rarely asked to build frameworks. They are asked to read a requirement, work out how a feature could fail, run checks, and report what they found so a developer can reproduce it. That is a thinking skill first and a tooling skill second.

Most entry-level testing tasks fall into four groups:

• Manual functional testing: executing test cases on a web or mobile screen and recording results.
• Test design: writing cases from requirements, including negative and boundary cases.
• Data and service checks: confirming through SQL and API calls that what the screen shows matches what the system stored.
• Basic automation: turning a stable, repetitive check into a script.

The roadmap below follows that same order, because each layer depends on the one before it. Automating a badly designed test only produces a fast, unreliable one.

The skills roadmap at a glance

If you have less time, compress stages 1 to 3 and keep automation to a single small script. A modest, understood project is more useful than a large copied one.

Stage 1: Testing fundamentals (weeks 1-2)

Concepts to be able to explain in your own words

• The difference between verification and validation.
• Where testing sits in the software development life cycle, and what the software testing life cycle adds.
• Test levels: unit, integration, system, acceptance.
• Test types: functional, regression, smoke, sanity, usability, compatibility, basic performance.
• Severity versus priority, with one example where they differ.
• The bug lifecycle: new, assigned, fixed, retested, closed or reopened.

Test design techniques that interviewers actually ask about

• Equivalence partitioning: group inputs that should behave the same and test one from each group.
• Boundary value analysis: test at, just below and just above each limit.
• Decision tables: list combinations of conditions and the expected outcome of each.
• State transition thinking: for example, an order moving from placed to paid to shipped to cancelled.
• Error guessing: blank fields, very long text, special characters, double clicks, back-button behaviour.

Writing a bug report that gets fixed

A good report is short and reproducible. Include a specific title, the environment (browser, device, build), numbered steps, expected result, actual result, and evidence such as a screenshot or screen recording. Avoid opinions like “the page is bad”. State what happened.

Stage 2: SQL for testers (weeks 3-4)

Testers use SQL to check that data was saved correctly, to set up test data, and to find records that break rules. You do not need advanced database design. You need to read tables confidently.

Minimum SQL skill set

1. Filtering rows with WHERE, AND, OR, IN, BETWEEN, LIKE.
2. Sorting and limiting results.
3. Aggregates: COUNT, SUM, MIN, MAX, with GROUP BY and HAVING.
4. Joins: INNER JOIN and LEFT JOIN, and why a left join exposes missing records.
5. Handling NULL correctly.
6. Primary keys, foreign keys and unique constraints, and what a violation looks like.
7. Basic INSERT, UPDATE and DELETE on a practice database only.

Validation queries worth practising

• Find duplicate emails in a users table.
• Find orders that have no matching customer.
• Compare the sum of order items with the stored order total.
• List records created in the last seven days with a blank mandatory field.

Use a free local database such as MySQL, PostgreSQL or SQLite with a sample dataset. Write each query, predict the row count before running it, then check your prediction. That habit builds the instinct testers need.

Stage 3: API basics (weeks 5-6)

Many defects are visible only below the screen. API testing checks the request and response directly, which is faster and more precise than clicking through a form.

What to learn

• HTTP methods: GET, POST, PUT, PATCH, DELETE, and when each is used.
• Status code families: 2xx success, 3xx redirect, 4xx client error, 5xx server error. Know 200, 201, 400, 401, 403, 404 and 500 well.
• Reading and writing JSON, including nested objects and arrays.
• Headers, query parameters, path parameters and request bodies.
• Authentication ideas: API keys, bearer tokens, and the difference between 401 and 403.

Tools

Postman or a similar client is enough to begin. Use a free public practice API, create a collection, add environment variables for the base URL, and write assertions for status code, response time and key fields. Then try failure cases: a missing field, a wrong data type, an expired token, an ID that does not exist.

API test ideas by category

Stage 4: Automation starter (weeks 7-9)

Pick one language and stay with it. Java and Python are both common in testing roles; choose whichever you already read comfortably from your coursework. Then pick one UI tool, such as Selenium or Playwright, and learn it properly rather than sampling three.

Learning order

1. Language basics: variables, conditions, loops, functions, lists and dictionaries or collections, exceptions.
2. Locating elements: IDs, CSS selectors, and XPath as a fallback.
3. Actions and assertions: click, type, read text, compare with expected values.
4. Waiting strategies: prefer explicit waits over fixed sleeps.
5. A test runner such as pytest or TestNG, with setup and teardown.
6. Page Object structure, so locators live in one place.
7. Git: commit often, write meaningful messages, push to a public repository.

What to automate, and what not to

• Good candidates: login, search, add to cart, form validation, a smoke suite you would run after each build.
• Poor candidates: one-off checks, visual judgement, features still changing daily, CAPTCHA flows.

Worked example (illustrative): testing a fee-payment form

This example is invented for practice and does not describe any real university system. Suppose a demo form accepts a student ID, an amount between 1,000 and 50,000 rupees, and a payment mode of UPI or card. No test has been run here; the tables show how the thinking works.

Step 1: Design cases with boundaries

Step 2: Verify the data with SQL

After TC07, a tester would check that exactly one row exists. A query like this would do it:

SELECT student_id, amount, COUNT(*) AS entries
FROM payments
WHERE student_id = 'DEMO101'
GROUP BY student_id, amount
HAVING COUNT(*) > 1;

An empty result means no duplicates. Any returned row is evidence for a bug report.

Step 3: Check the API behind the form

In Postman, send the same amount values to the payment endpoint. If the screen rejects 50,001 but the API accepts it, the validation exists only in the browser. That is a genuine finding because anyone calling the service directly can bypass the screen.

Step 4: Write the bug report

• Title: Payment API accepts amount above the 50,000 limit that the UI enforces.
• Steps: send a POST request with amount 50001, a valid student ID and the mode UPI.
• Expected: a client error response with a limit message.
• Actual: a success response and a new database row.
• Severity: high, because the rule can be bypassed.

Step 5: Automate the stable part

The boundary cases TC01 to TC04 are repetitive and stable, so they suit a data-driven script that loops through amount and expected-message pairs. TC07 needs careful timing, so it is better to leave it manual until the rest is solid.

Scorecard: rate yourself before you apply

Score each row from 0 (not started) to 3 (can do it without notes and explain it). Be strict; interviewers will be.

A total of 20 or more out of 27 suggests you are ready to apply widely. Between 12 and 19, keep applying while closing the weakest rows. Below 12, spend another two weeks on stages 1 and 2, because those carry the most weight at entry level.

Practice milestones with a weekly rhythm

• End of week 2: a test case sheet and five bug reports on a public demo application.
• End of week 4: a file of validation queries with a note beside each stating what defect it would catch.
• End of week 6: a Postman collection with at least 15 requests, including negative cases.
• End of week 9: an automation repository with a README explaining setup, how to run the tests and what they cover.
• End of week 10: a resume with a projects section and two mock interviews with a friend or senior.

A workable rhythm is five short sessions a week: two for new learning, two for practice, one for review. Keep a log of mistakes. Repeated mistakes show where to spend the next hour.

Interview questions to rehearse

1. What is the difference between smoke and sanity testing?
2. Give a case where severity is high but priority is low.
3. How would you test a login page? Give ten cases.
4. What is the difference between INNER JOIN and LEFT JOIN?
5. What does a 401 response mean, and how does it differ from 403?
6. Why should an automated test avoid fixed sleeps?
7. When would you decide not to automate a test?
8. Describe a bug you found in your own project and how you proved it.

Chandigarh University and the testing roadmap: what the published pages show

Chandigarh University publishes its academic calendars and curriculum schemes institute by institute, so the first step is to find the pages for your own institute. The University Institute of Computing (UIC) calendar for 2026-27 is one example, and it applies to UIC, not to every programme. Check the current version, because the excerpt may have been updated.

Timing matters for the roadmap, which runs about nine weeks. According to that UIC calendar, practical exams run from 16-11-2026 to 20-11-2026 and end-semester theory exams from 23-11-2026 to 19-12-2026. The same page shows even-semester registration from 21-12-2026 to 03-01-2027 and the even semester starting on 04-01-2027. In practice, the stages on testing fundamentals and SQL are better done around coursework than during exam weeks. Applications and any document work are easier in the roughly two-week gap between semesters. A student in another institute should look up that institute’s own calendar.

For mapping skills to subjects, the BE CSE curriculum page lists schemes by batch (2023-27 and 2024-28 among them) with L-T-P-S-C credit columns. A separate BE CSE Full Stack Development scheme exists with its own course codes. Schemes differ by batch and specialisation, so open the one matching your admission year and mark which later-semester subjects cover databases, software engineering or programming. Link them to roadmap stages 2, 1 and 4 only after reading the real subject titles.

On internships, the only rule-like fact found is programme-specific: the MBA Business Intelligence scheme for Batch 2025-27 lists a Summer Internship Project course (25BAT-734) in semester 3 as a 4-credit project. That applies to that MBA scheme and says nothing about engineering or computing programmes. A 2026 press release mentions compulsory summer training in aerospace engineering, but it is a press release, not a regulation. Whether an external online testing internship counts for anything in your programme must be confirmed with your own department.

Checks to finish before you start the testing roadmap

• Find your institute’s calendar on cuchd.in and note practical and theory exam dates before fixing your nine-week plan.
• Open the curriculum page for your programme and admission batch, and list subjects on databases, software engineering and programming with their credits.
• Ask your department coordinator in writing whether your scheme has a mandatory internship or summer training course, and what documents it requires.
• Ask the training and placement office whether an external online internship is permitted and what proof they accept.
• Ask a faculty member to confirm which syllabus units cover testing, SQL and web or API topics.

A free way to get structured practice

If you want a short, guided starting point, CareerSwami offers a free two-week (14-day) online internship across 26 tracks, with a free offer letter and a free completion certificate after successful completion. It does not include a stipend, and it does not promise academic credit, placement or a job, so treat it as practice material for the portfolio you are building.

Testing-prep mistakes that cost interns marks and offers

• Collecting tools before skills. Knowing five tools shallowly is weaker than knowing one well.
• Copying a project from a video. If you cannot explain every line, an interviewer will find out in two questions.
• Skipping negative cases. Testing is mostly about what happens when things go wrong.
• Ignoring communication. A clear bug report is part of the job.
• Overstating results. Describe what your project covers and what it does not.

Frequently Asked Questions

How much programming should I know before applying for a software testing internship?

Not for every role. Manual and functional testing internships focus on test design, bug reporting, SQL and API basics. Programming helps for automation roles, so learn it in stage 4 once the fundamentals are solid.

Which should I learn first, SQL or automation?

SQL. It is quicker to learn, comes up in almost every interview, and is useful in manual and automation roles alike. Automation comes after you can design good tests.

Should a beginner in test automation start with Selenium or Playwright?

Both are acceptable. Select based on the language you already know and the job listings you are targeting, then stay with that choice through one complete project.

How many testing projects should I show in my portfolio?

Two or three small ones are enough: a test case and bug report pack, an API collection, and a small automation repository. Each should have a README that explains scope and how to run it.

Can I prepare for this alongside semester classes?

Yes. Five sessions of 60 to 90 minutes a week is realistic. Use your database and programming subjects as practice time where they overlap with the roadmap.

Will an online software testing internship certificate count toward my Chandigarh University requirements?

That depends on your programme’s rules, which this guide cannot confirm. Ask your department coordinator or training and placement office for the written rule before relying on it.

What should a testing resume include?

A short skills list, your projects with one line each on what was tested and how, a link to your repository, and any completed internship. Describe results factually and avoid inflated numbers.

How do I practise bug reporting without a real application?

Use public demo shops, practice sites built for testers, or open-source applications you can run locally. Log defects in a spreadsheet or a free issue tracker using the report structure above.

Related Software Testing guides

• Software Testing Internship Prerequisites for Kumaraguru College of Technology Students
• Manual or Automation Testing Internship? A Guide for Vishwakarma Institute of Technology, Pune Students
• Building a Software Testing Internship Portfolio for Pune Institute of Computer Technology Students
• All Software Testing internship guides