Infosys Iconnect Interview Questions

https://www.techbeamers.com/manual-testing-interview-questions-experienced-qa/ 

I attended the Test Analyst role and all the questions were related to Testing, Testing Concepts, and Testing Methodologies the main focus was on Agile Methodologies questions and they asked me to derive scenarios for some examples.

Tips

Be clear on your basics, all questions will come from our daily activities itself

*Infosys Automation Testing Interview Questions

Company Location: Bangalore, India

Exp Range: 3 Year

Interview Date: 16.08.2022

Updated on: 01.09.2022

Submitted By: Achal Kumar

1.Can we time one test case for 5 min?

Yes, you can time a test case to run for a specific duration, such as 5 minutes. Timing a test case is a common practice in automated testing to ensure that it doesn't run indefinitely and to monitor its execution time.

Here's an example of how you can implement a test case with a maximum execution time of 5 minutes in Java using the TestNG testing framework:

```java

import org.testng.annotations.Test;

public class MyTest {

    @Test(timeOut = 300000) // 300,000 milliseconds = 5 minutes

    public void myTestCase() {

        // Your test logic goes here

        // This test will fail if it runs for more than 5 minutes

    }

}

```

In this example, we use the `@Test` annotation from TestNG and set the `timeOut` attribute to 300,000 milliseconds (5 minutes). If the test case takes longer to execute, it will be marked as failed. You can adapt this approach to other testing frameworks or programming languages as needed.

Keep in mind that setting a maximum execution time is useful for preventing tests from hanging indefinitely, but it's also important to optimize your test cases to run efficiently, as excessively long test cases can be a sign of underlying issues in your application or test suite.

2.How do you decide that you need a hybrid framework?

Deciding to use a hybrid testing framework in software testing is based on several factors and considerations. A hybrid framework combines different aspects of multiple testing frameworks (e.g., data-driven, keyword-driven, and modular-driven) to create a more flexible and robust testing solution. Here's how you can decide if you need a hybrid framework:

1. Complex Testing Requirements: If your application has complex testing requirements that cannot be adequately addressed by a single testing framework, a hybrid approach can provide a solution. For example, if you need to handle various types of tests, such as functional, regression, and performance testing, a hybrid framework can be beneficial.

2. Scalability: A hybrid framework is often a good choice when you expect your test suite to grow significantly over time. It can accommodate different types of tests and testing scenarios while maintaining test suite scalability.

3. Reusability: If you want to promote code reusability across test cases, modules, and different testing types, a hybrid framework allows you to create reusable components and libraries that can be shared across different test scripts.

4. Flexibility: A hybrid framework offers flexibility in selecting the best approach for different aspects of your testing. You can use data-driven techniques for data input, keyword-driven methods for test step management, and modular-driven approaches for test script organization, all within the same framework.

5. Maintainability: A well-designed hybrid framework can be easier to maintain because it promotes modularity and reusability. You can make changes or updates to a particular module or component without affecting other parts of the test suite.

6. Test Reporting: If you require comprehensive test reporting and result analysis, a hybrid framework can incorporate various reporting mechanisms and allow you to generate detailed test reports and logs.

7. Technology and Application Compatibility: Some applications or systems may require a mix of testing approaches due to their unique architecture or technology stack. A hybrid framework can adapt to the specific needs of your application.

8. Resource Availability: Consider the availability of skilled resources and the team's expertise. A hybrid framework may require knowledge in multiple testing approaches, so ensure that your team is capable of working with different testing techniques.

9. Cost and Time Constraints: Evaluate the cost and time constraints for your testing efforts. While a hybrid framework can offer many advantages, it may require more initial investment in terms of planning and development.

10. Testing Goals and Objectives: Finally, assess your testing goals and objectives. Determine whether a hybrid framework aligns with your testing strategy and objectives.

In summary, the decision to use a hybrid testing framework depends on the complexity of your testing requirements, the need for flexibility and scalability, and your team's capabilities. A hybrid framework can be a valuable solution when different testing techniques and approaches are necessary to achieve comprehensive and effective testing coverage.

3.If there are two test cases in the suite, what is the flow of execution?

The flow of execution for a test suite with two test cases typically follows this general sequence:

1. The test suite is initialized and any necessary dependencies or resources are set up.
2. The first test case is executed.
3. The results of the first test case are recorded and any necessary cleanup is performed.
4. The second test case is executed.
5. The results of the second test case are recorded and any necessary cleanup is performed.
6. The test suite is torn down, and any resources that were set up are cleaned up.

Note that the exact flow of execution may vary depending on the testing framework or tools being used, as well as the specifics of the individual test cases themselves. For example, some testing frameworks may allow for parallel execution of test cases, or may include additional steps such as test case discovery or reporting.

When answering the interview question about the flow of execution with two test cases in a test suite, you can provide a structured and concise response. Here's a sample answer:

"In a typical test suite with two test cases, the flow of execution follows these steps:

1. Test Suite Initialization: Before any test cases are executed, the test suite is initialized. This phase involves setting up any global or suite-level configurations, data, or resources that are common to both test cases. Initialization steps occur only once at the beginning of the test suite.

2. Execution of Test Case 1: The first test case is executed. During this phase, the test case script performs actions, interactions with the application, and validation steps as defined in the test case. If there are any setup steps specific to this test case, they are executed before the main test case steps.

3. Cleanup for Test Case 1: Following the execution of the first test case, any cleanup steps specific to this test case are performed. Cleanup steps may include resetting the application state, closing browser sessions, or releasing resources.

4. Execution of Test Case 2: The second test case is executed in a manner similar to the first test case. It follows its predefined steps and verifications. Like the first test case, any setup steps specific to this test case are executed before the main test case steps.

5. Cleanup for Test Case 2: After the execution of the second test case, any cleanup steps specific to this test case are performed.

6. Test Suite Cleanup: Once both test cases have been executed, the test suite cleanup phase is initiated. This involves releasing any remaining resources, closing open application sessions, or performing any other suite-level cleanup tasks. Similar to the test suite initialization, the suite cleanup is executed only once at the end of the test suite.

It's important to note that the exact flow of execution may vary depending on the testing framework and automation setup in use. Some testing frameworks offer flexibility in defining test case order and customized setups, such as parallel test execution or custom setup and teardown methods at various levels. The specific test suite configuration can also influence the order of test case execution."

4.Why relative XPath is preferred by automation developers

Automation developers often prefer using relative XPath expressions over absolute XPath expressions for several reasons:

1. Robustness: Relative XPath is less likely to break when the structure of the HTML or XML document changes. Absolute XPath expressions are dependent on the full path from the root of the document to the element, and any change in the document structure can render them invalid. Relative XPath expressions, on the other hand, are more flexible because they locate elements based on their relationship to other elements.

2. Readability: Relative XPath expressions are generally more readable and concise. They focus on the relationship between elements and provide context, making it easier to understand the purpose of the XPath.

3. Maintainability: Relative XPath expressions are easier to maintain because they are more resistant to changes in the document structure. When changes occur, you may only need to update a portion of the XPath, while with absolute XPaths, you might need to update the entire path.

4. Efficiency: Relative XPath expressions often require less typing and are quicker to write, which can improve development efficiency.

5. Reuse: Relative XPaths can be more reusable across different parts of a page or across similar pages. They are more likely to work for multiple elements that share the same relationship to their parent or sibling elements.

6. Portability: Relative XPaths are often more portable across different environments or browsers. They are less likely to be tied to a specific document structure or browser implementation.

7. Testing Framework Support: Many testing frameworks and libraries, such as Selenium, encourage the use of relative XPath expressions. They provide mechanisms for finding elements by relationships, CSS selectors, and other locators.

While relative XPath expressions have advantages, there can be cases where using absolute XPaths is necessary, especially when dealing with complex, deeply nested structures or when no unique relationships can be leveraged. However, it's a good practice for automation developers to prioritize relative XPath expressions when possible to create more robust and maintainable test scripts.

5.How to do database connection in selenium.

Selenium is primarily a web testing framework, and it doesn't provide built-in features for directly connecting to and interacting with databases. However, you can perform database operations within your test automation scripts by using external libraries and integrating them into your Selenium tests. Here's how you can establish a database connection in Selenium:

1. Choose a Database Library: Select a database library for your programming language that allows you to interact with the database. For Java, you can use libraries like JDBC (Java Database Connectivity) or third-party libraries like Hibernate or JPA. For Python, you can use libraries like SQLAlchemy or psycopg2 (for PostgreSQL).

2. Import the Library: Include the database library in your project by adding the necessary dependencies to your project's build or configuration file. For example, if you are using Java with JDBC, you would add the JDBC driver for your specific database (e.g., MySQL, Oracle, or PostgreSQL) as a dependency.

3. **Establish a Database Connection**: Use the library to establish a connection to the database. You'll typically need to provide connection details like the database URL, username, and password. Here's a simplified example using Java and JDBC to connect to a MySQL database:

   ```java

   import java.sql.Connection;

   import java.sql.DriverManager;

   import java.sql.SQLException;

   public class DatabaseConnection {

       public static void main(String[] args) {

           String dbUrl = "jdbc:mysql://localhost:3306/mydatabase";

           String username = "your_username";

           String password = "your_password";

           try {

               Connection connection = DriverManager.getConnection(dbUrl, username, password);

               // Now you have a database connection

           } catch (SQLException e) {

               e.printStackTrace();

           }

       }

   }

   ```

4. Perform Database Operations: Once you have established a connection, you can execute SQL queries and perform database operations using the methods provided by the database library. For example, you can retrieve data, insert records, update data, or delete records from the database.

5. Integrate with Selenium: You can now integrate the database operations into your Selenium tests. You might use the database connection to set up test data, verify data after actions in your web application, or perform other database-related verifications as part of your test scenarios.

Remember that you need to manage resources properly when working with database connections. Open a connection when needed and close it when you're done. Additionally, ensure that you handle exceptions and errors appropriately in your test scripts to maintain robust and reliable test automation.