Skip to content

Template Testing #352

Description

@ianphil

Description

As a user, I would like to understand how to test a template, so that I can insure changes do not cause regressions.

Acceptance Criteria

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

  • Should test the template created in story Create a new template #349
  • Should detail how and where to put the test
  • Should explain how to run the test and debug
  • Should explain how the test is run during CI/CD

Also, here are a few points that need to be addressed:

  1. See stub file for this story: docs/4_STACK_TESTING.md

Resources

Epic #346

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

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions