How regularly do you release code to live? Is there a cadence or is it based on something hard like deadlines?
GlasgowTestingGroup retweeted
How to Write a Good Bug Report buff.ly/1LMibNO by @testlodge
Go live dates, my 30th, Star Wars and last minute Christmas shopping. This week is going to be full on!
GlasgowTestingGroup retweeted
I don't tweet a lot here, but I still read! You can find me to be more interactive @GlasgowTesting
There's so many "ship it" go to production memes out there, I struggled yesterday to decide which to use.
GlasgowTestingGroup retweeted
Replying to @MaddogMikeB
“@MaddogMikeB: New digs but some familiar friends @octopusdeploy https://teapaw.org/t.co/EK3TNzVntO”
GlasgowTestingGroup retweeted
In Agile, feedback is generated by testing - not testers. Never surrender @DawnMHaynes keynote. #LetsTest
GlasgowTestingGroup retweeted
The most powerful benefit of using tools wisely is not in what the tools *free* the tester to do, but in what they ENABLE the tester to do.
GlasgowTestingGroup retweeted
Tonight we're at @XEDOSoftware for @LeanAgileGLA – Agile transformation tour, Q&A, #leancoffee, beer & pizza.
ow.ly/2bwecd
Small and regular releases are where it's at. No user chooses overblown perfection over good enough and here now. teapaw.org/ianlclark/status/66310…
@ianlclark @TestingCircus @KeithKlain down and dirty.... Haha
Me after a hard day testing... teapaw.org/GlasgowTesting/status/…
Good luck to @GlasgowCSS hosting their first meet up tonight @XEDOSoftware
GlasgowTestingGroup retweeted
Uh... "Marks and Spencer website suspended after shocked customers get access to other shoppers' personal details": mirror.co.uk/news/uk-news/ma…
How long does it take a story from inception to production? @chrisvmcd












