Eliminating Assumptions by Day[9]

Reading Time: 1 minute

Using my twitter reading list (Tester Tower Live) I stumble upon this great four part video lecture on Eliminating Assumptions from Sean Day[9], professional StarCraft player, shoutcaster, and stand-up comedian. Link to video lecture was categorized in my company as against code and ethics rules of my company! Reporting this as a exception to isit department they agreed that this link should be unblocked. In this lecture Day[9], based on his gaming (or should I say testing) experience, lists nine assumptions that work against the player (tester) in problem solving of video games challenges. What shook my mind in this lecture are examples form video games, puzzles and riddles that Day[9] used in explaining why those assumptions are wrong.
Enjoy in lecture!

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

One tester and 30+ developers at Code At Six

Reading Time: 1 minute

Yesterday I attended Code At Six meetup. As it is written at their site, this is developers meetup where developers socialize and give short hand on lectures. They discuss hipe technologies for web and mobile development. Code At Six grown from legendary Ruby At Six meetup where Ruby language (and related technologies) was main topic. Goal of Code At Six is to gather all web developers. There were 30 developers and me, one tester. I gave hands on lecture on Grinder, load testing framework based on Java and Jython technologies. Merlin Rebrovic hands on was about hacking Git history.





Using Grinder TCPProxy, I recorded http data while loading Code At Six home page (github grinderShowCase project). Audience reaction was pretty good, and of course main request was to try to crash Code At Six homepage. Of course we only created a load of two concurrent users, and presented grinder test reports.
After the hands on lectures, we formed smaller groups to discuss various topics about web development.
I am very proud that I was given a privilege to talk in front a such smart audience.



Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Zagreb STC Meetup #3

Reading Time: 2 minutes

 Zagreb testers community held Meetup #3. For now we are at our schedule to have those gatherings every two months and we are very happy about that fact.
First, we distributed free copies of Testing Planet that we received from Software Testing Club. We are very grateful for that gesture!



First testing problem (was it accidental or intentionally?) was the room projector problem. Projector was at the ceiling of our room and we did not have its remote. On projected image we could not see Windows XP taskbar. We agreed that we have to discover the proper laptop resolution for the projector. First we blindly tried several laptop resolutions with no success. Than one tester suggested that we should use resolution with ratio similar to ratio of projector canvas. At that was solution of our problem!

Where is the taskbar?



Topic of meeting was performance testing. Our fellow testers from Asseco gave presentation about testing in their organisation, and they finished it with live presentation of performance test of their product using Jmeter. 
They tailored testing process from Microsoft Solution Framework. Before that, there was no dedicated testing team in their organisation. Developers were responsible for testing. They are continously working on testing process, but their experience for now is that they now have much less problems with their products in live production.

Congratulations to projector problem resolver! (first from the left)





Mission of performance test was to discover reference system configuration for their application. Basic input is that response for the application most critical service must be under 300ms. They changed their application from java process and in house code to J2EE application. Tomcat is application server, Oracle is database and Linux is target os. Client interface are web services. Other testers commented that this architecture is very similar to architecture of products in their organisations.
First observation of performance test was that product on new J2EE architecture had slower response times than the stand alone java process application. Their experience with Tomcat is that commercial solutions like IBM Websphere are much better.





They created various scenarios in Jmeter. Important note is that they cooperated with developers in order to create Java client code for Jmeter scenarios! Testers in their organisation do not program.
During the live demo, we discussed (along with pizza that was kindly sponsored by Asseco fellow testers) several testers topics:

  • communication/cooperation with developers in our organisations
  • using Junit framework for system testing
  • bug reporting (Bugzilla, Mantis)
  • test reporting
  • testing estimation
  • sql injection
  • mobile testing (automated vs. manual)
In the end I conclude that Zagreb STC MeetUp #3 was very productive and interesting gathering. If you would like to join for the next meeting, please subscribe to our Google group Zagreb STC, drop an introduction post about yourself, or propose something of your interest for the next meeting.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather