54. When you receive a new build, which test scripts do you execute first?
Answer:
We prioritize executing the Smoke Test suite first. Smoke tests are a subset of test cases that cover the most critical functionalities of the application. This ensures that the major features work correctly before proceeding with more detailed testing.
55. What is the role of Selenium in your project?
Answer:
Selenium is used for automating web application testing to ensure functionality, compatibility, and performance across different browsers and operating systems. It helps in:
- Automating repetitive test cases.
- Performing cross-browser testing.
- Integrating with CI/CD tools for continuous testing.
- Reducing manual testing effort and increasing test coverage.
56. How many modules have you worked on?
Answer:
I have worked on multiple modules, including:
- User Authentication Module.
- Product Management Module.
- Order Processing Module.
- Reporting and Analytics Module.
In each module, I was responsible for creating and maintaining automated test scripts, ensuring functionality, and integrating tests into the CI/CD pipeline.
57. What are your daily responsibilities in the office?
Answer:
My daily tasks include:
- Reviewing and analyzing new requirements.
- Writing and maintaining automated test scripts.
- Executing test cases and reporting defects.
- Collaborating with developers to resolve issues.
- Attending daily stand-up meetings to discuss progress and blockers.
58. How many test cases can you write in a month?
Answer:
The number of test cases I can write in a month depends on the complexity of the application and the requirements. On average, I can write and automate around 100-150 test cases per month, ensuring they are robust and maintainable.
59. How many test cases have you written in your last project?
Answer:
In my last project, I wrote approximately 500 automated test cases covering various functionalities, including login, user management, product catalog, and checkout processes. These tests were integrated into the CI/CD pipeline for continuous testing.
60. What processes did you follow in your last project?
Answer:
We followed Agile methodologies with the following processes:
- Sprint Planning: Defining the scope and objectives for each sprint.
- Daily Stand-ups: Discussing progress, blockers, and plans.
- Sprint Reviews: Demonstrating completed features and gathering feedback.
- Retrospectives: Analyzing what went well and areas for improvement.
- Continuous Integration/Continuous Deployment (CI/CD): Automating the build, test, and deployment processes.
61. How many builds do you get in one release?
In Agile development, the number of builds per release can vary. Typically, a sprint (usually two weeks) may have multiple builds, including nightly builds, integration builds, and release candidates. The exact number depends on the project’s complexity and requirements.
62. How many releases did you handle in your last project?
In my previous project, we followed a bi-weekly release cycle, resulting in approximately 24 releases over the year. Each release included new features, enhancements, and bug fixes, validated through automated TestNG suites.
63. How many bugs did you find in automation?
Automation testing helped identify numerous bugs, including regression issues, UI inconsistencies, and functional errors. The exact number varied per release, but automation significantly reduced manual testing efforts and improved defect detection rates.
64. Write an automation code for Login Page using TestNG:
java
@Test
public void loginTest() {
WebDriver driver = new ChromeDriver();
driver.get(“https://example.com/login”);
driver.findElement(By.id(“username”)).sendKeys(“testuser”);
driver.findElement(By.id(“password”)).sendKeys(“password123”);
driver.findElement(By.id(“loginBtn”)).click();
Assert.assertEquals(driver.getTitle(), “Dashboard”);
driver.quit();
}
65. When few out of 100 test scripts fail, what is your first approach?
First, I analyze the failed test cases to determine if the failures are due to script issues, application bugs, or environmental problems. I review logs, screenshots, and reports to identify root causes and take corrective actions accordingly.
66. When all 100 test scripts fail, what might be the issue?
If all test scripts fail, it could indicate a major issue such as application downtime, incorrect environment configuration, or problems with the test data. I would verify the application’s availability, environment settings, and data integrity to pinpoint the problem.
67. What were your roles & responsibilities in your last project?
My responsibilities included designing and developing automated test scripts using Selenium and TestNG, maintaining the test framework, integrating tests with Jenkins for CI/CD, and collaborating with the development team to ensure quality deliverables.
68. When did you start automation in your project?
Automation was initiated after the application’s core functionalities stabilized. We prioritized automating regression and smoke test cases to ensure quick feedback on code changes and reduce manual testing efforts.
69. What is not automatable?
Certain aspects like CAPTCHA, barcode scanning, and visual aesthetics are challenging to automate due to their dynamic nature and reliance on human perception. Such scenarios are better suited for manual testing.
70. What are the challenges in automation?
Challenges include handling dynamic web elements, synchronization issues, test data management, maintaining test scripts amid frequent UI changes, and ensuring cross-browser compatibility.
71. What automation process does your company follow?
We follow a structured automation process involving test case identification, script development using Selenium and TestNG, code review, integration with Jenkins for continuous testing, and regular maintenance of the test suite.
72. What is the entry and exit criteria for automation?
Entry Criteria:
Exit Criteria:
- All planned test cases automated
- Successful execution of test suites
- Defect resolution and verification
73. Why automation? What is the role of automation in regression?
Automation accelerates the testing process, enhances test coverage, and ensures consistency. In regression testing, automation quickly verifies that new code changes haven’t adversely affected existing functionalities.
74. If a set of manual test cases is given to you, what do you do first?
I review the test cases to identify candidates suitable for automation based on factors like repeatability and stability. Then, I prioritize and plan the automation development accordingly.
75. What is GitHub?
GitHub is a web-based platform for version control and collaboration, allowing multiple developers to work on projects simultaneously. It hosts code repositories and facilitates code sharing and management.
76. What is the role of GitHub in automation?
In automation, GitHub serves as a centralized repository for storing and managing test scripts. It enables version control, collaboration among team members, and integration with CI/CD tools like Jenkins.
78. What are the advantages of GitHub?
- Centralized code management
- Version control and history tracking
- Collaboration through pull requests and code reviews
- Integration with CI/CD pipelines
79. What is Maven?
Maven is a build automation tool used primarily for Java projects. It manages project dependencies, builds, and documentation through a standardized project object model (POM).
80. What is the role of Maven in your framework?
Maven manages project dependencies, compiles code, runs tests, and packages the application. It streamlines the build process and integrates with tools like Jenkins for continuous integration.
👉The Next 20 Questions-III: AUTOMATION TESTING
