These are chat archives for bluefin-octopusdeploy/chrome-extension

18th
May 2016
David Roberts
@davidroberts63
May 18 2016 03:04
Published
I'm going to start looking at browser testing services. I imagine we could stand up VM with Selenium on it but I'd like to look at some of the online service offerings to see what they provide report wise as well. A quick google turned up a couple: https://www.browserstack.com/ and https://crossbrowsertesting.com/
David Roberts
@davidroberts63
May 18 2016 03:10
Both of those have a free option for open source or just a free tier. I've heard browserstack in the news before I think, wasn't good news but that was last year I think. The idea would be to at least get screenshots of each feature being used. But how to trigger it properly. That's where I think some Azure template + DSC would come into play to setup at least two (for starters) different Octopus Deploy versions. Once the VM is running have it kick off the browser testing pointed at the VMs. Just what I'm thinking at the moment. Open to any other ideas you may have.
Ultimately what I'd like to see is when you or anyone else send a PR we could somehow choose if we wanted it to go through auto browser testing and then put the results in the PR comments. Along with a few screenshots perhaps. I've done something minor like that for the C# group where I'm at. It works okay. But nothing as involved as this may be.
David Roberts
@davidroberts63
May 18 2016 03:33

Wohoo! I got the room back. So yeah. I transferred the repo and it kept the OctoPygmy name, so I said, well I'll delete 'chrome-extension' repository. Didn't even think about it removing the gitter room as well. Then I renamed the bluefin-octopusdeploy/OctoPygmy to 'chrome-extension' and bam the room is back!

On another note you now have commit access Matt, congrats! Now...don't make me take it away. ;-)

Matt Richardson
@matt-richardson
May 18 2016 06:21
Awesome - thanks for publishing that.
Matt Richardson
@matt-richardson
May 18 2016 06:29
In gonna still do PRs for all changes - be good to be on the same page.
David Roberts
@davidroberts63
May 18 2016 12:19
Agreed. I'll do the same except for version bumping after merging.
Matt Richardson
@matt-richardson
May 18 2016 13:07
I think we're gonna have to keep an eye on 3.4...
there's a bunch of changes that look like they'll break BlueFin
they've changed the variables page, so the 'view resultant variables' link isn't showing up
David Roberts
@davidroberts63
May 18 2016 13:11
Yeah that last blog post started raising my eye brows.
That and that little change in 3.14 for the dashboard. And then the template library is changing soon to.
Matt Richardson
@matt-richardson
May 18 2016 13:13
how are they changing the template library?
David Roberts
@davidroberts63
May 18 2016 13:17
Just the community website. Some API changes that will affect the part of bluefin that allows for quickly importing them into your template library.
Matt Richardson
@matt-richardson
May 18 2016 13:20
Its funny, as they rely on bluefin, but dont take it into account when changing the product
David Roberts
@davidroberts63
May 18 2016 13:22
Huh didn't think about that. They have mentioned several times that they tell customers that a particular feature is in bluefin , just use it.
David Roberts
@davidroberts63
May 18 2016 13:27
But they did reach out to me concerning the template library website change. So some are keeping it in mind.
Matt Richardson
@matt-richardson
May 18 2016 13:28
thats good to hear
David Roberts
@davidroberts63
May 18 2016 13:42
I have a way in the metrics part that gets the version of Octopus Deploy it's operating on. We could use the same code to get the Octopus version number upon startup and pass that onto the observe method for each feature. Then it could store it and adjust as necessary.
Matt Richardson
@matt-richardson
May 18 2016 13:52
that sounds like user agent detection...