Each checkbox job is meant to test one thing, this is why intermediate verifications are not supported within job.
Having said that, there is a way to create a chain of jobs, where next stage requires the previous one to pass [1].
Furthermore, checkbox makes distinction between three sections of descriptions: purpose, steps, verification. When used, each of those will be rendered on a separate ‘screen’ of the app.
By combining ‘depends’ field (chaining) and purpose/steps/verification fields expected behaviour can be achieved.
Each checkbox job is meant to test one thing, this is why intermediate verifications are not supported within job. steps/verificat ion fields expected behaviour can be achieved.
Having said that, there is a way to create a chain of jobs, where next stage requires the previous one to pass [1].
Furthermore, checkbox makes distinction between three sections of descriptions: purpose, steps, verification. When used, each of those will be rendered on a separate ‘screen’ of the app.
By combining ‘depends’ field (chaining) and purpose/
[1] http:// plainbox. readthedocs. org/en/ latest/ manpages/ plainbox- job-units. html?highlight= job%20unit