Thursday, 21 July 2016

Blueberry Footwraps

Are you a completionist? If so don't bother installing Idle Quest by TopCog onto your Android. It's the kind of game which is a lot like Clicker Heroes. Designed to use up time, doing nothing specific at all. Why not? Well the accomplishments are really easy to get most of. In fact you are going to get all but a handful of the game achievements (and the google play XP points) just by tapping the screen repeatedly and randomly so long as you do it about once a day, 5 minutes, over about 3 months. Sounding difficult yet?

In the clip I show you a hack to get levels in the game much faster, but I am missing a few accomplishments still. One of them is to craft a pair of "Blueberry Footwraps" boots.
I've yet to calculate the total number of craft-able items and quests you can go on along with quest storyline, it's pretty big, but not humongous. But the chances of crafting the specific footwrap boots are pretty low it seems.
I have managed to reach 92'nd on the leaderboard, so I've a way to go still. The boots seem to be just out of reach, I mean the "All your Spatula Needs" accomplishment seemed hard, but the 2 items are craft-able with some amount of ease individually. The trick is to have both items crafted, and then just wait until you get a Spatula city quest as well, which may or may not take terribly long. I think I waited about 10 minutes. If you get the Blueberry Footwraps do share.

Saturday, 11 June 2016

Beyond Eyes : A contemplative game review

Beyond Eyes is not a game, and it is;
it's not a graphic novel, and it is;
it's not a walking simulator it is, a very slow walk. I hope that has saved you some time, but if you are looking for a game that will change you, please join me. By their very nature video games change your world, sometimes they train you in keyboard mashing or in bad physics , always involving explosives. Beyond Eyes is a "game" that belongs in a genre of the kind of games that change your outlook. I call these contemplative games. The story starts with Rae, a young girl, around 8 or 9 by my guess, and blind.


Created by Tiger and Squid, Beyond Eyes took over 2 years of solo work until being adopted by Team17 (of Worms fame.) Published on Xbox , PC and Playstation4 in August 2015 the game is intended to create empathy, and to experiment with the act of exploring one's environment.  It's the exploring of a blind person executed in beautifully rendered watercolours, clean pastels on a muted back cloth of white which lends itself to the empathy experience that any game making it into this genre must have. You play as Rae, but soon I felt I was not playing as the young girl, but rather playing the part of the one thing glaringly missing, the parent. A parent who should be protecting what was once a promising and outgoing child but now damaged and terribly alone in the world. The sense of being alone is very strong in the game and it is personified in the appearance of a stray ginger cat whom Rae names Nani. Some people have drawn lots of conclusions from Nani's name or behaviour or meaning, but to me she is just a gentle but aloof cat. Nani appears in Raes' life just at the point when she is suddenly alone, and attempts to draw your character out of their shell by doing what cats do. The cat doubles as a kind of symbol, but Nani introduces you to the idea that a blind persons world is built using sound and smells. Which is why Nani smells like and behaves like a stray ginger cat. Wandering off and luring you through the garden gate into the exploring part of this game. The exploring mechanics introduces and uses an element that creator Sherida Halatoe capitalizes upon to emphasise the sensation of blindness. Your world as a blind person (and Raes' broken social life) is very small, and as you explore you must rebuild these 2 and at the same time overcome obstacles. You will get lost as you explore and search for Nani, and even temporarily stuck because you have to feel your way about because Raes' vision is built using sound. Sound which misleads her sometimes, resulting in some surprises and fun and leading to frustrations too. The game is played at a slow walking pace, I mean blind people can run, but the way the world fades slowly back to white after she passes, and the slow exploring speed really make you feel blind and trapped. You cannot move fast enough to rebuild the fading surroundings, and at one point it rains which literally washes away the beautiful watercolour rendered world. I started to feel a sense of urgency at this point and got totally hooked.




But even before this all, the game fell down for me. Just a few minutes into the game that will keep you busy for about 2 hours (more if you explore fully) I decided to see if closing my eyes would work. The sound-scape is really good, with chapters or stages are introduced with some brilliant piano work to compliment the mood. But the sound has holes, little things like a fountain that does not sound like a fountain if you approach it from the wrong side. Different walking surfaces are accurately rendered in the sound-scape with grass crunching giving way to the hard sound of stone and a crunch of gravel. But then the woodpecker at the bottom of the yard sounds out the same toc toc toc with no natural variations. Subtle environmental sound hardness changes and depth or echoes is another thing I expected to hear too, but to be fair I've not experienced in all but high budget games anyway. But these are made up for by the huge variety of sounds, smells and locations you must explore and the fact that Rae does not find a gun or a sword. Which would have come in handy in some of the threatening situations she finds herself in. Which is why I liked this game. I hope I've not given anything away, and helped you to decide if it's your kind of game. Creator Sherida Halatoe has added a few other elements to the game and story, but I'll leave you to find them.

Final scoring 

(How I score: http://softcircuitry.blogspot.com/2015/12/new-genre-contemplative-computer-games.html)
Artwork  5/5
SoundTrack  4/5
Plot 4/5
Playability 5/5
Value 3/5

Friday, 10 June 2016

failed mumble mumble : Rescue a partial gotoMeeting GTM recording

So, quick disclaimer, this post is a raw braindump. Nothing to see here (besides the fact that it ends in failure).
Today I was given a corrupted gotomeeting .G2M file to try and repair. I stupidly announced that I have repaired broken GTM recordings in the past. True and not true, 2 facts here:
Fact#1 GTM is a screen recorder, and as such is optimized for meetings and records at 10fps, in RAW by default to get good performance. Fact#2, the raw recording mode can be overriden in settings, and it's suggested you do so, it takes a bit more CPU poke, but is fine on most computers.

What has changed is that the codec Goto uses is a custom part, built to get performance, and like in all video tools you also need a decodec - luckily GTM provide the conversion tool in the UI.
If the UI fails... which it will do for me shortly, (I'm debugging while writing this as the conversion does take a few minutes) you have to try convert it manually.
OK, so now the digging starts.

https://glenndcitrix.wordpress.com/2010/12/17/the-ultimate-gotomeeting-recording-guide/
https://glenndcitrix.wordpress.com/2010/04/06/convert-recordings/
https://judisohn.com/2010/12/11/converting-gotomeeting-recording-to-something-you-can-actually-use/
While that goes on we are trying the following: use ffmpeg to convert the video to an MP4
Turns out ffmpeg seems to find the code needed for the g2m file and any container and starts decoding, but it's going to take hours and hours and the decoded file will probably be 30fps with higher data rate so that means around 10 x size increase...
But as we continue regardless, lets see what the support gurus can tell us at GotoMeeting.com forums.

Final result, nope, conversion failed

Friday, 26 February 2016

Powershell and open-auth / braindump

another /dump.

will take some shape as a go along. Basic problem I want to solve is using powershell to pass authentication through when calling a rest service, but in reality the "passthru" part of it all is a bit of a mystery to me. And feels like it might well be impossible to do in a really secure fashion.

http://foxdeploy.com/2015/11/02/using-powershell-and-oauth/

Wednesday, 24 February 2016

I'm Hangry, so I decided to give up strangling people for Lent


Everyone is a tester

I stopped being a software developer about 5 years ago now. Well that's not entirely true, I have always been a tester. In fact everyone tests, but not everyone puts "tester" in their job-title; so if this is you, stick with me a sec.

So lent runs from February 10 to March 24th, and generally people will give up something over that time. It's normally a Christian kind of thing, but in general it's a mindfulness exercise that's good for any religious conviction. Or even if that's not your thing. My thing is not killing people who #$%*@ me off on a daily basis. Most people will be giving up chocolate, they may have tried a Dryathalon, or a "Stoptober", but generally cutting any distraction out of your life helps you. Getting hacked off when someone disappoints you is not healthy, and that is true for software testing as a role.

The Lone Tester

Last night I attended a DOJO Masterclass called "The Lone Tester" by the lead test engineer at Bitly, who has worked solo for much of her tester career. Jess Ingrassellino talks about skills and fresh learnings for anyone who works solo, as a contractor, or who is keen to start learning how to start a career in test or, to shift themselves from Manual into Automated testing. That sounds like a lot, but Jess has done it all in just 4 years, so it's all very well related; her delivery is centred around being the only tester in your organisation or division and having to make your own way. If you are the Lone Tester, Jess gives some tips on how to see yourself as not being alone in reality, since everyone is in fact thinking about quality, but not necessarily an expert. Which is what you are really there for with your tester hat on.
It's not in my opinion a talk with any great revelations in terms of content or process wisdom to any seasoned tester, but she does drop in some pointers for managing your time and workload better and these might inspire the old guard too. To see the talk recording, sign up in the Dojo at Ministry of Test.

Back to the Lean coffee.

I snagged the following topics (actual POSTIT notes visible in micro above with the donkey.) As always my summaries are my words and how I understood them. Everyone in the room hears these same words but takes them on slightly differently. It's called language, and in my case hard-arse.
Performance Testing: Should I test little and often or full-on and infrequently?
  • A few ideas about why the question is the wrong question came out here. long-running stress tests are more like regression tests in many ways and thus carry the same high costs. They also find completely different classes of defect. Knowing this in advance will clue you up on where to go in your strategy
  • You do need both, but understand why first and when first
  • Quick can never be replaced by deep testing, mainly because it can deliver test verdicts quickly and supports your CI process more directly
  • Deep testing delivers more accurate metrics than a quick performance test. But if you apply the same metrics gathering and performance gathering history analysis to your quick testing runs, you will get more value more often and sooner
  • Long running test are best run infrequently in your cycle, and only when you change something that could cause the problems associated with stress failures: Namely; changing the version of any 3-rd party component, major algorithm/architecture change or anything infrastructural that the architects identify as risky
For anyone with time to google around, maybe look for some tips at a recent #TESTBASH by Scott Barber.

I've been asked to test a spreadsheet WTF???
This one came from Alan I think it was, like all simple questions it raised good responses:
  • Sometimes you get asked to test something that you don't really want to test. This severely impacts your reaction and emotions can very quickly prevent you being effective
  • Analyse the business risks, work out the value to business. Then move
  • Gather some stats on how often the "spreadsheet" causes losses, present your findings in easy to consume form like a graph, so that people can understand the risks. Exposing actual size of any risk is your speciality as a tester

How to cope with Context switching and Time management

This was my topic, but more a question, since it's something I'm rubbish at. I was inspired by the tips that Jess Ingassellino shared in her "Lone Tester" masterclass.
  • Time your activities to fit in with natural times of the day, like lunch for people-time, mornings for firefighting, and afternoons for actual core work
  • Plan actual test "session-based testing" for set times
  • sprint, and capture stories
  • Use various todo listing tools

How do I assess my value as a tester?

A topic which Jess co-incidentally also touched on, funny how this kept coming up. Honest guv.
  • toot your horn
  • drive process, management expect you to make process changes that impact quality
  • protect revenue. It's not your job to sell the product. Not your job to fix bugs, nor even to find them. All you have to do is ensure customers don't find them.. well at least not the ones that make them select a different vendors' product
As a tester, you must always be asking questions. First, foremost and often. It's called left-shifting.

In closing; one of the topics not covered (there were a good few) was using "Selenium from absolute scratch". I think a few people are interested in getting a n00bs guide.

Tuesday, 16 February 2016

Test automation sticky-note (sic)

A quick note to make sure I do not loose a little idea I got while browsing recent presentation a STARWEST. The specific presentation I have in mind is here:
http://www.stickyminds.com/interview/five-patterns-test-automation-starwest-2015-interview-matt-griscom?page=0%2C0

Matt Griscom links you to his website and a download for the .NET Framework based tool he created. I believe it warrants a try, because although it glosses over some problem-domain specific areas for me, it seems to take account of a lot of the automation framework gotchas I currently face.
His blog is http://metaautomation.blogspot.co.uk/ and the download is hosted here http://metaautomation.net/ .

Basically I face a problem where my current automation system is not flexible and powerful enough, so requires fragile customization. Stable over the short term, your test code breaks every time the framework revision changes. Which has to happen as you integrate common or shared test-code down into a pattern in the toolstack or into a shared library. All this work needs to be designed and to be planned to reduce maintenance load. Matt seems to recognize many of the related problems I face there, although maybe not solving them, the act of identifying them helps us a lot. Basically he takes the approach "measure everything". Make it easy to mine all data and suddenly you can do comparative and performance testing as well as predictive triage.

So, just a quick note before I forget all about this angle.

Thursday, 28 January 2016

Why testing fails (the short of it)

I was asked to try take the speaking place of a colleague, and talk on this for CEWT #2. Cambridge Exploratory Workshops in test.
I was initially just hoping to get onto the reserve list, then someone dropped out after I wrote this. So here we go.
Not the kind of thing you want to admit having first-hand experience in when you work for a company falling into the top 100 of almost every desirable list. I'll share my 2 reasons on the topic "Why testing fails".
It's not possible any-more to book a place at CEWT #2, basically because the workshop is limited in size. But if you want to find out more, do get along to a lean coffee morning, just google for the (real) Cambridge meetup "software testing club lean coffee"
To be on 28th February at DisplayLink Cambridge. Contact JamesThomas @qahiccupps .

Rushed Implementations 

“Look before you leap” comes to mind.
  • Features without right hygiene loose in the quality department
  • Feature does not solve customer a problem and becomes harder to test
  • Test not involved early enough

Test Planning 

“Fail to plan, and plan to fail", going around in vicious circles comes to mind.
  • Close-down cycle with no resources planned or budgeted for it
  • Planning impacted by rushed implementation
  • Planning is easier than you think (with good data to support it)