Branched from #2885127: Refactor tests as Unit and Functional.
Nightwatch documentation for contrib. is very sparse. And my previous efforts failed to get a Nightwatch test running on drupalci (let alone locally because chromedriver is required).
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | interdiff-3070113-7-9.txt | 5.52 KB | mradcliffe |
| #9 | cck_select_other-3070113-nightwatch-9.patch | 9.02 KB | mradcliffe |
| #7 | cck_select_other-3070113-nightwatch-7.patch | 9.5 KB | mradcliffe |
| #6 | cck_select_other-3070113-nightwatch-6.patch | 9.55 KB | mradcliffe |
| #5 | interdiff-3070113-4-5.txt | 6.67 KB | mradcliffe |
Comments
Comment #2
mradcliffeOld patch refactored to remind myself what it was doing before.
Comment #3
mradcliffeTries to install config for nodes manually?
Comment #4
mradcliffeConfirmed that testing profile is the one in-use so we do need to create content types ourselves.
Let's see if this will work. It didn't work in ddev, but I may not have nightwatch setup correctly. Ugh, it's a pain.
Comment #5
mradcliffeOkay, this should get the site installed with node + configuration enough to run a test.
But it still fails. I've tried going to /admin/structure/types/manage/page/form-display and confirming that the field is in the Content region and even saving it again, but it won't show up on /node/add/page. :|
testing profile sure doesn't make it easy to test.
Comment #6
mradcliffeThis patch only adds debug data because it's not possible to get screenshots yet and I can't run anything locally because my chromium is too old and chromium is worse than firefox at compiling.
Hope my debug statements work!
Comment #7
mradcliffeNope. PHPStorm decided to not give the actual API because it was guessing and not sure :|
Maybe manually adding a screenshot will just show up?
Comment #8
mradcliffeI give up again. It's taking too much of my time to figure out how to get Nightwatch to debug anything.
Comment #9
mradcliffeAll this patch does is re-order things so I don't expect anything since it was still failing locally yesterday. The form display some how either isn't being saved (it is, I can confirm it in the admin ui) or something else is utterly broken with the testing profile.
I don't find Nightwatch, the testing profile and the hard-coded use of chromedriver very easy to use with Drupal. It is not obvious how I can debug, console.log debug, screenshot debug, print_r debug without running out of memory. Documentation is still very sparse about how to get something actually working. I thought I found a core bug, but then it wasn't broken on the test bot so all I can think is that Nightwatch, like protractor, is very brittle.
Comment #10
mradcliffeWorked up on testing infrastructure. Sigh. I guess that's enough for a "working Nightwatch test" for some regression testing.
Comment #12
mradcliffe