Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ Docs ] Document Steps for Container validation #313

Open
2 tasks
TechnicallyWilliams opened this issue Sep 24, 2019 · 0 comments
Open
2 tasks

[ Docs ] Document Steps for Container validation #313

TechnicallyWilliams opened this issue Sep 24, 2019 · 0 comments
Assignees
Labels
documentation Applies to documentation and diagrams effort - medium 2 day effort pri-Med Medium priority issue

Comments

@TechnicallyWilliams
Copy link
Contributor

TechnicallyWilliams commented Sep 24, 2019

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Applies to documentation and diagrams effort - medium 2 day effort pri-Med Medium priority issue
Projects
None yet
Development

No branches or pull requests

1 participant