Skip to content

Automation Testing Last-Minute Revision

Quickly revise the questions you picked. Add questions from the interview-questions lists with Save to → Last-Minute Revision.

30 quick revision notes for Automation Testing

  1. Implicit wait applies globally to findElement; explicit wait waits for a specific condition; never mix them in one framework.
  2. findElement throws NoSuchElementException when nothing matches; findElements returns an empty list instead.
  3. StaleElementReferenceException means the DOM was re-rendered; locate the element again instead of reusing the old reference.
  4. driver.close() closes the current window; driver.quit() ends the whole session and all windows.
  5. Selenium Manager, built into Selenium 4.6 and later, downloads the matching browser driver automatically for each run.
  6. Use switchTo().frame() for iframes, switchTo().window(handle) for tabs, and switchTo().alert() for JavaScript alerts.
  7. Shadow DOM elements are reached with getShadowRoot() and CSS selectors; XPath does not work inside shadow roots.
  8. TestNG order: BeforeSuite, BeforeTest, BeforeClass, BeforeMethod, Test, then the After methods in reverse order.
  9. A failed configuration method in TestNG causes dependent tests to be skipped, not failed.
  10. DataProvider repeats one test method with different data; Factory repeats a whole test class with different constructor data.
  11. Use alwaysRun = true on teardown methods so drivers are quit even after failures.
  12. SoftAssert collects failures and reports them only when assertAll() is called at the end of the test.
  13. Use ThreadLocal<WebDriver> so each parallel thread owns its own browser session, and call remove() after quit().
  14. Page objects hold locators and user actions for one page; the tests themselves hold the assertions.
  15. Prefer composition with reusable page components such as headers and modals over deep page inheritance chains.
  16. REST Assured follows given (setup), when (call), then (validate), with extract() to reuse values.
  17. Path params identify a resource like /users/{id}; query params filter results like ?page=2.
  18. POST creates and is not idempotent; PUT replaces and DELETE removes, and both should be idempotent.
  19. Status codes: 200 OK, 201 Created, 204 No Content, 400 Bad Request, 401 Unauthenticated, 403 Forbidden, 404 Not Found, 429 Too Many Requests, 500 Server Error.
  20. JSON schema validation catches structure and type changes that single field assertions miss.
  21. Scenario Outline runs once per Examples row; a DataTable passes a table into a single step.
  22. Cucumber creates new step definition instances per scenario; share state with dependency injection, not static fields.
  23. Write declarative Gherkin that states business intent, and keep UI clicks inside step definitions and page objects.
  24. Maven lifecycle order: validate, compile, test, package, verify, install, deploy; each phase runs all earlier ones.
  25. Surefire runs tests in the test phase and can point to testng.xml through suiteXmlFiles.
  26. Use mvn dependency:tree to find version conflicts that cause NoSuchMethodError at runtime.
  27. git merge keeps history with a merge commit; git rebase rewrites commits into a straight line, so never rebase shared commits.
  28. Use git revert to undo a pushed commit safely; git reset rewrites history and suits only local commits.
  29. In a declarative Jenkinsfile, the post always block is where you publish test results and archive screenshots.
  30. The test pyramid puts many unit tests at the base, fewer API tests in the middle and few UI tests at the top.

Night-before checklist

  • Revise your saved questions on this page once, aloud.
  • Read the quick notes and mark any you cannot explain in one line.
  • Rehearse a two-minute self-introduction and two project stories.
  • Keep CV, ID, laptop charger and interview link ready; sleep on time.

Frequently asked questions

How does Last-Minute Revision work?

On any question page, open Save to → Last-Minute Revision. Saved questions appear here with their answers, so the night before an interview you revise only what you found hard.

Is my list saved?

Yes, in this browser. Guests can save 5 questions; free accounts can save 20 for revision and 100 for the 7-day plan.

What should I revise last before a Automation Testing interview?

Your saved misses first, then the quick notes on this page, then one or two project stories. Avoid learning brand-new topics the night before.