Avocado Test Writer’s Guide¶
- Writing an Executable Test
- Writing Avocado Tests with Python
- Basic example
- Multiple tests and naming conventions
- Convenience Attributes
- Test statuses
- Test methods
- Turning errors into failures
- Turning errors into cancels
- Saving test generated (custom) data
- Accessing test data files
- Accessing test parameters
- Running multiple variants of tests
unittest.TestCase
heritage- Running tests under other
unittest
runners - Setup and cleanup methods
- Running third party test suites
- Fetching asset files
- Test log, stdout and stderr in native Avocado modules
- Setting a Test Timeout
- Skipping Tests
- Canceling Tests
- Docstring Directives
- Declaring test as not being avocado-instrumented
- Declaring test as being avocado-instrumented
- (Deprecated) enabling recursive discovery
- Categorizing tests
- Python
unittest
Compatibility Limitations And Caveats - Environment Variables for Tests
- SIMPLE Tests BASH extensions
- Docstring Directives Rules
- Signal Handlers
- Wrap Up
- Advanced logging capabilities
- Test parameters
- Utility Libraries
- Subclassing Avocado
- Integrating Avocado