Sounds like you are over complicating things... The component tests should cover components styling and CSS (including CSS variables that can be affected externally)... Integration tests (and beyond) shouldn't care about that... End To End or Integration tests should just be confirming proper input nets proper output (or page/view changes etc).
-Karl Tiedt On Mon, Oct 2, 2017 at 1:20 PM, <peterse...@gmail.com> wrote: > We have a website that in each page there are multiple components, so we > need to run acceptance tests to pierce each component and test them > > On Friday, September 29, 2017 at 12:09:09 PM UTC-6, Karl Tiedt wrote: >> >> The more important question... why do you feel you need /deep/ to test >> components? >> >> -Karl Tiedt >> >> On Fri, Sep 29, 2017 at 12:58 PM, <peter...@gmail.com> wrote: >> >>> I will reply with something i found on slack overflow >>> >>> "The piercing selector is being dropped (/deep/ and >>>). There's >>> currently no other alternative to search through the whole DOM with a >>> single query. The current solution is to implement a custom selector >>> <https://github.com/angular/protractor/issues/4367#issue-240858568> taking >>> multiple CSS segments to search each context" >>> >>> On Thursday, September 28, 2017 at 9:18:01 AM UTC-6, peter...@gmail.com >>> wrote: >>>> >>>> My organization is going to be moving to Polymer 2 and with that they >>>> will have to move away from the shady dom to the shadow dom. I do know that >>>> /deep/ is being deprecated? Is there going to be something that will >>>> substitute for /deep/ that we can use in place when using Selenium and >>>> Protractor and Mocha? >>>> >>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Polymer" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to polymer-dev...@googlegroups.com. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/polymer-dev/52149efb-bb20-46ce-aa38-dafe9c708adc%40googlegroups.com >>> <https://groups.google.com/d/msgid/polymer-dev/52149efb-bb20-46ce-aa38-dafe9c708adc%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> Follow Polymer on Google+: plus.google.com/107187849809354688692 > --- > You received this message because you are subscribed to the Google Groups > "Polymer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to polymer-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/polymer-dev/0f92cce9-a733-4391-8b7d-dacc1f70620f%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/0f92cce9-a733-4391-8b7d-dacc1f70620f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CADNgbTFQTh7eFgSVtE8iMOugUWB8KxYADty5dhiJHhtJaZ7k-w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
