The questions were mostly generic testing theory questions, including basic concepts such as black-box testing. I did not feel there was enough focus on practical senior-level QA automation topics such as framework architecture, coding decisions, web testing strategy, API/UI automation design, CI/CD integration, debugging flaky tests, or real project scenarios.
1. git and cucumber
4.multithrading, Jenkins, can we write 2 mains in a class
Got a website with many bugs. Make a table discribing all the bugs.
Screenshot snippet Webdriver coding, import statements, read data from excel file
Experiencia con Selenium, .Net o Java. Jenkins.
Basic selenium and high-level java questions
Asked questions depending on my cv
automation, java , testng, selenium , agile , jira , cucumber, bdd , page object model
Logging and reporting Able to connect to the project and use basic reporting features Has theoretical knowledge and pros/cons of using custom reporting Understanding log levels and configurations Using simple existing log classes and methods Ability to integrate reporting into CI/CD Ability to modify code to do changes and customization according to project's needs Ability to use properties, layout, filters Ability to customize storage options for logs and screens Ability to create own custom extension/library based on existing (using http/s endpoint) Ability to use logs for notifications and for collecting/diagnostic/analytics
Viewing 3241 - 3250 interview questions