Assam University Students: Choosing a Testing Specialisation Through a Two-Week Trial

Yes, two weeks is enough to choose a direction in software testing, provided you sample the three main paths deliberately: manual, API and automation. Spend roughly four days on each, record how each felt and what you produced, then compare the evidence in a scoring grid instead of following whatever is fashionable. This article gives you the 14-day plan, the grid, a worked illustration and a decision rule.

Why sampling beats guessing when you pick a testing path

Testing job titles blur together. “QA Engineer” can mean someone who writes test cases from requirements, someone who probes REST endpoints with Postman, or someone who maintains Selenium or Playwright suites. Course syllabi rarely let you feel the difference. A short trial does.

The three paths reward different habits:

• Manual testing rewards curiosity, attention to detail, and clear written communication. Your output is test cases, bug reports and exploratory session notes.
• API testing rewards comfort with structured data (JSON, status codes, headers) and logical thinking about contracts between systems. Your output is request collections, assertions and defect evidence.
• Automation rewards patience with programming, debugging and maintenance. Your output is scripts, a small framework and run reports.

The aim is not to master anything in 14 days. It is to collect honest signals: what held your attention, what you did well, and what you would be willing to do for eight hours a day.

The 14-day trial plan: manual, API and automation sampled in sequence

This plan fits the free two-week online internship from CareerSwami, which offers 26 tracks, a free offer letter and a free completion certificate after successful completion. It also works as a self-run schedule using any practice application. Pick one small web application (a demo shopping site, a to-do app, or a public practice API) and use it for all three phases so your comparisons are fair.

Daily rhythm that keeps the trial honest

1. Work in a fixed block of two to three hours so every phase gets comparable effort.
2. Keep a one-line log at the end of each day: what you did, what annoyed you, what you wanted to continue.
3. Save every artefact with a date. Evidence beats memory when you fill the grid.
4. Do not switch phases early because something is hard; difficulty is part of the signal.

The reflection grid: scoring manual, API and automation side by side

After each phase, score the criteria from 1 (low) to 5 (high). Write one sentence of evidence per score, such as “found a boundary bug in the age field” or “spent 90 minutes on one locator.” Scores without evidence tend to drift towards whatever you already hoped to hear.

Weighting the grid

Not all criteria matter equally for a decision. Double the score for Engagement and Curiosity pull, because interest sustains the months of practice that follow. Skill fit can be improved with study, so treat it as a tiebreaker rather than a verdict.

Worked illustration: how one student’s scores could translate into a choice

This is an illustrative example with invented numbers, not a record of a real student or a tool run.

Suppose a BCA student uses a public demo shop for all three phases. After the weights are applied, the grid looks like this:

The evidence lines tell the story. In the manual phase the student found two validation bugs but noted that repetitive regression runs felt dull. In the API phase they enjoyed reading response bodies and found a missing-field handling defect. In the automation phase they spent most of day 12 fixing a broken locator and felt stuck.

The reading: API testing leads clearly, manual is a solid second, and automation scored low mainly because of learning speed and friction, which are fixable with more programming practice. A sensible plan is to specialise in API testing first, keep manual exploratory skills as a base, and return to automation by scripting API checks, which is a gentler route into code than browser automation.

Turning your totals into a decision: a simple rule set

1. Clear lead (8 or more points): choose that path for your next 30 days and build one deeper project in it.
2. Narrow lead (under 8 points): choose the path with the higher Engagement plus Curiosity score. If still tied, choose the one with the higher Evidence of value.
3. Automation low only because of learning speed or friction: do not discard it. Add two weeks of programming fundamentals and re-test with a smaller script.
4. All three similar: start with manual and API together. They build the test-thinking that automation depends on, and many entry-level roles blend them.
5. One path scored below 3 on Engagement: treat that as a genuine signal and drop it for now.

What each result points to as a next step

• Manual lead: practise test design techniques, write sharper bug reports, learn a test management tool, and study basic SQL so you can verify data.
• API lead: learn HTTP in more depth, authentication methods, JSON schema checks, and how to script collections from the command line.
• Automation lead: deepen one language, learn a test framework, version control, and how tests run in a pipeline.

Assam University students: fitting a testing trial around FYUG internship rules and your semester

If you study at a college affiliated to Assam University, the 2023 FYUG regulations are the document that shapes how any internship fits your degree. They cover four-year UG programmes (BA, BSc, BCom, BBA, BCA, BVoc) in affiliated colleges, and they describe Internship/Community Engagement/Field Work as a compulsory 2-credit course in semester 5 for all disciplines. Note that this copy of the regulations is hosted on an affiliated college’s website, so check the current version with your own department.

In practice, the regulations leave the mechanism to each college and its departments, with groups of at most 20 and allocation preferably by DSC subject. On completion you present to departmental teachers and submit a report certified by your Head of Department, Coordinator or Mentor, preferably with an authentication certificate from the host organisation. The passages summarised do not mention online internships or a fixed duration, so do not assume a self-run or online trial counts toward that course. A trial like this one is best treated as a skill-building exercise that gives you material for a semester-5 report topic, until your department says otherwise.

Computer science students can also look at the B.Sc. Computer Science first-year syllabus hosted by the department (listed from search excerpt, so confirm the current version) to see which programming foundations you already have before choosing automation. The university’s Career Counselling & Placement Cell page lists contact emails and a placement data file; use it to ask what skills recruiters look for rather than assuming.

Schedule the 14 days outside examination weeks. A university notice indicated that even-semester examinations of May 2026 would begin in the second or third week of May; the 2026-27 calendar should be checked separately.

Five verification steps for your department

1. Email your department coordinator asking, in writing, whether a self-run or online two-week trial can be used as material for the semester-5 internship report.
2. Ask who your mentor or certifying Head of Department would be, and what format the report and presentation must follow.
3. Request the current FYUG regulations or your college’s internship guidelines from the college office, and compare them with the 2023 copy.
4. Check the academic calendar for your semester and pick 14 days clear of examinations and practicals.
5. Write to placement@aus.ac.in or the cell contact on the placement page asking which testing or QA skills are most useful for your programme.

Practice material that makes each phase productive

Manual phase checklist

• Test cases cover valid, invalid and boundary inputs.
• Each bug report has title, steps, expected result, actual result and severity.
• One exploratory session has a charter, a time box and notes.

API phase checklist

• Each endpoint has at least one positive and one negative request.
• Assertions check status code and at least two response fields.
• You tested missing, empty and wrongly typed fields.

Automation phase checklist

• The script runs end to end from a clean start.
• Locators and data are separated from test steps.
• You recorded how long a deliberate break took to fix.

An illustrative API check to try on day 8

This is a sketch of an assertion idea for a practice API, not output from an executed test:

Request:  POST /users  with body {"name": "", "email": "a@b.com"}
Expect:   status 400 (or the API's documented validation code)
Expect:   response body names the "name" field as the problem
Note:     if the API returns 200 and creates the user, log a defect

Turning the trial into evidence you can show

On day 14, collect a small portfolio: the test case sheet, two or three strong bug reports, the API collection, the working script, the completed grid and your half-page summary. Describe what you did accurately and avoid inflating it. A reviewer will trust “sampled three paths over 14 days and chose API testing based on scored evidence” more than a vague claim of expertise. If you complete the CareerSwami internship, the free completion certificate confirms completion of the programme; it is not a guarantee of academic credit, placement or a job.

Frequently Asked Questions

Can I really judge three testing paths in 14 days?

You cannot master them, but you can learn which one holds your interest and suits your strengths. Four focused days per path, with artefacts and scores, produce enough evidence for a first direction, which you can revise later.

Should I start with manual testing before API or automation?

Starting with manual testing is sensible because it teaches test design and bug reporting, which both other paths rely on. The order also lets you reuse the same application and the cases you already wrote.

I am weak at programming. Should I skip the automation phase?

Do it anyway, but keep the script small. The phase shows whether the difficulty is the concept or simply lack of practice. Low scores on learning speed alone are a reason to add programming practice, not necessarily to abandon the path.

Will a self-run trial count for my Assam University semester-5 internship course?

The regulations summarised here leave the mechanism to each college and do not mention online internships, so do not assume it counts. Ask your department coordinator in writing before relying on it.

Which tools are enough for a beginner trial?

A spreadsheet for test cases, a free API client such as Postman, and one browser automation tool in a language you already know are enough. Choosing fewer tools leaves more time to practise testing itself.

What if two paths score almost the same?

Compare Engagement and Curiosity pull first, then Evidence of value. If they still tie, begin with manual and API together, since scripting API checks is a gentle bridge into automation.

How should I describe the trial on a resume?

List the concrete artefacts: number of test cases written, bugs reported, API collection built and script created, along with the practice application used. Label it as a structured self-study or internship project, and avoid implying paid or employer experience.

Can the CareerSwami internship fit this three-path trial?

Its 14-day online format matches the plan’s length, so you can map the phases onto your chosen track. Check the track details on the site to see how closely its tasks follow manual, API or automation work.

Related Software Testing guides

• Shreyarth University Students: Turning Internship Bugs Into Interview Stories
• Software Testing Internship Prerequisites for Kumaraguru College of Technology Students
• Manual or Automation Testing Internship? A Guide for Vishwakarma Institute of Technology, Pune Students
• All Software Testing internship guides