Closed jan-molak closed 4 years ago
Merging #34 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #34 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 61 61
=========================================
Hits 61 61
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 6038fb0...adb15af. Read the comment docs.
Hey @Georgegriff! Thanks for your feedback, I'm glad you're happy with this PR :-) I've added an example to the readme and am planning to write a short tutorial to demonstrate how to use Serenity/JS with query-selector-shadow-dom
as soon as the new version of this lib lands in NPM.
I'd be happy to submit another PR linking to the article from the readme if you'd like?
Yeah any more documentation more than welcome
Hi again, @Georgegriff !
I've prepared a simple Angular Protractor plugin that addresses #33 and should integrate nicely with Serenity/JS I'm the author of, and which uses Protractor under the hood.
So starting from the outside, a person using Angular Protractor would need to configure their test runner in their
protractor.conf.js
to use thequery-selector-shadow-dom/plugins/protractor
Protractor plugin:You'll see this demonstrated in the end-to-end test I've added (see
test/protractor-locator.e2e.js
andprotractor.conf.js
)The plugin (at
plugins/protractor/index.js
) follows a very similar pattern you've already established for Playwright.Since both Serenity/JS and Protractor are written in TypeScript I've also added a
plugins/protractor/index.d.ts
file that describes the new method that the plugin registers on Protractor'sby
object.There's a couple of things I wasn't sure of, so would appreciate your feedback on.
test/
. I'm not sure if you're happy with this location or if I should move that file somewhere else?npm run e2e:protractor
to the CI config too, but not to regularnpm test
since that might interfere with running Karma in watch mode.by.shadowDomCss
, which may or may not be the best name for it. I've consideredby.shadowCss
but that didn't seem correct (it's a shadow DOM, not a shadow CSS after all) andby.querySelectorShadowDom
, but that seemed a bit wordy.If you find this PR too large or out of scope for this project please let me know and I can release it as a separate lib with a dependency on yours, I don't mind.
Looking forward to hearing your thoughts!
Jan