diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-19 21:08:23 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-19 21:08:23 +0300 |
| commit | 3f0db3db2ad99a74c3969bf2e930814004ccf1ec (patch) | |
| tree | c8b4123b3b4b422b14211430b85556e64eb68a26 /doc/development/refactoring_guide | |
| parent | 4a721269429a178957e8ce7c6d0a75d3307c9830 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/refactoring_guide')
| -rw-r--r-- | doc/development/refactoring_guide/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/refactoring_guide/index.md b/doc/development/refactoring_guide/index.md index a25000589c0..a6ed83258f3 100644 --- a/doc/development/refactoring_guide/index.md +++ b/doc/development/refactoring_guide/index.md @@ -14,7 +14,7 @@ Pinning tests help you ensure that you don't unintentionally change the output o ### Example steps -1. Identify all the possible inputs to the refactor subject (e.g. anything that's injected into the template or used in a conditional). +1. Identify all the possible inputs to the refactor subject (for example, anything that's injected into the template or used in a conditional). 1. For each possible input, identify the significant possible values. 1. Create a test to save a full detailed snapshot for each helpful combination values per input. This should guarantee that we have "pinned down" the current behavior. The snapshot could be literally a screenshot, a dump of HTML, or even an ordered list of debugging statements. 1. Run all the pinning tests against the code, before you start refactoring (Oracle) |