The ICFAI University Sikkim: A Decision Tree for Choosing Your First Testing Tool

Pick Postman if you have under an hour a day or want the fastest visible result, Selenium if you want browser automation and have some programming comfort, and JMeter if performance testing interests you and you can handle configuration screens. If you are unsure, start with a manual-testing toolkit plus Postman, because both transfer to every other tool. The decision tree below turns your goal and daily hours into one choice, then gives a 14-day plan for that branch.

Why the first testing tool matters less than finishing one project

Students lose weeks comparing tools and then learn none. Employers and interviewers care about whether you can design test cases, spot defects, explain what you tested and why, and show a small piece of evidence. The tool is the vehicle. Any of the four options below will teach you test design, if you build a small portfolio piece alongside it.

The tree is built on two inputs only: what you want to be able to do after 14 days, and how many hours a day you can honestly give. Programming comfort comes in as a tiebreaker.

Four tools, four kinds of testing: what each one is actually for

The decision tree: answer three questions in order

Question 1: What do you want to show at the end of 14 days?

• “I want to prove I can find and report bugs.” Go to Branch A (manual toolkit with Postman support).
• “I want to test how a backend or API behaves.” Go to Branch B (Postman).
• “I want to automate checks on a website.” Go to Question 2.
• “I want to see how a system behaves under many users.” Go to Branch D (JMeter).
• “I am not sure.” Go to Branch B. It is the safest default.

Question 2: Can you write and debug basic code (variables, loops, functions)?

• Yes, comfortably. Go to Question 3.
• Only a little. Take Branch B first; its small scripts build the coding habit, and you can add Selenium afterwards.
• Not at all. Branch A or B. Starting Selenium without code leads to copy-pasting you cannot debug.

Question 3: How many hours a day can you give?

• Two hours or more. Branch C (Selenium).
• Under two hours. Branch B (Postman), then Selenium later. Selenium setup and debugging eat time in small sessions.

The tree as a quick-reference table

Branch A: 14-day plan for the manual testing toolkit

1. Days 1-2: Learn the basics of the testing life cycle, test case structure, severity versus priority. Pick a free public website or a practice application as your test subject.
2. Days 3-5: Write 25 test cases in a spreadsheet covering positive, negative and boundary inputs for one feature, such as a login or signup form.
3. Days 6-8: Execute them. Record pass or fail with evidence such as screenshots.
4. Days 9-10: Use browser developer tools (network and console tabs) to see what the page sends and receives. This builds the bridge to API testing.
5. Days 11-12: Write 8 to 10 bug reports with title, steps, expected result, actual result and severity.
6. Days 13-14: Assemble a one-page test summary and a short write-up of what you learned.

Branch B: 14-day plan for Postman

1. Days 1-2: Learn HTTP basics: methods (GET, POST, PUT, DELETE), status codes, headers, JSON. Install Postman and send your first GET request to a public practice API.
2. Days 3-4: Build a collection with requests for create, read, update and delete on a practice API.
3. Days 5-7: Add assertions in the Tests tab: status code equals expected, response time under a limit, a field has the right value.
4. Days 8-9: Use environment variables for base URL and tokens, so the collection is reusable.
5. Days 10-11: Add negative tests: missing fields, wrong data types, invalid IDs.
6. Days 12-13: Run the whole collection with the Collection Runner and read the results.
7. Day 14: Export the collection, write a short README, and list what each test checks.

Branch C: 14-day plan for Selenium

1. Days 1-2: Confirm your language (Python or Java), install the driver setup, and open a browser from a script.
2. Days 3-4: Learn locators: ID, name, CSS selector, XPath. Practise finding elements on a practice site.
3. Days 5-6: Automate a login flow with an assertion on the result.
4. Days 7-8: Learn waits. Replace fixed sleeps with explicit waits, the most common source of flaky scripts.
5. Days 9-10: Add a test runner (pytest or TestNG) so tests report pass or fail.
6. Days 11-12: Restructure using the page object pattern: one class per page.
7. Days 13-14: Add three more tests, push the project to a public repository, and write a README.

Branch D: 14-day plan for JMeter

1. Days 1-2: Learn the vocabulary: throughput, response time, percentile, concurrent users, ramp-up. Install Java and JMeter.
2. Days 3-4: Build a Thread Group with an HTTP Request sampler against a practice or locally hosted site you are allowed to test.
3. Days 5-6: Add assertions, timers and a CSV data source.
4. Days 7-8: Use listeners to inspect results, then switch to non-GUI mode for actual runs.
5. Days 9-11: Run the test at 10, 50 and 100 simulated users and compare response times.
6. Days 12-13: Generate the HTML report and interpret it: where does response time rise, and do errors appear?
7. Day 14: Write a one-page findings note. Never load-test sites you do not own or have permission to test.

Worked example: one student, three answers (illustrative)

This is a made-up scenario to show the tree in use. Riya can study about 90 minutes a day, has written small Python programs, and wants to automate website checks.

• Question 1: website automation, so she goes to Question 2.
• Question 2: she has basic code comfort, so she goes to Question 3.
• Question 3: 90 minutes is under two hours, so the tree sends her to Branch B.

She follows the Postman plan for 14 days and builds a collection with assertions. Because she already knows Python, her next step after the internship is Branch C, and her API collection gives her a head start: she can later call the same endpoints from Python to prepare test data for UI tests. The tree did not tell her Selenium was a bad choice; it told her that her time budget makes Postman the better first investment.

Where to try the plan with structure

If you want a deadline and a deliverable, the free two-week online internship from CareerSwami fits the 14-day length of these plans, and it comes with a free offer letter and a free completion certificate after successful completion. Treat the certificate as a record of work done, and keep your own project files as the real proof.

ICFAI Sikkim students: fitting a testing tool into BCA and MBA internship rules

The Gangtok-based university was established under the ICFAI University, Sikkim Act 2004 and recognised under Section 2(f) of the UGC Act. For you, the relevant point is how internships are handled. The Summer Internship page says internships are undertaken as per each programme’s curriculum, and that students must find internships on their own, with the Placement Cell helping only in exceptional cases. So the rules sit with your programme, not in one university-wide document.

Programme structures differ. The BCA structure lists a 2-credit Summer Internship plus Internship Program-I and II tied to the exit options, and the BCA offers specialisations including Cyber Security and Full Stack Development, which pair naturally with API and UI testing. The MBA structure includes a 4-credit Summer Internship, with a duration of 4 to 6 weeks shown in one version. Those pages describe the university’s own internships; whether an online testing internship can count toward them is not stated, so do not assume it does. Treat a 14-day testing project as skill-building and a portfolio piece unless your department confirms otherwise in writing.

The Career Management Centre/Placement Cell page says it runs workshops and skill programmes and facilitates internships and placements, and gives placement@iusikkim.edu.in as a contact.

Five steps to verify before you rely on a testing project

1. Open the course structure for your exact programme and batch and note the internship credits, duration and any stated evaluation method.
2. Email your programme coordinator asking whether an online internship of 14 days is acceptable for the internship component, and keep the reply.
3. Ask what documents are needed (offer letter, certificate, report format, mentor sign-off) and by what date.
4. Write to placement@iusikkim.edu.in asking whether the Career Management Centre has any testing or software-quality opportunities or workshops this term.
5. If you are in BCA, ask which specialisation electives cover testing, so your tool choice lines up with coursework.

Checklist: signs your first tool choice is working by day seven

• You can explain in two sentences what your tool tests and what it cannot test.
• You have at least one test that fails for a reason you understand.
• Your project files are saved in a folder or repository, not just on screen.
• You can run your tests a second time without rebuilding anything.
• You have written down one question you could not answer, to research tomorrow.

If two or three of these are missing at day seven, drop one scope item rather than switching tools. Switching resets progress.

What to add after your first tool

Frequently Asked Questions

Should a complete beginner start with Selenium?

Usually not. Selenium needs coding and debugging skills that take time to build. Starting with Postman or the manual toolkit gives faster feedback and builds test-design habits that Selenium also needs.

Is Postman enough to get a first testing internship?

It is a strong starting point for API testing, especially when paired with well-written test cases and a documented collection. Many roles also expect some UI and manual testing, so plan to add those.

Can I learn JMeter without knowing Java?

Yes, for basic tests. JMeter is mostly configured through a graphical interface. You only need Java installed to run it. Deeper scripting later benefits from some Java or Groovy knowledge.

How many hours a day does each branch realistically need?

Manual and Postman branches work at about one hour a day. JMeter works from roughly 90 minutes. Selenium is best at two hours or more because setup and debugging come in long stretches.

Can I combine two tools in a 14-day plan?

Only if the second is small. A sensible mix is Branch A plus a few Postman days. Splitting time evenly across Selenium and JMeter usually leaves both half-finished.

Will a 14-day testing project count toward my ICFAI Sikkim internship credits?

The published pages say internships follow each programme’s curriculum, and no rule on online internships was verified. Ask your coordinator in writing before assuming it counts.

What should my project show to a recruiter?

A short README, the test files or exported collection, a list of what is covered, and a few real defects or findings. Clear explanations matter more than the number of tests.

Does the free CareerSwami internship suit the Postman or Selenium branch?

Its 14-day length matches the plans here, and you can choose a testing-related track from its 26 tracks. Pick the branch using the decision tree first, then use the internship period to complete that plan.