Friday, 17 February 2017

Harness Your Ruthless Efficiency as MVP in testing and development

TLDR; Ruthlessly look at your process and incrementally improve your efficiency. Take the same attitude when testing and developing and harness MVP as often as you can.




In this post I’m going to describe focus and how you can apply that in your work, not just for testing but for software development in general with examples.

On the morning of 17th Feb 2017, I created an Instagram video on ‘focus’ and it was about… how ruthlessly efficient we can be if we focus.

The Monty Python Test Tactics

And it was partly inspired by Monty Python with their Spanish Inquisition sketch. They have three main weapons, four or five, but it’s surprise, fear, and ruthless efficiency.

Wednesday, 15 February 2017

Should I test at the GUI Level or the API Level?

TLDR; Where to test? Can you isolate the functionality? If so, test the isolation most heavily. Then look to see what integrates, and how it integrates. Then test the integration as heavily as the ‘how’ requires.




Question: Is there a rule of thumb when deciding to test at the GUI level or API level? Are any rules to help decide when to test at one level over the other?
Answer: I don’t think I use a simple rule of thumb. But I will try and explore some of the thought processes I use to make the decision.

When I am trying to decide whether to test at the GUI or the API I have to figure out:
  • what am I trying to test?
  • can I isolate the functionality I’m testing to a specific ‘level’?

Tuesday, 31 January 2017

How to test a text adventure game - some notes on Testing RestMud

TLDR; RestMud has JUnit Unit @Test coverage, functional integration testing, REST API testing with Jsoup and Gson, Bots for multi-user and model based testing, Postman and GUI based exploratory testing.




I’m getting RestMud ready for some workshops later in the year and this means:
  • making sure a player can complete the maps I have created
    • I’m OK with some bugs (because they are for testers), but I need them to complete because they are games
  • making sure they can handle enough players
    • I imagine that we will have a max of 20 or so people playing at a time
  • making sure I don’t break existing games
    • with last minute engine changes
    • with new game maps
    • with new game commands and script commands
As most of you reading this will realise - that means as well as developing it, I need to test it.

RestMud Text Adventure Game for Testers Walkthrough

I have created a walkthrough for the RestMud game I released last year.

Why? Because I have had a few people email me asking for tips.

Warning:
  • This is a full walkthrough
  • Start to finish, every command
  • It will not improve your technical skills
  • If you don’t play the game with dev tools on then it might not be obvious why you use some of these commands
  • there is a full map at the end of the walkthrough, I put it at the back because you should only use it in an emergency
I recommend:
  • use this sparingly
  • go as far as you can, and only if you get stuck to you use it
  • search for your location id if you are stuck to jump to the correct hint
  • make your own map
You can find the walkthrough and a hand drawn map on the RestMud game page.

PS. The walkthrough was generated by an automated script that played the game to check that it completes.

Thursday, 12 January 2017

What do you do? As a Tester, when you are asked for ROI calculation

TLDR; push back, ask questions, and if all else fails - plan it as a manageable set of tasks

At the Test Automation Guild I was asked a question about how we calculate ROI for Test Automation. And its a hard question for me to answer in 30 seconds when I don’t know enough about the situation the person asking the question finds themselves in.

Because testers are often asked by managers for information that the manager should really be dealing with and which does not seem to add value to the process and which we are concerned trivializes or views the process from the wrong perspective.

I know this is a difficult position for testers.

And I know testers are asked to do this.

I empathize. I’ve been there.

And I want you to be able to take this less seriously - consider that your only warning for what you are about to receive.

So I will attempt to provide tactics to help with the situation.

Monday, 2 January 2017

Hack the JavaScript Evil Tester Sloganizer to Generate Random New Year's Resolutions



I wrote a blog post for the new year:
And in there I noted that if you go off to the Evil Tester Sloganizer
and type this code

for(var x=0;x<100;x++){
console.log("-" + process_sentence(sentences[30]));}

Then you’ll get a bunch of New Year’s Resolutions printed out to the console:

Lessons Learned from Arnold Schwarzenegger Applied to Software Testing

Lessons Learned from Arnold Schwarzenegger Applied to Software Testing

TLDR; Start emulating people, use your job to learn, keep training,  identify other people's strategies, experiment to see what works for you, make your own tools, harness your uniqueness.



Everyone that is successful in their discipline and is prepared to tell their story, we can probably learn lessons from. Particularly if they are someone who’s really driven toward certain goals.

With Arnold Schwarzenegger, you’ve got the benefit that he has had multiple careers or multiple things that he has done throughout his life, and each one of them he has had to work for and practise hard to achieve.

I read Arnold Schwarzenegger Autobiography “Total Recall” and I made some notes, and I’m going to turn these into applied notes for learning how to improve our testing.