01
What is CI/CD and how does testing fit?
Show answer
Code is built and tested automatically on each change; tests are quality gates that stop faulty builds from moving forward.
Course5 Intelligence Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Course5 Intelligence hiring for Software Testing roles
Course5 Intelligence is a Mumbai-based analytics and AI company that offers market research, digital analytics, customer analytics and AI-driven insights to global brands. It works with clients in technology, retail, consumer goods, media and pharma. In India it hires data analysts, research analysts, data scientists and engineers who turn survey, digital and business data into insights.
For Software Testing roles, this Course5 Intelligence practice set focuses most on Test Case Design (8), STLC and Test Planning (7), Automation Basics for Manual Testers (5), Agile, SQL and API Testing (4). It has 7 easy, 31 medium, 2 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Analytics
- Headquarters
- Mumbai, India
- Main India offices
- Mumbai, Bengaluru
Course5 Intelligence Software Testing interview process
- Online assessment (aptitude + analytics basics)
- Technical interview
- Case or managerial round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Course5 IntelligenceStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
02
How do you test session management in a web application?
Show answer
Check that a new session ID is created after login, and that the session expires after the defined idle time. Verify logout invalidates the session on the server, so pressing back or reusing the old cookie does not work. Check that cookies use Secure, HttpOnly and SameSite flags. Test concurrent logins if they are limited, and that changing the password ends other sessions. Session IDs must not appear in URLs.
03
How do you make test cases reusable and easy to maintain?
Show answer
Write one clear objective per case, keep steps short and avoid hard-coding data that changes. Put shared steps such as login into a common precondition instead of repeating them. Use consistent naming, link each case to a requirement and group them by module. Keep expected results specific but not tied to exact pixel layouts. Review and update cases whenever a story changes, so the suite stays trustworthy for regression.
04
Your team wants to use an AI tool to generate test cases and automation scripts. What benefits and risks do you point out?
Show answer
AI assistants can draft test cases from requirements, suggest edge cases, generate first versions of scripts and test data, and some tools self-heal locators when the page changes. Risks are confident but wrong output, tests that assert the wrong behaviour, hidden locator changes that mask real bugs and leaking confidential data into external tools. Treat AI output like a junior's draft: review it, run it and keep human judgement on what matters.
05
How do you test an application when requirements change frequently?
Show answer
Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.
06
What is the definition of done?
Show answer
A shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.
07
What should a tester verify about HTTPS on a website?
Show answer
Check every page and API uses HTTPS, and plain HTTP redirects to HTTPS. Verify the certificate is valid, not expired, and matches the domain, with no browser warnings. Look for mixed content, where an HTTPS page loads scripts or images over HTTP. Check login and payment forms submit only over HTTPS and that cookies holding session data have the Secure flag.
08
How do you manage testing for multiple projects with competing deadlines?
Show answer
Model answer: Situation: I was supporting two products whose releases fell in the same week. Task: deliver both without dropping quality. Action: I listed tasks by release date and risk, agreed priorities with both leads, blocked focus time for each product and shared daily status. I also asked a teammate to take retesting on one project. Result: both releases went out on time with no critical escapes.
09
What is the difference between an error, a defect and a failure?
Show answer
A human error causes a defect in the code, and when that defect is executed it produces a failure visible to users.
10
How do you capture screenshots, videos and traces when an automated test fails?
Show answer
Most frameworks support this through configuration. In Playwright, set screenshot to only-on-failure, video to retain-on-failure and trace to on-first-retry in the config, then open the trace viewer to step through actions, network calls and the page state. In Selenium, call save_screenshot in a teardown hook when a test fails. Store these artefacts in CI so anyone can debug the failure without rerunning it.
11
Write test cases for a change password screen.
Show answer
1. Correct current password and valid new password: success, old password stops working. 2. Wrong current password: error, no change. 3. New password same as current: rejected if policy says so. 4. New and confirm fields do not match: error. 5. New password below minimum or above maximum length: error. 6. Missing digit or special character: policy message. 7. Other active sessions are logged out. 8. Confirmation email or alert is sent. 9. Password fields are masked.
12
What does the absence-of-errors fallacy mean?
Show answer
It means that finding and fixing many defects does not guarantee success if the system itself does not meet user needs. A bug-free product built on wrong or misunderstood requirements is still a failure. For example, a perfectly working report that shows the wrong business metric is useless to the client. This is why testers validate against real user expectations, not just the written specification.
13
Write test cases for an OTP verification screen.
Show answer
Verify a correct OTP within validity logs the user in. Verify a wrong OTP shows an error and an expired OTP is rejected. Check the OTP length and that only digits are allowed. Test resend: it is disabled during the countdown, and the old OTP stops working after resend. Check the maximum number of wrong attempts locks verification. Verify auto-read on mobile, paste support, and behaviour when the network drops during submission.
14
What is defect leakage?
Show answer
Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.
15
The build arrived three days late but the release date has not moved. How do you prioritise execution?
Show answer
Rank test cases by business risk and usage: critical flows like login, payment and data saving first, then new features, then high-risk regression from past defects, and cosmetic checks last. Run smoke testing immediately to avoid wasting time on a broken build. Share the reduced plan with the lead and product owner so they know what will not be covered, and get agreement on the remaining risk.
16
A feature passed all your test cases, but users say it is confusing. What went wrong?
Show answer
The tests verified the specification but did not validate the user experience. The test cases probably checked only functional outcomes and missed usability: unclear labels, too many steps or poor error messages. Next time, add usability heuristics to reviews, do exploratory sessions as a real user persona and involve users in UAT or demos. Log the current feedback as improvement items with clear examples.
17
What is the difference between a test suite and a test run?
Show answer
A suite is a collection of related test cases; a run is one execution of a set of tests against a build.
18
What are the boundary values for an age field that accepts 18–60?
Show answer
Test 17, 18, 19, 59, 60 and 61.
19
Tell me about a time you found a usability problem that the requirements did not mention.
Show answer
Situation: while testing a leave application form, every test case passed. Task: I still felt the flow was confusing. Action: I noticed the date picker started on Sunday and the half-day option was hidden under 'More', so I asked two colleagues to apply for leave while I watched; both made mistakes. I logged a usability suggestion with notes. Result: product moved the option and support queries dropped.
20
How do you test an API using Postman?
Show answer
Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.
21
What is normalization and why should a tester understand it?
Show answer
Normalization organises tables to reduce duplicate data, for example storing the customer address once in a customers table instead of repeating it in every order. Testers should understand it because it explains where data lives and which joins are needed to verify a screen. It also shows risk: in a denormalized report table, the same value is copied in many places, so updates must be tested to confirm every copy changes.
22
How do you convert existing manual test cases into automated scripts?
Show answer
Pick a small set of stable, high-value regression cases first. Review each one: make steps precise, remove judgement-based checks and define clear expected results. Prepare test data that the script can create and clean up. Build reusable page objects and helpers for common steps like login. Automate, run several times to confirm stability, then link each script to its manual case ID and mark the manual case as automated.
23
Write test cases for live order tracking in a food delivery app.
Show answer
Verify each status change appears in order: placed, accepted, preparing, picked up and delivered. Check the rider's location updates on the map at the expected interval. Test the estimated time updates when there is a delay. Verify notifications for each status. Check behaviour when the network drops and recovers, when the app is reopened, and when the order is cancelled midway. Confirm tracking stops after delivery and the rating screen appears.
24
You join a project in the middle of a release. How do you plan your testing?
Show answer
Spend the first day learning the scope: read the release notes, user stories and test plan, and ask the lead what is at risk. Get access to the environment, tracker and test repository. Pick up a clearly defined module, run its existing test cases to learn the application and note gaps. Ask questions early in stand-up. Within a few days, take ownership of retesting and regression for that module.
25
How do you run a moderated usability test session?
Show answer
Define goals and three to five realistic tasks, such as 'Book a train ticket for next Friday'. Recruit participants who match real users. In the session, explain that you are testing the product, not them, ask them to think aloud, and avoid hinting even when they struggle. Record the screen with consent, note where they hesitate or fail, and finish with a short questionnaire. Then group findings by severity and frequency.
26
How do you test touch target size and gestures for accessibility in a mobile app?
Show answer
Check that buttons and icons are large enough to tap without hitting neighbours: Android guidance is 48 by 48 dp and iOS is 44 by 44 points. Test with large font settings and one-handed use. Any action using complex gestures, such as swipe to delete or pinch, must have a simple tap alternative. Then turn on TalkBack and VoiceOver and confirm each control can be focused, named and activated.
27
Why must input validation be tested on the server and not only in the browser?
Show answer
Client-side validation improves user experience by giving quick feedback, but anyone can bypass it by disabling JavaScript or sending requests directly with tools like Postman. The server must validate every input again for type, length, format and business rules. Testers check this by sending invalid data straight to the API, such as a negative quantity or a very long name, and confirming the server rejects it.
28
How do you plan testing for a two-week sprint?
Show answer
In sprint planning, review each story's acceptance criteria and estimate test effort, including test data and regression. Write test cases in the first days while development starts. Ask for early builds so testing is spread across the sprint, not crowded at the end. Keep time for regression and bug retesting in the last two or three days. Track progress on the board and raise risks in stand-up.
29
What is mobile app testing and what extra checks does it need?
Show answer
Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.
30
Write test cases for a signup form.
Show answer
Mandatory fields, email format, password rules, duplicate email, terms checkbox, captcha, confirmation email and field length limits.
31
How do you test a modal dialog for accessibility?
Show answer
Open the dialog with the keyboard. Focus should move into it, usually to the first field or heading, and the screen reader should announce it as a dialog with its title. Tab must stay inside the dialog while it is open and the page behind must not be reachable. Escape and the close button should close it, and focus must return to the button that opened it. Also check it reads correctly when zoomed.
32
What is the difference between statement coverage and branch coverage?
Show answer
Statement coverage measures the percentage of code statements executed by tests. Branch coverage measures whether every decision outcome, true and false, has been executed. Branch coverage is stronger: for 'if (amount > 1000) applyDiscount()', one test with 1500 gives 100 percent statement coverage, but you need a second test with 500 to cover the false branch. 100 percent branch coverage implies 100 percent statement coverage, not the other way round.
33
How do you use JIRA in testing?
Show answer
Log and track bugs, link them to stories, build dashboards and filters with JQL, manage sprints and generate reports.
34
What happens in the requirement analysis phase of STLC?
Show answer
In requirement analysis, the testing team studies the requirements to understand what needs to be tested. They identify testable requirements, clarify doubts with the business analyst or client, decide test types needed, note automation candidates and look at environment needs. The outputs are a list of questions, a requirement traceability matrix draft and an automation feasibility note. Problems found here are the cheapest to fix.
35
How do you chain requests in Postman by passing a token from login to the next call?
Show answer
// Tests tab of the Login request
const body = pm.response.json();
pm.environment.set('authToken', body.token);
// Next request header:
// Authorization: Bearer {{authToken}}
// Postman replaces {{authToken}} with the saved value
36
Why are stable locators like data-testid or roles preferred over position-based XPath?
Show answer
A position-based XPath such as /html/body/div[3]/div[2]/button breaks whenever a developer adds a wrapper div or reorders the layout, even though the feature still works. That creates false failures and maintenance work. Locators based on a dedicated data-testid attribute or the accessible role and name, like a button named Submit, stay valid through design changes and describe intent clearly. Testers should ask developers to add test IDs.
37
How do you do cross-browser testing and choose which browsers to cover?
Show answer
Use analytics to pick browsers and versions that most real users have, plus the ones listed in the requirement, usually the latest two versions of major desktop and mobile browsers. Run the main flows on each and check layout, fonts, forms, date pickers, file upload and JavaScript errors in the console. Use responsive mode for screen sizes, and real devices or a cloud device lab for mobile browsers.
38
Functional vs non-functional testing?
Show answer
Functional testing checks what the system does (login, checkout). Non-functional testing checks how well it does it (performance, security, usability, compatibility).
39
Write test cases for a file upload feature.
Show answer
Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.
40
Write a CSS selector and an XPath for a Login button that has the attribute data-testid='login-btn' and the text Login.
Show answer
/* CSS selector using the test id */
button[data-testid='login-btn']
// XPath using the test id
//button[@data-testid='login-btn']
// XPath using the visible text
//button[normalize-space()='Login']
Tips to crack the Course5 Intelligence Software Testing interview
- Revise Excel, SQL and a visualisation tool such as Power BI or Tableau, which are widely used in analytics roles.
- Learn basic market research concepts like surveys, sampling and segmentation if you apply for research and insights positions.
- Practise presenting a short insight story from a dataset, explaining what the numbers mean for a business decision.
- Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
- Practise the hard questions on this page aloud; Course5 Intelligence interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Course5 Intelligence Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + analytics basics); Technical interview; Case or managerial round; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Course5 Intelligence Software Testing interview?
This practice set leans on Test Case Design (8), STLC and Test Planning (7), Automation Basics for Manual Testers (5), Agile, SQL and API Testing (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Course5 Intelligence interviewers ask you to walk through real work.
Are these the exact questions asked at Course5 Intelligence?
No. These are curated practice questions that match the skills and difficulty usually tested in analytics interviews like Course5 Intelligence's. They are not a leaked or verified list of past questions.
Where does Course5 Intelligence hire Software Testing professionals in India?
Course5 Intelligence has large teams in Mumbai, Bengaluru. Openings and locations change often, so check the Course5 Intelligence careers page and filter by city and experience.
Software Testing questions for similar companies
Analytics
NielsenIQ
Software Testing interview questions
Vadodara, Chennai, Pune
View questionsAnalytics
Tredence
Software Testing interview questions
Bengaluru, Chennai, Gurugram
View questionsAnalytics
Quantiphi
Software Testing interview questions
Mumbai, Bengaluru
View questionsAnalytics
Affine
Software Testing interview questions
Bengaluru
View questionsAnalytics
Sigmoid
Software Testing interview questions
Bengaluru, Pune
View questionsAnalytics
Tiger Analytics
Software Testing interview questions
Chennai, Bengaluru, Hyderabad
View questionsMore ways to practise
Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets