With POM, each web page in an application should have a corresponding page class that represents all of the
elements on the page

A page class using POM should include verification tests

Using a Page Object Factory, we would identify a web element named "uid" using the following code:

@By(name = "uid")
WebElement userName;

To instantiate the web elements when using POF, we call the initElements method of the PageFactory class:
PageFactory.initElements(driver, this);

The Page Object Model and the Page Object Factory are primarily for tests written in Java

With Selenium WebDriver, using implicit waits are always preferable to using explicit waits or using thread.sleep.

One of the advantages of DDT is that test scripts connect only to internal resources, increasing security.

When using Apache POI, XSSF is for older Excel files and HSSF is for newer Excel files and OOXML files

When reading an Excel file using Apache POI, you would use
FileInputStream excelFile = new FileInputStream(new File(FILE_NAME));
and then instantiate the necessary XSSF or HSSF objects.

A hybrid framework always consists of a combination of data-driven and keyword-driven testing.

Test driven development is easy to adapt to legacy code

ode smells are usually bugs—they may not be technically incorrect but may currently prevent the program from
functioning.

The average iteration in an agile team is known as a run, often lasting 2-4 weeks

When using TestNG for unit testing, we can use the @Test annotation at the class level so that all public methods
are considered tests.

The only accurate documentation is our code.
The code is what we develop, what we deploy, and is the only source that truthfully represents our application

While TDD, which is based on unit level, can be described as outside-in (we begin with units and build in towards
functionalities), BDD is often understood as inside-out (we start with features and go outside towards units).

Behavior-driven development can be used as an acceptance criteria that acts as an indicator of readiness telling us
when something is finished and ready for production

Steps are a sequence of preconditions, events, and expected outcomes of the scenario.

Each BDD scenario is very similar to a unit test, with the main difference being the scope (one method against a
whole feature) and time it takes to implement it (a few seconds or minutes against a few hours or even days).

Question 38 1 / 1 point
Unlike unit tests, which were written as code by developers for developers, BDD scenarios should be defined
in specific language and with maximum technical details so that only those involved with the project who have the
necessary technical knowledge can have an in-depth understanding about behaviors (or features) that will be added
to the system.

Each BDD scenario consists of a description and one or more steps that start with the words Who, What, or Where.

There is a decreasing number of organizations that are employing testers as integral members of the developmen
team with the job of ensuring that quality is built in.

Using code as documentation does not exclude other types. Quite the contrary, the key is not to avoid using static
documentation, but to avoid duplication.

Looking at the code to understand the code is often enough to figure out its purpose.

The executable documentation obtained through unit tests is often enough; we get insights into details making it
easy to see the big picture.

Some people and companies forget about the value of automated testing and rely on users in what are called user
acceptance tests consisting of recreating real-world scenarios in a controlled environment, ideally identical to
production.

All of the design principles introduced by the textbook are applicable and desirable in both test and non-test driven
development, because, apart from other benefits, they make our code more maintainable.

Primitive Obsession involves using primitive data types to represent domain ideas

Many times, legacy code is tightly coupled and presents other symptoms that show a poor design or at least a lack
of interest in the code's quality in the past.

A Kata is an exercise that defines some requirements or fixed features to be implemented in order to achieve some
goals

The major activities involved in keyword-driven testing are
Identifying low level as well as high-level, Implementing the keyword as exe,Creating test cases,Creating the driver scripts,Executing the automation test scripts
keywords

One benefit of keyword-driven testing is that test automation can be planned before the application is completed

DDT goal to seperate data from scripts