Ques:- What is traceability matricks
Asked In :-
Polestar Solutions & Services India LLP, Incap, smiths detection, dealersocket, roblox, grm, starship technologies,
Ques:- What is the difference between severity and priority? Tellme example.
Asked In :-
NISC Exports Services (p), DSVV,
Ques:- What is security Hole ? Is this possible Some one can acess any of restricted page (like admin side)? How you test this previllaze?
Ques:- What are the testing methodologies?
Asked In :-
Right Answer:
The testing methodologies include:
1. **Black Box Testing** - Testing without knowledge of the internal workings.
2. **White Box Testing** - Testing with knowledge of the internal code and logic.
3. **Gray Box Testing** - Combination of black box and white box testing.
4. **Unit Testing** - Testing individual components or functions.
5. **Integration Testing** - Testing combined parts of an application to ensure they work together.
6. **System Testing** - Testing the complete and integrated software system.
7. **Acceptance Testing** - Testing to determine if the system meets business requirements.
8. **Regression Testing** - Testing to ensure that new changes haven't adversely affected existing functionality.
9. **Performance Testing** - Testing to evaluate the speed, scalability, and stability under load.
10. **Security Testing** - Testing to identify vulnerabilities and ensure data protection.
The testing methodologies include:
1. **Black Box Testing** - Testing without knowledge of the internal workings.
2. **White Box Testing** - Testing with knowledge of the internal code and logic.
3. **Gray Box Testing** - Combination of black box and white box testing.
4. **Unit Testing** - Testing individual components or functions.
5. **Integration Testing** - Testing combined parts of an application to ensure they work together.
6. **System Testing** - Testing the complete and integrated software system.
7. **Acceptance Testing** - Testing to determine if the system meets business requirements.
8. **Regression Testing** - Testing to ensure that new changes haven't adversely affected existing functionality.
9. **Performance Testing** - Testing to evaluate the speed, scalability, and stability under load.
10. **Security Testing** - Testing to identify vulnerabilities and ensure data protection.
Ques:- What is Virtual Users?
Asked In :-
Right Answer:
Virtual users are simulated users created by performance testing tools to mimic real user interactions with an application during load testing. They help assess how the application performs under various levels of user load.
Virtual users are simulated users created by performance testing tools to mimic real user interactions with an application during load testing. They help assess how the application performs under various levels of user load.
Ques:- If yahoo ceo asks you to do performance testing for yahoosite, what are the inputs you ask from them?
Asked In :-
Right Answer:
1. Performance goals and benchmarks (e.g., response time, throughput).
2. User load expectations (e.g., number of concurrent users).
3. Test environment details (e.g., hardware, software, network configuration).
4. Specific scenarios to test (e.g., user journeys, peak usage times).
5. Historical performance data (if available).
6. Acceptance criteria for performance testing.
7. Tools and technologies preferred for testing.
8. Any existing performance issues or concerns.
1. Performance goals and benchmarks (e.g., response time, throughput).
2. User load expectations (e.g., number of concurrent users).
3. Test environment details (e.g., hardware, software, network configuration).
4. Specific scenarios to test (e.g., user journeys, peak usage times).
5. Historical performance data (if available).
6. Acceptance criteria for performance testing.
7. Tools and technologies preferred for testing.
8. Any existing performance issues or concerns.
Ques:- Please any on explain usage of “on error resume next”,”Onerror goto 0″ with sample code….Thankyou………when a tester is asked to execute 100 scripts in a shorttime..(the server will be down in another 10 min)..how hehas to run those scripts?
Asked In :-
Right Answer:
`On Error Resume Next` is used in VBScript to ignore runtime errors and continue executing the next line of code. `On Error GoTo 0` disables this error handling, allowing the script to stop on errors.
**Sample Code:**
```vbscript
On Error Resume Next
' Attempt to open a non-existent file
Dim fso, file
Set fso = CreateObject("Scripting.FileSystemObject")
Set file = fso.OpenTextFile("nonexistent.txt")
If Err.Number <> 0 Then
WScript.Echo "Error occurred, but continuing..."
Err.Clear ' Clear the error
End If
' Continue with other operations
WScript.Echo "Continuing with the script..."
On Error GoTo 0 ' Disable error handling
```
To execute 100 scripts in a short time when the server will be down in 10 minutes, the tester can use a loop to run the scripts concurrently or in quick succession, ensuring to handle
`On Error Resume Next` is used in VBScript to ignore runtime errors and continue executing the next line of code. `On Error GoTo 0` disables this error handling, allowing the script to stop on errors.
**Sample Code:**
```vbscript
On Error Resume Next
' Attempt to open a non-existent file
Dim fso, file
Set fso = CreateObject("Scripting.FileSystemObject")
Set file = fso.OpenTextFile("nonexistent.txt")
If Err.Number <> 0 Then
WScript.Echo "Error occurred, but continuing..."
Err.Clear ' Clear the error
End If
' Continue with other operations
WScript.Echo "Continuing with the script..."
On Error GoTo 0 ' Disable error handling
```
To execute 100 scripts in a short time when the server will be down in 10 minutes, the tester can use a loop to run the scripts concurrently or in quick succession, ensuring to handle
Ques:- What is show stopper bug pls explain,pls give any real timebug u get in your project
Asked In :-
Right Answer:
A show stopper bug is a critical defect that prevents the software from functioning at all, making it impossible to proceed with testing or use the application. For example, if a banking application crashes when a user tries to log in, this would be a show stopper bug, as it halts all user access to the system.
A show stopper bug is a critical defect that prevents the software from functioning at all, making it impossible to proceed with testing or use the application. For example, if a banking application crashes when a user tries to log in, this would be a show stopper bug, as it halts all user access to the system.
Ques:- What is your company testcase format?
Asked In :-
Right Answer:
Our company test case format includes the following fields:
1. Test Case ID
2. Test Case Title
3. Description
4. Preconditions
5. Test Steps
6. Expected Result
7. Actual Result
8. Status (Pass/Fail)
9. Comments/Notes
10. Author
11. Date Created
12. Last Updated
Our company test case format includes the following fields:
1. Test Case ID
2. Test Case Title
3. Description
4. Preconditions
5. Test Steps
6. Expected Result
7. Actual Result
8. Status (Pass/Fail)
9. Comments/Notes
10. Author
11. Date Created
12. Last Updated
Ques:- What will be verification and validation test cases foryahoo login page (only functional test cases)?Please explain in details.
Asked In :-
Right Answer:
**Verification Test Cases:**
1. **UI Elements Check:**
- Verify that the login page displays the Yahoo logo.
- Verify that the username and password fields are present.
- Verify that the "Sign In" button is visible.
2. **Field Labels:**
- Verify that the username field is labeled correctly.
- Verify that the password field is labeled correctly.
3. **Input Field Types:**
- Verify that the username field accepts text input.
- Verify that the password field masks input characters.
4. **Link Verification:**
- Verify that the "Forgot password?" link is present and clickable.
- Verify that the "Create an account" link is present and clickable.
**Validation Test Cases:**
1. **Valid Login:**
- Enter valid username and password, and verify successful login.
2. **Invalid Username:**
- Enter an invalid username and valid password, and verify an error message is displayed.
3
**Verification Test Cases:**
1. **UI Elements Check:**
- Verify that the login page displays the Yahoo logo.
- Verify that the username and password fields are present.
- Verify that the "Sign In" button is visible.
2. **Field Labels:**
- Verify that the username field is labeled correctly.
- Verify that the password field is labeled correctly.
3. **Input Field Types:**
- Verify that the username field accepts text input.
- Verify that the password field masks input characters.
4. **Link Verification:**
- Verify that the "Forgot password?" link is present and clickable.
- Verify that the "Create an account" link is present and clickable.
**Validation Test Cases:**
1. **Valid Login:**
- Enter valid username and password, and verify successful login.
2. **Invalid Username:**
- Enter an invalid username and valid password, and verify an error message is displayed.
3
Ques:- There is a mobile phone and it has got 2 buttons one is it takes photo other is it uploads photo to facebook how to you test this application ?
Asked In :-
testhouse,
Right Answer:
To test the application, I would perform the following steps:
1. **Functionality Testing**:
- Verify that the photo button takes a clear photo.
- Check that the upload button successfully uploads the photo to Facebook.
2. **Usability Testing**:
- Ensure the buttons are easy to locate and use.
- Test the app's response time when taking and uploading photos.
3. **Integration Testing**:
- Confirm that the photo uploads correctly to the user's Facebook account.
- Check for any errors or issues during the upload process.
4. **Performance Testing**:
- Measure the time taken to take a photo and upload it.
- Test the app under different network conditions (Wi-Fi, 4G, etc.).
5. **Error Handling**:
- Test how the app behaves when the upload fails (e.g., due to no internet).
- Check for appropriate error messages and recovery options.
6. **Compatibility Testing**:
To test the application, I would perform the following steps:
1. **Functionality Testing**:
- Verify that the photo button takes a clear photo.
- Check that the upload button successfully uploads the photo to Facebook.
2. **Usability Testing**:
- Ensure the buttons are easy to locate and use.
- Test the app's response time when taking and uploading photos.
3. **Integration Testing**:
- Confirm that the photo uploads correctly to the user's Facebook account.
- Check for any errors or issues during the upload process.
4. **Performance Testing**:
- Measure the time taken to take a photo and upload it.
- Test the app under different network conditions (Wi-Fi, 4G, etc.).
5. **Error Handling**:
- Test how the app behaves when the upload fails (e.g., due to no internet).
- Check for appropriate error messages and recovery options.
6. **Compatibility Testing**:
Ques:- How smoke testing is done with example??
Asked In :-
Ques:- Can u write Script to do Data Driven Testing throuh Externel & internel XL Sheet
Asked In :-
Ques:- How do you carry usability testing?
Asked In :-
Right Answer:
Usability testing is carried out by observing real users as they interact with the product to complete specific tasks. This involves creating test scenarios, recruiting participants, facilitating the testing sessions, collecting feedback, and analyzing the results to identify usability issues and areas for improvement.
Usability testing is carried out by observing real users as they interact with the product to complete specific tasks. This involves creating test scenarios, recruiting participants, facilitating the testing sessions, collecting feedback, and analyzing the results to identify usability issues and areas for improvement.
Ques:- What are the types of testing
Asked In :-
Right Answer:
1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing
5. Regression Testing
6. Performance Testing
7. Load Testing
8. Stress Testing
9. Security Testing
10. Usability Testing
11. Compatibility Testing
12. Smoke Testing
13. Sanity Testing
14. Alpha Testing
15. Beta Testing
1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing
5. Regression Testing
6. Performance Testing
7. Load Testing
8. Stress Testing
9. Security Testing
10. Usability Testing
11. Compatibility Testing
12. Smoke Testing
13. Sanity Testing
14. Alpha Testing
15. Beta Testing
Ques:- Can you plz tell me the all documents to be completed by a manual tester?
Asked In :-
Right Answer:
The documents to be completed by a manual tester typically include:
1. Test Plan
2. Test Case Document
3. Test Script
4. Test Data
5. Test Execution Report
6. Defect Report/Bug Report
7. Test Summary Report
8. Traceability Matrix
9. Test Closure Report
The documents to be completed by a manual tester typically include:
1. Test Plan
2. Test Case Document
3. Test Script
4. Test Data
5. Test Execution Report
6. Defect Report/Bug Report
7. Test Summary Report
8. Traceability Matrix
9. Test Closure Report
Ques:- How u track bugs using Test director in manual testing.
Asked In :-
Right Answer:
To track bugs using TestDirector in manual testing, follow these steps:
1. **Log In**: Access TestDirector with your credentials.
2. **Create a Project**: Select or create a project for your testing.
3. **Enter Bugs**: Navigate to the "Defects" module and click on "Add" to create a new bug report.
4. **Fill Details**: Enter the necessary details such as summary, description, severity, status, and steps to reproduce.
5. **Assign**: Assign the bug to the appropriate team member for resolution.
6. **Update Status**: As the bug is worked on, update its status (e.g., Open, In Progress, Fixed, Closed).
7. **Generate Reports**: Use the reporting features to track bug trends and status over time.
This process helps in effectively managing and tracking bugs throughout the testing lifecycle.
To track bugs using TestDirector in manual testing, follow these steps:
1. **Log In**: Access TestDirector with your credentials.
2. **Create a Project**: Select or create a project for your testing.
3. **Enter Bugs**: Navigate to the "Defects" module and click on "Add" to create a new bug report.
4. **Fill Details**: Enter the necessary details such as summary, description, severity, status, and steps to reproduce.
5. **Assign**: Assign the bug to the appropriate team member for resolution.
6. **Update Status**: As the bug is worked on, update its status (e.g., Open, In Progress, Fixed, Closed).
7. **Generate Reports**: Use the reporting features to track bug trends and status over time.
This process helps in effectively managing and tracking bugs throughout the testing lifecycle.
Ques:- If you have 2 versions of a software (v1.0 & v1.1) and you are testing v1.0. How do you confirm that the defects found in v1.0 have been fixed and have not migrated to v1.1 ?
Asked In :-
Integra Micro Software Services (P),
Ques:- When we enter wrongpaasword and wrong userid in login pageand click on ok.it did not display that error msg. itdisplays that which page we want.what type of testing is this1)functional testing 2)security testing
Asked In :-
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.
