Skip to content

[ Docs ] Document Steps for Container validation #313

@TechnicallyWilliams

Description

@TechnicallyWilliams

Description

*As a user, I'd like some guidance for how to check and test for a running container.

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

  • Documentation should highlight preexisting conditions for a running container
  • Documentation should include screenshots of configuration menus that demonstrate that all conditions have been met for running a container. (App settings, Webhook, etc.)

Resources

Technical Design Document
Mockups

Tasks

Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic.
Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)

Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)

Assignee should break down work into tasks here

  • Begin documenting path for checking a running container.

Metadata

Metadata

Labels

documentationApplies to documentation and diagramseffort - medium2 day effortpri-MedMedium priority issue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions