Skip to content

{doc} Add Scenario Test Best Practice section in authoring_tests#22760

Merged
kairu-ms merged 6 commits intodevfrom
kairu-ms-patch-2
Jun 8, 2022
Merged

{doc} Add Scenario Test Best Practice section in authoring_tests#22760
kairu-ms merged 6 commits intodevfrom
kairu-ms-patch-2

Conversation

@kairu-ms
Copy link
Copy Markdown
Contributor

@kairu-ms kairu-ms commented Jun 7, 2022

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature


This checklist is used to make sure that common guidelines for a pull request are followed.

Copy link
Copy Markdown
Collaborator

@yonzhan yonzhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If all combinations of parameters are covered, the existing examples are automatically covered, right?

@yonzhan yonzhan added this to the Jun 2022 (2022-07-05) milestone Jun 7, 2022
@yonzhan
Copy link
Copy Markdown
Collaborator

yonzhan commented Jun 7, 2022

This is a good practice to incorporate boundary condition in test cases.

Co-authored-by: Jiashuo Li <4003950+jiasli@users.noreply.github.com>
@kairu-ms kairu-ms requested a review from wangzelin007 June 8, 2022 01:50
kairu-ms and others added 2 commits June 8, 2022 10:05
Co-authored-by: ZelinWang <zelinwang@microsoft.com>
Co-authored-by: ZelinWang <zelinwang@microsoft.com>
Co-authored-by: Jiashuo Li <4003950+jiasli@users.noreply.github.com>
@kairu-ms kairu-ms merged commit 199a43c into dev Jun 8, 2022
@kairu-ms kairu-ms deleted the kairu-ms-patch-2 branch November 1, 2022 05:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants