From 55ff6e240b9d61d4a3e0c36dee53c6bb3d029eaf Mon Sep 17 00:00:00 2001 From: sand4rt Date: Thu, 13 Jun 2024 22:16:09 +0200 Subject: [PATCH] docs(ct): faq how to access the component instance --- docs/src/test-components-js.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/src/test-components-js.md b/docs/src/test-components-js.md index 099dc2b362..cdb065347e 100644 --- a/docs/src/test-components-js.md +++ b/docs/src/test-components-js.md @@ -928,3 +928,7 @@ test('override initialState ', async ({ mount }) => { await expect(component).toContainText('override initialState'); }); ``` + +### How do I access the component's methods or its instance? + +Accessing a component's internal methods or its instance within test code is neither recommended nor supported. Instead, focus on observing and interacting with the component from a user's perspective, typically by clicking or verifying if something is visible on the page. Tests become less fragile and more valuable when they avoid interacting with internal implementation details, such as the component instance or its methods. Keep in mind that if a test fails when run from a user’s perspective, it likely means the automated test has uncovered a genuine bug in your code.