Find Interview Questions for Top Companies
Ques:- Wirte the test cases for triangle by using testing techniques
Asked In :-
Right Answer:
1. **Equilateral Triangle**
- Input: (3, 3, 3)
- Expected Output: Valid triangle

2. **Isosceles Triangle**
- Input: (4, 4, 5)
- Expected Output: Valid triangle

3. **Scalene Triangle**
- Input: (3, 4, 5)
- Expected Output: Valid triangle

4. **Invalid Triangle (Sum of two sides less than third)**
- Input: (1, 2, 3)
- Expected Output: Invalid triangle

5. **Invalid Triangle (Negative side)**
- Input: (-1, 2, 3)
- Expected Output: Invalid triangle

6. **Invalid Triangle (Zero side)**
- Input: (0, 2, 3)
- Expected Output: Invalid triangle

7. **Invalid Triangle (
Ques:- Which of the following is NOT a characteristic of UserAcceptance Testing??A.Use of automated test execution toolsB.Testing performed by userC.testing against acceptance test criteriaD.integration of system with user documentation.
Asked In :-
Right Answer:
A. Use of automated test execution tools
Ques:- Write test 10 cases for program which has a table with 2fields of NAME od char type and CLASS of INT type.NAME fields is truncatedafter 26 charaters and CLASS takes value between 1 to 9 both included.There are 3 possible opearations program can performa)When a new student joins the class the program adds a newfieldb)When student leaves the class the field get deleted c)when student gets promoted then program incremts the classby 1Write 5 test cases for the scenario
Asked In :- Lantrasoft,
Right Answer:
1. **Test Case 1: Add New Student**
- Input: NAME = "John Doe", CLASS = 5
- Expected Result: Student added successfully.

2. **Test Case 2: Add New Student with Long Name**
- Input: NAME = "This name is definitely longer than twenty-six characters", CLASS = 3
- Expected Result: NAME truncated to "This name is definitely long", Student added with CLASS = 3.

3. **Test Case 3: Add Student with CLASS Out of Range**
- Input: NAME = "Alice", CLASS = 10
- Expected Result: Error message indicating CLASS must be between 1 and 9.

4. **Test Case 4: Delete Existing Student**
- Input: NAME = "John Doe"
- Expected Result: Student deleted successfully.

5. **Test Case 5: Promote Student**
- Input: NAME = "Alice", CLASS = 8
Ques:- When to prepare System test plan aftergetting build or before getting build?
Asked In :-
Right Answer:
The System Test Plan should be prepared before getting the build.
Ques:- What is the RTM(Requirement Traceability Matrix)
Asked In :-
Right Answer:
The Requirement Traceability Matrix (RTM) is a document that links requirements throughout the project lifecycle, ensuring that all requirements are covered by test cases and that changes are tracked. It helps verify that the final product meets the specified requirements.
Ques:- Can u draw the template for Requirement Traceability Matrix?
Asked In :-
Right Answer:
| Requirement ID | Requirement Description | Test Case ID | Test Case Description | Status | Comments |
|----------------|-------------------------|---------------|-----------------------|--------|----------|
| Req-001 | Description of Req-001 | TC-001 | Description of TC-001 | Pass | |
| Req-002 | Description of Req-002 | TC-002 | Description of TC-002 | Fail | Needs review |
| Req-003 | Description of Req-003 | TC-003 | Description of TC-003 | Pass | |
| ... | ... | ... | ... | ... | ... |
Ques:- Can u plz write/tell me 2 main Negative Test Cases for myMobile Phone.
Right Answer:
1. Test Case: Attempt to make a call when the phone is in airplane mode.
Expected Result: The call should not go through, and an error message should be displayed.

2. Test Case: Try to send a text message to an invalid phone number format (e.g., "12345").
Expected Result: The message should not be sent, and an error notification should appear indicating the number is invalid.
Ques:- What is the difference between value table and check table?
Right Answer:
A value table is used to define a set of valid values for a field, while a check table is used to enforce referential integrity by linking a field to a set of valid entries in another table.
Ques:- Difference between SRS and FRS
Asked In :- Veho, ASSURANCE IQ, goc, clarasys,
Right Answer:
SRS (Software Requirements Specification) outlines the complete software requirements, including functional and non-functional requirements, while FRS (Functional Requirements Specification) focuses specifically on the functional requirements of the system, detailing what the system should do.
Ques:- Write the Test Cases for Ball Pen and Water Bottle.
Asked In :-
Right Answer:
**Test Cases for Ball Pen:**

1. **Test Case ID:** BP-001
**Test Case:** Check if the pen writes smoothly.
**Expected Result:** The pen should write without skipping or blotting.

2. **Test Case ID:** BP-002
**Test Case:** Verify ink color.
**Expected Result:** The ink color should match the specified color (e.g., blue, black).

3. **Test Case ID:** BP-003
**Test Case:** Test the pen's durability.
**Expected Result:** The pen should withstand a drop from a height of 1 meter without breaking.

4. **Test Case ID:** BP-004
**Test Case:** Check the cap's fit.
**Expected Result:** The cap should fit securely on the pen without falling off.

5. **Test Case ID:** BP-005
**Test Case:** Verify the pen's refillability.
**Expected
Ques:- Explain test procedure and write test cases for EFTPOS/CREDIT CARD
Asked In :-
Right Answer:
**Test Procedure for EFTPOS/CREDIT CARD:**

1. **Setup Environment:**
- Ensure the EFTPOS terminal is connected to the payment network.
- Verify that the software is installed and configured correctly.

2. **Test Case Design:**
- Identify scenarios including valid and invalid transactions, network issues, and user interactions.

3. **Execute Test Cases:**
- Perform transactions using various card types (credit, debit).
- Test different transaction amounts (below, at, and above limits).

4. **Verify Results:**
- Check if the transaction is processed correctly.
- Validate the response messages and receipts.

5. **Log Results:**
- Document the outcomes of each test case, including any defects found.

**Test Cases for EFTPOS/CREDIT CARD:**

1. **Valid Transaction:**
- Input: Valid card details, valid PIN, amount $50.
- Expected Result: Transaction approved, receipt printed.

2. **
Ques:- Explain test plan template?
Right Answer:
A test plan template is a structured document that outlines the strategy, scope, resources, and schedule for testing activities. It typically includes sections such as:

1. **Test Plan Identifier**: Unique ID for the test plan.
2. **Introduction**: Overview of the project and objectives.
3. **Test Items**: Features or functionalities to be tested.
4. **Test Scope**: What will and will not be tested.
5. **Test Strategy**: Approach to testing (manual, automated, etc.).
6. **Resources**: Team members, tools, and environments needed.
7. **Schedule**: Timeline for testing phases.
8. **Risk Assessment**: Potential risks and mitigation strategies.
9. **Approval**: Sign-off section for stakeholders.

This template helps ensure consistency and thoroughness in the testing process.
Ques:- What r the different types of test case? and tell me the names.
Asked In :-
Right Answer:
1. Functional Test Cases
2. Non-Functional Test Cases
3. Regression Test Cases
4. Integration Test Cases
5. System Test Cases
6. User Acceptance Test Cases
7. Smoke Test Cases
8. Sanity Test Cases
9. Performance Test Cases
10. Security Test Cases
11. Usability Test Cases
12. Compatibility Test Cases
13. End-to-End Test Cases
14. Unit Test Cases
Ques:- What is the role of a tester in the test plan preparation?What elements tester physically develops in the test plandocument.& what exactly this document contains?
Asked In :-
Right Answer:
The role of a tester in the test plan preparation includes defining the testing scope, objectives, resources, schedule, and approach. The tester physically develops elements such as:

1. Test objectives
2. Test scope (in-scope and out-of-scope items)
3. Test strategy (types of testing to be performed)
4. Test environment requirements
5. Test schedule (timeline and milestones)
6. Resource requirements (team roles and responsibilities)
7. Risk assessment and mitigation strategies
8. Test deliverables (what will be produced)
9. Entry and exit criteria for testing phases

The test plan document contains all these elements, providing a comprehensive guide for the testing process.
Ques:- How will you manually test yahoo messenger on single system.
Asked In :-
Right Answer:
To manually test Yahoo Messenger on a single system, follow these steps:

1. **Installation**: Ensure Yahoo Messenger is installed correctly on the system.
2. **Login**: Test the login functionality with valid and invalid credentials.
3. **User Interface**: Check the layout, buttons, and menus for usability and accessibility.
4. **Messaging**: Send and receive messages to/from another user account to verify real-time communication.
5. **File Transfer**: Test sending and receiving files to ensure the file transfer feature works.
6. **Voice/Video Calls**: Initiate voice and video calls to check audio and video quality.
7. **Notifications**: Verify that notifications for new messages and calls are functioning.
8. **Settings**: Test the settings options for customization (e.g., status, privacy).
9. **Performance**: Monitor the application’s performance under different loads (e.g., multiple messages).
10. **Error Handling**: Check how the application handles network
Ques:- Expalin integration tsting who will perform ths type oftesting at what time will do
Asked In :- arbisoft,
Right Answer:
Integration testing is a type of software testing where individual components or systems are combined and tested as a group to identify interface defects. This testing is typically performed by developers or dedicated testers after unit testing and before system testing, often during the development phase when modules are integrated.
Ques:- Write down test cases for “x>=1”
Asked In :-
Right Answer:
1. **Test Case 1: Valid Input**
- Input: `x = 1`
- Expected Result: True (Condition is satisfied)

2. **Test Case 2: Valid Input**
- Input: `x = 5`
- Expected Result: True (Condition is satisfied)

3. **Test Case 3: Boundary Input**
- Input: `x = 0`
- Expected Result: False (Condition is not satisfied)

4. **Test Case 4: Negative Input**
- Input: `x = -1`
- Expected Result: False (Condition is not satisfied)

5. **Test Case 5: Large Positive Input**
- Input: `x = 1000`
- Expected Result: True (Condition is satisfied)


The Whitebox Testing section on takluu.com is designed for QA professionals, testers, and developers who want to master the internal testing techniques crucial for delivering high-quality software. Whitebox testing, also known as structural or glass-box testing, involves examining the internal logic, code structure, and workflows to ensure thorough test coverage and bug detection.

This category covers essential concepts such as code coverage metrics (statement, branch, path coverage), control flow testing, data flow testing, unit testing frameworks, and debugging techniques. You’ll also learn about writing effective test cases, identifying edge cases, and using automation tools that support whitebox testing.

Whitebox testing is vital in detecting hidden errors early in the development cycle, improving code quality, and facilitating continuous integration and deployment. This section provides practical interview questions and detailed explanations to help you understand how whitebox testing differs from blackbox testing and when to apply each.

You will also find scenario-based questions frequently asked in QA and software developer interviews that test your understanding of testing methodologies, code instrumentation, and test-driven development (TDD).

Whether you’re preparing for roles such as QA Engineer, Software Tester, or Automation Engineer, this section equips you with the knowledge and skills to perform effective whitebox testing and confidently answer related interview questions.

At Takluu, we focus on practical learning, ensuring you can apply whitebox testing techniques in real projects and succeed in your career journey.

AmbitionBox Logo

What makes Takluu valuable for interview preparation?

1 Lakh+
Companies
6 Lakh+
Interview Questions
50K+
Job Profiles
20K+
Users