FahdShalhoub
45 lines
1.8 KiB
Gherkin
45 lines
1.8 KiB
Gherkin
Feature: Transcoding status
|
|
A registered video starts life as "processing" and is handed to MediaConvert.
|
|
MediaConvert reports every job state change to an SNS topic, which fans the
|
|
event out to a queue cms consumes, so the catalogue record catches up with
|
|
the transcoding job on its own — nobody polls AWS and nothing is exposed for
|
|
AWS to call back into.
|
|
|
|
Background:
|
|
Given the CMS API is available
|
|
|
|
Scenario: A finished job marks the video ready
|
|
Given I have registered a video that is being transcoded
|
|
When MediaConvert reports that the job reached "COMPLETE"
|
|
Then the video eventually has status "ready"
|
|
|
|
Scenario Outline: A job that did not finish cleanly marks the video failed
|
|
Given I have registered a video that is being transcoded
|
|
When MediaConvert reports that the job reached "<state>"
|
|
Then the video eventually has status "failed"
|
|
|
|
Examples:
|
|
| state |
|
|
| ERROR |
|
|
| CANCELED |
|
|
|
|
Scenario Outline: A state that is not an outcome leaves the video processing
|
|
Given I have registered a video that is being transcoded
|
|
When MediaConvert reports that the job reached "<state>"
|
|
Then the video keeps status "processing"
|
|
|
|
Examples:
|
|
| state |
|
|
| SUBMITTED |
|
|
| PROGRESSING |
|
|
| STATUS_UPDATE |
|
|
|
|
# A message naming a job nobody has must be consumed and dropped, not left to
|
|
# redeliver forever. The second event is the assertion that it was: it can
|
|
# only be handled if the first one did not wedge the consumer.
|
|
Scenario: An event for a job no video has does not stop the consumer
|
|
Given I have registered a video that is being transcoded
|
|
When MediaConvert reports that the job "1700000000000-nosuchjob" reached "COMPLETE"
|
|
And MediaConvert reports that the job reached "COMPLETE"
|
|
Then the video eventually has status "ready"
|