Easy Automation Test Engineer questions
34 questions · 5 points each for a correct first answer.
- 1.Choosing a stable locatorlocators, ui-automationeasy
- 2.Waiting for an elementwaits, ui-automationeasy
- 3.Page Object Modelframework-designeasy
- 4.A test without assertionstest-designeasy
- 5.Headless modeui-automation, ci-cdeasy
- 6.Structure of a good testtest-designeasy
- 7.API or UI testtest-strategy, api-testingeasy
- 8.Where test code livesgit, framework-designeasy
- 9.The test pyramidtest-strategy, test-pyramideasy
- 10.Reading a CSS selectorlocators, css-selectorseasy
- 11.A missing awaitplaywright, async-javascripteasy
- 12.toBe versus toEqualassertions, javascripteasy
- 13.What a pytest fixture doespytest, fixtureseasy
- 14.BeforeEach or BeforeAlljunit, test-lifecycleeasy
- 15.Status code for a created resourceapi-testing, httpeasy
- 16.Which method is idempotentapi-testing, httpeasy
- 17.Postman collections in CIpostman, ci-cdeasy
- 18.Smoke suite or regression suitetest-strategy, smoke-testingeasy
- 19.What makes a test flakyflaky-testseasy
- 20.How Selenium talks to a browserselenium, webdrivereasy
- 21.Browsers Playwright coversplaywright, cross-browsereasy
- 22.Running tests in Dockerdocker, ci-cdeasy
- 23.Passwords in test codesecurity, ci-cdeasy
- 24.Why validate a JSON schemaapi-testing, json-schemaeasy
- 25.Boundary value inputstest-design, boundary-valueseasy
- 26.Equivalence partitioningtest-designeasy
- 27.What an end-to-end test istest-levelseasy
- 28.Using the trace viewerplaywright, debuggingeasy
- 29.Running only tagged teststest-organisation, ci-cdeasy
- 30.Screenshots on failuredebugging, reportingeasy
- 31.Triggering a workflowgithub-actions, ci-cdeasy
- 32.Naming a testtest-design, readabilityeasy
- 33.Reviewing test codecode-review, giteasy
- 34.Matching runner to languagetest-frameworkseasy