dokucama

This is an old revision of the document!

hierarchy typically looks like:

Unit testing (atomic level) - individual functions/methods. (Module testing often gets lumped into either “unit testing” (for simple modules) or “component testing” (for complex modules))
Component testing - groups of related units working together
Integration testing - multiple components interacting
System testing - entire application

TODO

Definition: Statements used in tests to verify that a specific condition holds true.
Usage: Typically done using Python's built-in
```
assert
```
statement.
Example:

    assert interface.status == "up"

Purpose: To validate correctness during test execution; a failed assertion marks the test as failed.

Examples:

@pytest.mark.skip(reason="Not implemented")

(skipping)

pyATS-specific:

@aetest.loop

,

@aetest.setup

,

@aetest.cleanup

    @pytest.fixture
    def test_device():
        device = connect_to_device("router1")
        yield device
        device.disconnect()

Purpose: Manage test environments and dependencies, ensuring isolation and reproducibility.

Definition: Technique to run the same test with different sets of parameters.
Usage: Implemented with
```
@pytest.mark.parametrize
```
.
Example:

    @pytest.mark.parametrize("ip", ["8.8.8.8", "1.1.1.1"])
    def test_ping(ip):
        assert ping(ip)

Testcase/Testscript:
- A testcase is a Python class, often subclassing
```
aetest.Testcase
```
  , containing test sections.
- A testscript is a file containing one or more testcases.
Sections:
- Special methods within a testcase, such as
```
setup
```
  ,
```
test
```
  , and
```
cleanup
```
  .
Testbed:
- A YAML or Python file describing devices and connections used in tests.
Loggers:
- Used for reporting test steps and results (
```
log
```
  object).
aetest:
- Core pyATS test harness module for organizing and running tests.