Development and test environments - on demand at the press of a button (That actually work!)

“Works on my machine!”

“Fails most epicly on my test system!”

“Oh, wait… it works on CI but fails in Test env 3.”

Sound familiar?

These sorts of conversations are thankfully a thing of the past.

Wait, hold on - are you still having these sorts of conversations?

That's probably because you are working somewhere where the development, test, production & CI servers are being created by people, painfully, once.

Alexander the Great cutting through the Gordian knot of a particularly gnarly micro-service deployment.

You set up your laptop, you pray to the god of operating system patches and upgrades and hope that nothing ever changes (ever). You're gonna be the last person in the team to take that new Mac OS upgrade - let the rest of the team run through those mine fields first.

And the test systems? Last time you asked for a new one of those your programme manager ended up on new & stronger heart meds.

Luckily, there are tools that can help.

Gitpod, for example, allows you to create a development environment every time you log on, or in fact whenever you want.

Gitpod has a number of useful features that together can make your lives easier. They are:

It provides an easy to use development IDE (it's a web version of VS Code, one of the most popular IDEs in the world).
A cloud based workspace with a command line terminal (Yes, Bash), and even a linux desktop if you need one.
Configure your whole development/test environment with standard Docker & Docker Compose commands to be built and deployed anytime.
Smooth integration with Github, GitLab or BitBucket. (Or you could even self host it)

Now that's a lot to digest. What it means in practice is that your team can create one template of how to set up your app.

You can then store that template in the code repository, along with the app and test code.

And when you need to fix a bug, code review a pull request or test the app you can just build the app and the whole supporting environment in the cloud and on demand (it takes seconds).

Tools like Gitpod have the potential to save teams a massive amount of time lost to misconfiguration, confusion and the laborious work of creating and keeping environments in sync. You don’t realise how much time is lost in the setup and untangling of the Gordian knot that constitutes the average development environment - until it disappears.

Comments

Betting in Testing

“I’ve completed my testing of this feature, and I think it's ready to ship” “Are you willing to bet on that?” No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten. Instead, I recommend you to ask yourself that question next time you believe you are finished. Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach. Testing is gambling with your time to find information about the app. Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app

Test Engineers, counsel for... all of the above!

Sometimes people discuss test engineers and QA as if they were a sort of police force, patrolling the streets of code looking for offences and offenders. While I can see the parallels, the investigation, checking the veracity of claims and a belief that we are making things safer. The simile soon falls down. But testers are not on the other side of the problem, we work alongside core developers, we often write code and follow all the same procedures (pull requests, planning, requirements analysis etc) they do. We also have the same goals, the delivery of working software that fulfills the team’s/company's goals and avoids harm. "A few good men" a great courtroom drama, all about finding the truth. Software quality, whatever that means for you and your company is helped by Test Engineers. Test Engineers approach the problem from another vantage point. We are the lawyers (& their investigators) in the court-room, sifting the evidence, questioning the facts and viewing t

XSS and Open Redirect on Telegraph.co.uk Authentication pages

I recently found a couple of security issues with the Telegraph.co.uk website. The site contained an Open redirect as well as an XSS vulnerability. These issues were in the authentication section of the website, https://auth.telegraph.co.uk/ . The flaws could provide an easy means to phish customer details and passwords from unsuspecting users. I informed the telegraph's technical management, as part of a responsible disclosure process. The telegraph management forwarded the issue report and thanked me the same day. (12th May 2014) The fix went live between the 11th and 14th of July, 2 months after the issue was reported. The details: The code served via auth.telegraph.co.uk appeared to have 2 vulnerabilities, an open redirect and a reflected Cross Site Scripting (XSS) vulnerability. Both types of vulnerabilty are in the OWASP Top 10 and can be used to manipulate and phish users of a website. As well has potentially hijack a user's session. Compromised URLs, that exp

investigating software

Search This Blog