SWISS RE IS HIRING : QA ENGINEER

QA Engineer I – Interview Questions and Sample Answers

1. Can you explain what manual testing is and why it is important?

Answer:

Manual testing is the process of manually checking the software for defects. As a tester, I execute test cases without using any automation tools. It helps in understanding the user perspective, especially for testing the user interface (UI), and is useful in early stages of development.It is important because:

• It helps find bugs that automation might miss.
• It allows flexibility to explore different parts of the application.
• It helps in verifying if new features work as expected before automating them.

2. What are the different types of testing you have worked on?

Answer:

I have worked on:

• Functional Testing: To check if the application works according to the requirements.
• Regression Testing: To make sure new changes haven’t broken existing features.
• UAT (User Acceptance Testing): Helping users test the application before going live.
• Automation Testing: Using tools like Selenium and Playwright to save time on repetitive tests.
• Performance Testing: Using JMeter or LoadRunner to see how fast the application works under load.

3. What is automation testing? Which tools do you use?

Answer:

Automation testing means writing scripts to test software automatically. It saves time and improves accuracy.I have used:

• Selenium: A tool for testing web applications using Java or Python.
• Playwright: A modern tool for end-to-end testing with support for multiple browsers.

These tools help me run the same tests faster and more reliably, especially for regression testing.

4. Can you explain a test case and a test scenario with an example?

Answer:

Yes.

• Test Scenario: A high-level idea of what to test.
  • Example: Check the login functionality.
• Test Case: Detailed steps to carry out the test.
  • Example:
    • Step 1: Open the login page.
    • Step 2: Enter a valid username and password.
    • Step 3: Click on the login button.
    • Expected Result: User should be logged in and redirected to the dashboard.

5. What are some common bugs you’ve found during testing?

Answer:

Some common bugs include:

• Broken links
• Button not clickable
• Incorrect error messages
• Page loading slowly
• Application crashes on certain inputs
• Data not saving correctly

Finding these bugs helps improve the quality of the software.

6. How do you report a bug in Jira?

Answer:

In Jira:

1. I create a new issue.
2. Set the issue type to Bug.
3. Add a clear summary and description.
4. Mention steps to reproduce, expected result, and actual result.
5. Attach screenshots or logs.
6. Set priority and assign it to the right developer.

This helps the developer understand and fix the issue quickly.

7. What is performance testing? How do you do it?

Answer:

Performance testing checks how fast and stable the application is under load.I use:

• JMeter: To simulate many users using the application at the same time.
• LoadRunner: For more detailed performance and stress testing.

This helps find bottlenecks and make sure the system doesn’t crash under heavy usage.

8. What is a CI/CD pipeline and why is it important?

Answer:

CI/CD stands for Continuous Integration and Continuous Deployment.

• CI means merging code regularly and testing it automatically.
• CD means automatically deploying code after testing.

I use Azure DevOps to manage this process. It’s important because it:

• Reduces manual work
• Catches bugs early
• Speeds up delivery of features

9. What is the difference between Selenium and Playwright?

Answer:

I am comfortable using both depending on the project needs.

10. How do you ensure test coverage for all features?

Answer:

To ensure full test coverage:

• I review the requirements carefully.
• I prepare a traceability matrix to map each requirement with test cases.
• I include positive, negative, boundary, and edge case test cases.
• I also work closely with developers and business analysts to ensure nothing is missed.