TesterHQ - The Evil Tester Blog Aggregator

Feb 15, 2017 - 4 minute read - Automating Evil Tester

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?

Jan 31, 2017 - 9 minute read - Evil Tester Technical Testing

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.

Jan 31, 2017 - 1 minute read - Evil Tester Technical Testing

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:

Jan 12, 2017 - 8 minute read - Evil Tester Techniques

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.

Jan 3, 2017 - 4 minute read - Linkedin

Recognise and Improve Your Personal Test Process

I believe that everyone has a unique and personal test process. Also, when we accept this, we can grow our testing skills further and faster than if we pursue the traditional path of learning a common body of knowledge. Learn your traditions We do have a tradition of common terms and information from our ‘craft’ - techniques, tactics, and strategies. For testing we have named techniques: “Boundary Value Analysis”, “Equivalence Partition Analysis”.

Jan 2, 2017 - 2 minute read - Evil Tester slogans

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

I wrote a blog post for the new year: http://blog.eviltester.com/2016/12/happy-testing-new-year-for-2017.html 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 e.g. : -I will try to pursue this risk further -I resolve to scrutinize requirements -I resolve to scrutinize ambiguity -I think I might just exploit this defect further -I will follow this risk further -I think I might just provide alternative alternatives -I will try to question more requirements -I will learn to test effectively -I resolved to scrutinize ambiguity -I think I might just test the lifeblood out of this system -I resolved to test the life out of this system etc.

Jan 2, 2017 - 13 minute read - Evil Tester Productivity

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.

Dec 31, 2016 - 3 minute read - Evil Tester slogans

Happy Testing New Year (for 2017)

Happy Testing New Year (for 2017) TLDR; Happy New Year - And all the best for 2017 - resolve to make changes every day - don’t rely on a single point in the year. I try to avoid New Year’s Resolutions. I think we need to resolve to make changes every day. But… The Evil Tester Sloganizer has a resolution template visit http://eviltester.com/apps/sloganizer.html Open the Browser Dev Console Type the JavaScript Below for instant resolutions: for(var x=0;x<100;x++){ console.

Dec 30, 2016 - 2 minute read - Evil Tester Technical Testing

How to configure Postman Native Client App to use an external proxy

TLDR; to configure Postman native client app to use a proxy: use Settings to configure specific or global proxy or start it with command line parameter -proxy-server=host:port This post updated 20170911 to describe the new Settings options in Postman to configure the Proxy. postman.exe -proxy-server=localhost:8888 One of things I like about Postman Chrome App is that, because it uses Chrome, it is really easy to feed through a debug proxy like Fiddler, or Zap, etc.

Dec 16, 2016 - 7 minute read - Evil Tester Techniques

Software Testing Definitions and Models - How and Why to Create your own Definition

TLDR; I avoided creating a definition of software testing for a long time because I thought it would constrain me. Instead I built a model of what I did. Eventually I generalised it to a ‘definition’ - “Testing is building and comparing models of a system to the system.” [Digital image courtesy of the Getty’s Open Content Program.] From 29/11/2016 to 6/12/2016, every weekday, I used Instagram as a platform for creating a ‘daily thought’ on the topic of “Definition of Software Testing”.