diff options
| author | Winnie Hellmann <winnie@gitlab.com> | 2018-11-13 12:33:04 +0000 |
|---|---|---|
| committer | Winnie Hellmann <winnie@gitlab.com> | 2018-11-13 12:33:04 +0000 |
| commit | 90c86b31c9ff1ae4b4013fc6bd3e88b2914fbac7 (patch) | |
| tree | 8fe0ac1f20a57d002d33366e6cc091a7b8da462f | |
| parent | 921d867806c6edeb06227f69bff8d87bbf255ea9 (diff) | |
| download | gitlab-ce-90c86b31c9ff1ae4b4013fc6bd3e88b2914fbac7.tar.gz | |
Make it explicit that we are referencing official Vue guidelines
| -rw-r--r-- | doc/development/new_fe_guide/development/testing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/new_fe_guide/development/testing.md b/doc/development/new_fe_guide/development/testing.md index 633a48b41df..5e9cc9141d7 100644 --- a/doc/development/new_fe_guide/development/testing.md +++ b/doc/development/new_fe_guide/development/testing.md @@ -56,7 +56,7 @@ Unit tests are on the lowest abstraction level and typically test functionality <summary>Vue components</summary> Computed properties, methods, and lifecycle hooks can be considered an implementation detail of components and don't need to be tested. They are implicitly covered by component tests. - The <a href="https://vue-test-utils.vuejs.org/guides/#getting-started">official guidelines</a> suggest the same. + The <a href="https://vue-test-utils.vuejs.org/guides/#getting-started">official Vue guidelines</a> suggest the same. </details> ### What to mock in unit tests |