Closed miherlosev closed 1 year ago
It seems to me that it might be a good idea to just directly use some of the vue-devtools
methods to do the work of finding nodes. I'm comparing their code to this plugin's and it seems that could be causing some of these problems.
I feel that I could help in solving some of these bugs, but you'll have to help me understand how to work with and debug a testcafe plugin.
I've copied the index.js
of this plugin to my directory and made some exploratory changes, but it seems that my console.log
calls and other attempts at actually understanding what's going on inside are being interfered with by the testing framework (or something)
I import the local source code into my fixture file
import { Selector } from 'testcafe'
// import VueSelector from 'testcafe-vue-selectors'
import VueSelector from './plugin'
fixture('Getting Started')
.page('http://localhost:8080')
// ...
But the code I've added, such as this, isn't output to the console.
// ...
}).addCustomMethods({
getVue: (node, fn) => {
console.log(node)
// ...
How do I go about actually debugging a testcafe selector plugin?
And my attempt at using the node debugger didn't work:
node inspect ./node_modules/testcafe -- 'chrome:headless' test/end-to-end/*.spec.js --app 'npm run dev' --app-init-delay 12000
I would love to help solve these problems. It's hard to work with a black box though ha.
This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.
We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.
Markup for reproduce:
Test for reproduce: