GlossaryΒΆ
- Case Execution
- The record of a specific run of a Test Case. The execution
has a description, start time, end time, result, and a reference to the
Test Case that it is for. Linked through the
test_cycle_test_case_execution
table to one or more Test Cycles. Case Executions also have meta information attached to them through Execution Batchs. Stored in thetest_case_execution
table, represented by theCaseExecution
model. - Default Case
- Each Execution Batch has a default Test Case associated with it. This case is used to generate Case Execution records that act as the current Test Case while the executor is outside of a test scope. This is primarily provided so that plugins have an entity to associate data to (such as log messages) when a test is not currently executing.
- Execution Batch
- A collection of meta information about a set of tests run together in a
single execution process. Provides data on batch start and end time,
execution host, environment, and nosetests command line options. Stored
in the
execution_batch
table, represented by theExecutionBatch
model. - Plugin Manager
- An object registered via the managers entrypoint that implements Sneeze plugin runtime behaviors via the plugin API.
- Test Case
- A particular set of operations and validations defined by a nose test.
Test Cases have a label and id. Stored in the
test_case
table, represented by theCase
model. - Test Cycle
- A collection of Case Executions with a name, label, and id.
Stored in the
test_cycle
table, represented by theTestCycle
model.