Technical Questions

Question 2

What automation stack do you use? -

Question 3

NodeJS

Answer 3

which is based on

Question 4

Javascript

Answer 4

Cypress for the Ul and API test automation

Question 5

for running CI/CD.

Question 6

What frameworks/tools/libraries do you use? - Cypress for the Ul

Question 7

and API test automation

Answer 7

Github actions for running CI/CD

Question 8

What are the best candidates for test automation/What tests wouldyou automate first? -

Question 9

Regression testing

Answer 9

the most repetitive tests

Question 10

most complicated tests to do manually but easy to automate.

Question 11

Does it matter what stack/language is used for the applicationwhen you write test automation? -

Question 12

Not really

Answer 12

But it could be handy to

Question 13

use the same language as your devs use in case you need their help

Question 14

once upon a time :)

Question 15

Advantages:

Question 16

• Code reviews can be shared for both app and test code

Question 17

• Automated Ul test writers can easily understand what unit tests cover

Question 18

• Discussions use the same terminology without constant translation

Question 19

• reuse of infrastructure parts without change

Question 20

Disadvantages:

Question 21

• QA engineers may not have skills in the language used by application

Question 22

engineers

Question 23

• QA engineers may lose their independence

Question 24

• QA engineers may think more in terms of application code and less in

Question 25

terms of user experience

Question 26

How do you deal with Flaky tests?

Answer 26

To handle flaky tests in Cypress: First I'm investigate 1. **Debug Root Cause**: Use `cy.log()`, screenshots, or Cypress Dashboard to identify issues like timing or network failures. 2. **Isolate Tests**: Move flaky tests to a separate suite (e.g., `flaky.spec.js`) for focused debugging. 3. **Use Dynamic Waits**: Retest with `cy.get('#element', { timeout: 10000 }).should('be.visible')` instead of `cy.wait(3000)`. If waits don't resolve issue I will implement Retries**: If needed, set `"retries": { "runMode": 2, "openMode": 1 }` in `cypress.json`. 5. **Enhance Stability**: Mock APIs with `cy.intercept()`, reset state between tests, and ensure consistent test data. This approach resolves flakiness efficiently while avoiding hard-coded waits.

Question 27

How do you ensure that the automation that you’re writing doesn’t break? - See the next one below How do you write reliable and maintainable automated tests? - See the next one below How do you write robust automated tests? –

Answer 27

This question requires a lot of experience and knowledge of best practices: 1. Make sure to use static selectors(preferably custom attributes created specifically for QA, otherwise there will be much more maintenance) 2. Make tests isolated - should not have any dependencies (data, other tests, etc.) 3. Write reusable code - create functions when there is a code duplication 4. Use the Page Object Model to keep your code well organized, readable, and maintainable 5. Create data over API if possible - use API helper methods in the UI framework to prepare test data 6. Use retry library instead of sleep 7. From time to time do review your growing code base