Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix typos #339

Merged
merged 1 commit into from
Jul 9, 2024
Merged

Fix typos #339

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/getting-started/first-steps.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ These classes are Context-aware, and can be used to represent a container for th
Test Nodes
----------

A test node is the logcial representation of a :ref:`test container <test-containers>`.
A test node is the logical representation of a :ref:`test container <test-containers>`.
It encapsulates the logic of a specific context and provides useful APIs to interact with the container.

To represent a node within the environment, implement a class that inherits from
Expand Down Expand Up @@ -357,7 +357,7 @@ Default Fixtures
Each component of the setup has its own `parameterized fixtures set <https://docs.pytest.org/en/latest/how-to/parametrize.html>`_.
These fixtures are responsible for generating the environment matrix and providing the test nodes for each test case.

Each of these components can be independently manipulated by hooking into the matching ``defualt_`` fixtures of the component,
Each of these components can be independently manipulated by hooking into the matching ``default_`` fixtures of the component,
as some of the following examples will show.

Test Worker
Expand Down