Corporate pushed a change to our PC's which similataneously installed chrome and pushed their security policies on us. Extensions are no longer available. I can't sign in with my chrome account anymore. I can't automate ui testing with selenium. I can't control any chrome settings, they're controlled by group policies now.

I guess it's time to switch to Firefox. At least until they block that. At least the UI testing still is functional on that...

  • 4
    I guess you'll have to do UI testing on a VM that is not on the corporate AD domain.
  • 1
    @SomeNone That's a good point. I don't have any VMs setup. I do have a spare server setup for build automation that hasn't been fully fleshed out yet. I can start throwing VMs on there.
  • 3
    Maybe rip the computer out, get it to IT and speak your mind.

    I know that certain policies make sense. And I'm usually the first one who shouts: don't give the devs what they want, it will end in a barbecue armageddon.

    But... Completely destroying existing workflows without alternatives isn't helping (so long the workflow isn't utterly wrong - and in case of Selenium / trusted extensions, I don't think so.)
  • 1
    @IntrusionCM you have a point. I'll bring it up saying that it broke automated tested. See if I can be put in a special OU which doesn't have it's chrome controlled so strictly. Doesn't seem like a crazy request right?
  • 0
    @vomitmachine in that case, no.

    Security wise, Selenium is limited to your machine.

    As long as you don't present extensions which export local data to external connections [without contracts] or provide access to the local machine, sounds sane to me.
  • 1
    Dunno why you guys like windows so much. It enables this manner of fuckery.
  • 0
    @SortOfTested mainly locked into it from Corp. It'd be nice to use Linux so I didn't have to worry about this stuff. But then I'd be struggling for quite a while trying to get used to the interfaces and the tools available on the system.
Add Comment