Lots more to write about this tool, but I was looking to get a VM up and running with Jira on it, mainly to trial some workflows and customisations.
In the search for installation gotchas, I found this handy github project: jira-vagrant-install.
A guy at work put me on to yoeman which gives your node package manager the ability to quickly deploy a scaffold for building lots of other stuff. Mainly because I want to learn some JS (using CucumberJS at work) but also so I can start building a simple web based application for a hobby of mine.
Some stuff that was installed:
- Sublime Text 2 – an excellent editor
- Java for Mac – I was prompted to install this at some point, can’t remember when
- nodejs – download from http://nodejs.org/download/
- github – so it doesn’t matter where I am, I have access to the code
- yoeman – With node installed, just:
npm install -g yo bower grunt-cli. This installs bower (dependency management) and grunt (a JS task runner) as well
- CucumberJS Easy with node:
npm install -g cucumber for any BDD testing needs
Then added yoeman generators: –
npm install -g generator-webapp followed by
The last step creates a scaffold on which to build your web app. Or whatever it is you’re doing. There are heaps of generators available.
I needed to manually install some grunt components due to permission issues with sudo on
Seems that the bower install done as part of the yo install didn’t quite work (on linux; worked fine on OS X). The previous post is all about fixing that.
Once that’s done, cd into the app directory and
grunt serve to start.
Grunt is pretty nifty. It’ll watch your application directory for any changes and automatically update the site. No need to run anything every time you save a change; grunt takes care of everything for you.
Found this problem while trying to get Bower to work with yeoman on Ubuntu. Turns out it’s the fun corporate proxy here but the problem isn’t insurmountable.
After installing jumping into the application directory and installing Bower with
sudo npm install bower -g
attempting to run
produces a bunch of connection related errors.
Find the port you’re proxying through by
env | grep -i proxy
Now that the port is known, edit .bowerrc in the application directory
and add the following
"proxy" : "http://localhost:<port>",
"https-proxy" : "http://localhost:<port>",
Save the .bowerrc file, close it and re-run the bower install.
If you ever need a readily accessible web dev environment, give cloud9.io a try. I’ve been looking at building a VM that I can use for dev work but this seems to do what I need.
Or, if building your own is what you want to do (practice makes perfect) try this guide at Zynga.
Names? Who needs names?
Three days here so far and I’m having a blast. Not honeymooning (too cynical now) but there’s a lot to like:
- Practical use of git
- New tools like Gradle (whatever happened to Maven?)
- New concepts e.g. contracts testing
- More technical testing than I’ve ever been able to do: automation, BDD, security, API’s
- Many things being implemented and trialed
- Angular and Protractor
- Little “a” agility
- Walls with cards, stories being progressed, get togethers around whiteboards to clarify things, developers, testers, designers and BA’s excited about what they’re doing and enthusiastic about overcoming challenges
In short, much more to learn in an environment I’m more comfortable in (agile) which makes me a happy tester :)
Any PM – or anyone else for that matter – telling you just how awesome waterfall is as a development methodology clearly isn’t paying attention. Experience of the last 50 or 60 years in software development aside, one only needs to look at the paper that supposedly proposed waterfall as a working model to know that the process was a pile of suck from the beginning.
See, a guy by the name of Winston Royce wrote a paper titled “Managing the Development of Large Software Systems“. Go read it. It’s worth it. In the paper he describes exactly why this process is complete balls. Even though he never actually names it as waterfall, it can be clearly seen as such from the diagram.
I find it funny that there has been industry wide adoption of a process that was demonstrably inadequate to the task of building software.
Apparently DSDM Atern is an Agile implementation.
I really have no idea how this could ever be considered aligning with the agile values and supporting principles. Seems more waterfall with smaller iterations rather than agile. Which is fine, just don’t say it’s agile, particularly when you have as a guiding principle “Demonstrate control” that includes the gem “use an appropriate level of formality for tracking and reporting” then I’m pretty sure you’re #notAgile.
Apparently it’s all the rage among big corporates, with 1% of all those surveyed saying . . . Wait, what? One percent? One. Percent. So it’s right up there with the Agile Unified Process and agile modeling. And slightly lower than the category of “Other”.
But it’s nice when they make you laugh on the way out.
A former manager of mine sent this on their last day.
One of the things about facing the imminent end of your current employment (contract’s not being renewed as the role I’m in is effectively redundant) is that you know you’re not going to be there to help out the people you’ve been helping out for the last year. In light of that harsh truth, I started putting together a list of useful testing resources, things to read, even things that aren’t specifically related to testing but have proved useful to me at various points of my career.
The list won’t be useful to everyone and I don’t recommend going and buying every book on it. This is just what I’ve collected over time. If you have any to add please feel free to say so in the comments section.
- The Little Black Book On Test Design – If you’re testing something new, read this if you get stuck for ideas. Even if you’re not read it anyway
- Lessons Learned in Software Testing – Can’t recommend this highly enough. Do not consume all at once though. Bach, Pettichord, Kaner. Suggest you get to know those names
- Tacit and Explicit Knowledge – Not specifically about testing, but very useful all the same
- An Introduction to General Systems Thinking – Gerry Weinberg. If you don’t know who he is, time to learn. Learn to look at (not just software) components as part of a larger whole. Business processes, human interactions, value drivers are all part of a larger system
- The Black Swan: The Impact of the Highly Improbable – This and the follow up Anti-fragile: Things that Gain from Disorder by Nassim Taleb aren’t specifically related to testing but are extremely valuable. The prose can be a bit heavy at times but both are excellent reads
- The Secrets of Consulting – Gerry Weinberg again. Can’t overstate how useful this is; everyone should have a consultative mindset, even if you’re not consulting
- Agile Testing: A Practical Guide for Testers and Agile Teams – Written by Lisa Crispin and Janet Gregory who really know their shit when it comes to the craft of testing and how it works with agile. There’s a follow up work that I haven’t read yet
- Perfect Software and Other Illusions About Testing – Weinberg again. Seeing a pattern?
- The Mythical Man Month – Should be required reading for anyone involved with the building of software, particularly PMs
- Experiences of Software Test Automation – Some pretty interesting case studies that might serve as a warning to others
- The Leprechauns of Software Engineering – Debunks a lot of the myths in our industry, like the cost of defects relative to when they’re found (hint: the ‘fact’ is total bullshit)
- Lean Software Development – An Agile Toolkit – First published in 2003, still relevant. Easy to read and full of practical tips
Stuff that’s related to Agile and Scrum that you might find useful, even though the journey there will be difficult
Technical stuff that I enjoyed reading that wasn’t specifically related to testing
- Introduction to the Command Line
- The Phoenix Project (fiction but a great read)
- Practical Lock Picking
- BackTrack 5 Wireless Penetration testing Beginner’s Guide
- Metasploit: The Penetration Tester’s Guide
- Nmap Cookbook
There’s a bunch of stuff that I’m yet to get around to reading from a few authors who interest me. These are mainly about techniques used to eliminate waste at a number of levels, from software development to pointless management bullshit. The following authors may be of interest to you too:
If you end up leading or managing people please, I beg of you, ensure you know the essentials of the above. It might help make the next generation of
leaders management types a little less dense.
My next trick is to post up a bunch of useful links, though the blogroll is a good place to start. This will include blogs, Twitter accounts, etc. that will give you insight into the craft. Some you may know, others may be unfamiliar.
Sometimes, when reading scientific literature of the psych/social nature, there’s a tendency to think “No shit, really?” in response to the findings. However, the advantage of having a paper published on a subject that confirms what anecdotal evidence has always assumed was correct lends weight to those original, un-researched findings.
Such is the case when I came across this particular paper: Boss Competence and Worker Well-being. Or, as the original ./ lede had it: Your incompetent boss is making you unhappy.
This really helps to explain the enjoyable jobs I’ve had in the past, as well as the not so enjoyable ones. All the roles I’ve occupied that have been enjoyable were in places where I work for, or report to, someone who I consider competent in the job they’re doing. And all the absolutely horrible ones – one last year springs to mind – have all been working for, or reporting to, incompetent cretins who have all the capability of an extremely stupid toaster. Either that or they’re lying scumbags.
Hmmm. That’s probably more about them being a shit person I suppose. Po-tay-to, po-tah-to.
What truly baffles me though is why, when we know all of this, when we understand why bonuses don’t work for knowledge work, that KPIs are seldom relevant to the work being carried out, that theory x type managers are bad for business, that happier employees contribute more to the value of the company than unhappy ones, that collaboration and trust are more effective than command and control . . . When we know all of this, why do we keep trying the same bullshit anti-patterns that continue to fail? Are companies addicted to failure? Or does someone at some point high up in the hierarchy think that if we just keep trying the same old thing then sooner or later we’ll get it right?
Anyway, I found the paper quite interesting. Given that my current contract is coming to an end, I’m hoping that wherever I land next will give me the opportunity to work for someone who knows their shit. Rather than for someone who everyone knows is shit.