🌍 Back-end Web Developement · flashcards

Back-end Web Developement Testing Flashcards

50 question-and-answer cards covering Testing as it is examined in Back-end Web Developement. 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.

50Cards in deck
24Free preview
7Syllabus topics
~161Chars per answer
FreePrice

24 sample cards from the Testing deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

  1. What are PyTest fixture scopes, and name them from narrowest to broadest?

    Scope controls how often a fixture is set up/torn down: function (default), class, module, package, and session (broadest, once per test session).

  2. What is Postman primarily used to test?

    Postman is an API development and testing platform used to build, send, and automate HTTP requests to test REST, SOAP, and GraphQL APIs and their responses.

  3. In Postman, what is a Collection?

    A Collection is a group of saved API requests (optionally organized into folders) that can be run, shared, and automated together as a suite.

  4. In which scripting language are Postman test scripts written, and where do they run?

    They are written in JavaScript and run in Postman's sandbox - either as pre-request scripts (before the request) or as test scripts (after the response).

  5. In Postman, how do you write an assertion on a response?

    Using pm.test("name", function(){ ... }) with assertions like pm.response.to.have.status(200) or pm.expect(value).to.eql(expected).

  6. What is the purpose of environment and collection variables in Postman?

    They store reusable values (like base URLs, tokens, or IDs) so requests can be parameterized and easily switched between contexts such as dev, staging, and production.

  7. What is Newman in the Postman ecosystem?

    Newman is Postman's command-line collection runner, used to execute Postman collections from the terminal or a CI/CD pipeline.

  8. What is Selenium and what does it automate?

    Selenium is an open-source suite for automating real web browsers, primarily used for functional and end-to-end testing of web applications across different browsers.

  9. What is Selenium WebDriver?

    WebDriver is the core Selenium component/API that drives a browser natively by communicating with browser-specific drivers (e.g. ChromeDriver, GeckoDriver) to simulate user actions.

  10. Name several programming languages officially supported by Selenium WebDriver.

    Java, Python, C#, Ruby, and JavaScript (among others) - Selenium provides language bindings for each.

  11. In Selenium, what are locators and give common examples.

    Locators are strategies to find elements on a page. Common ones: id, name, className, tagName, linkText, partialLinkText, CSS selector, and XPath.

  12. What is the difference between implicit and explicit waits in Selenium?

    An implicit wait sets a global timeout to poll for any element before failing, while an explicit wait (WebDriverWait) waits for a specific condition on a specific element and is generally preferred.

  13. What is Selenium Grid used for?

    Selenium Grid enables running tests in parallel across multiple machines, browsers, and operating systems by distributing tests to remote nodes via a hub/router.

  14. What is Cypress and what type of testing is it designed for?

    Cypress is a JavaScript-based front-end testing tool built for fast, reliable end-to-end, integration, and component testing of anything that runs in a browser.

  15. A key architectural difference: how does Cypress run relative to the application, compared to Selenium?

    Cypress runs directly inside the browser in the same run loop as the application (in-process), whereas Selenium controls the browser remotely from outside over a wire protocol.

  16. In Cypress, what does the cy object represent?

    cy is the global command object used to issue Cypress commands, e.g. cy.visit(), cy.get(), cy.click(), and cy.contains().

  17. What is automatic waiting (retry-ability) in Cypress?

    Cypress automatically waits and retries commands and assertions until the element appears/condition is met or a timeout is reached, reducing the need for manual/hard-coded waits.

  18. In Cypress, how do you make assertions?

    Using .should() or .and() with Chai-style assertions (e.g. cy.get('.item').should('have.length', 3)), or explicit expect() inside .then() blocks.

  19. What is a major browser limitation of Cypress compared to Selenium?

    Cypress historically supports a narrower set of browsers (Chromium-family, Firefox, WebKit/Electron) and runs tests only in JavaScript, while Selenium supports more browsers and many languages.

  20. What is TestCafe and what is its standout setup advantage?

    TestCafe is a Node.js-based end-to-end web testing framework whose standout advantage is that it requires no WebDriver or browser plugins/extensions - it works out of the box.

  21. How does TestCafe inject its automation into the page without WebDriver?

    It uses a URL-rewriting proxy (a reverse proxy) that injects the driver script into the page, letting it drive the browser without any external driver or browser extension.

  22. In TestCafe, what do fixture() and test() define?

    fixture() declares a group of tests (a page/feature under test), and test() defines an individual test case, which receives a t test controller for actions and assertions.

  23. How does TestCafe handle waiting for elements and requests?

    TestCafe has built-in automatic (smart) waiting for page loads, XHR/fetch requests, and elements, so explicit sleeps are usually unnecessary.

  24. Compare Selenium, Cypress, and TestCafe by their core technology/language.

    Selenium uses the WebDriver protocol with bindings in many languages (Java, Python, C#, etc.); Cypress runs in-browser and is JavaScript/TypeScript only; TestCafe is a proxy-based Node.js tool written in JavaScript/TypeScript that needs no WebDriver.

What this deck covers

The Testing deck follows the Back-end Web Developement Testing syllabus — 3 chapters and 7 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 16.7 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 161 characters, which is long enough to carry the reasoning and short enough to say out loud.

A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.

Testing flashcards FAQ

How many Testing flashcards are in this Back-end Web Developement deck?

50 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.

Are these Back-end Web Developement flashcards free?

Yes. The preview here is free to read with no signup, and the full 50-card deck is free inside the Examius app.

What do the Testing cards cover?

They follow the Back-end Web Developement Testing syllabus — 3 chapters and 7 topics — so the questions track what is actually examinable.

How should I use these flashcards?

Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.