Feature Overview:
An elevator pitch (value statement) that describes the Feature in a clear, concise way. ie: Executive Summary of the user goal or problem that is being solved, why does this matter to the user?

This feature covers all the work associated to getting the QE workflow and infrastructure up and running in the RHAI build pipelines. This covers:

• MVP development work for the autoqa and taskotron servers
• Deployment of the servers
• Integration into AIPCC pipelines

Product(s) associated:

Every product which has a build pipeline and wants to run automatic integration tests on its artifacts.

Goals:
Provide high-level goal statement with user context and expected user outcome(s) for this Feature

• Every high level artifact will be tested automatically by RHAI QE integration tests after build
• Concise and centralized way how to integrate QE test steps into RHAI build pipelines
• Centralized way to view reports of tests

Requirements:
A list of specific needs, capabilities, or objectives that a Feature must deliver.

• TBA -

Done - Acceptance Criteria:
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view

• The autoqa server has all the necessary features (NOTE: this would need a MVP)
• The autoqa server is deployed in production env
• At lease one of the build pipelines has a test step integrated

Use Cases - i.e. User Experience & Workflow:
Include use case diagrams, main success scenarios, alternative flow scenarios.

• TBA -

Out of Scope:
High-level list of items or personas that are out of scope.

• This feature does not cover the integration of test steps to all of the RHAI build pipelines

Documentation Considerations :
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation.

• Internal documentation how to include a test step into a step would be necessary
• Internal documentation about the autoqa and taskotron would be necessary