tag:blogger.com,1999:blog-6156777091769109824.post7027549675146368179..comments2024-02-22T07:21:56.298+02:00Comments on The Adventures of a Space Monkey: Tester 3.0Sami Söderblomhttp://www.blogger.com/profile/06690577772285551526noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-6156777091769109824.post-16636904972598177492012-03-30T11:57:05.186+03:002012-03-30T11:57:05.186+03:00Gerald Weinberg put it better than I ever could:
...Gerald Weinberg put it better than I ever could:<br /><br />http://blog.utest.com/testing-the-limits-with-gerald-weinberg/2012/03/?ls=Newsletter&mc=March_2012Sami Söderblomhttps://www.blogger.com/profile/06690577772285551526noreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-90737784165220659652012-01-31T23:49:41.766+02:002012-01-31T23:49:41.766+02:00@Nixon
Like the great warrior poet Snoop Dogg wou...@Nixon<br /><br />Like the great warrior poet Snoop Dogg would put it: "Fo shizzle!!" That's exactly what I'm afraid of when breeding Tester 2.0s. You pointed out that Tester 3.0 is a combination of Tester 1.0 and Tester 2.0, but I'd like to think 3.0 to be just an update. Tester 2.0 is a tester who has the tools of a developer, but who unfortunately thinks like a developer too. Tester 3.0 has the tools of a developer (not necessary though), but who thinks like a tester, which is actually more important than learning just the technical stuff.<br /><br />Now Nixon, I - among numerous others - have some insight on what you're capable of doing technically and some of it is truly remarkable, but what amazes me the most is that at the same time you're able to think like a true tester. That actually makes you, not Tester 3.0, but Tester 4.0; A kick-ass tester who's more proficient in actual development than developers themselves! :)<br /><br />When the industry starts to wake up, it realizes that it's not the testers that are about to be extinct; It's the developers! They are about to be replaced by Tester 4.0s! ;)Sami Söderblomhttps://www.blogger.com/profile/06690577772285551526noreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-37641426292007675442012-01-31T23:31:28.280+02:002012-01-31T23:31:28.280+02:00The the second part:
"Example case:
When pro...The the second part:<br /><br />"Example case:<br />When project starts everybody just wants to create rather than create and fix. But a project without any testers sounds like a bad idea, so one developer calls himself a tester and off they go! :) Now the project actually has a bunch of developers but one developer was smuggled in wearing testers' clothes. :) So what happens next. Project starts and there are 2-week sprints that end up in a demo. All the developers and the tester 2.0 are working well together and the demo is successful. Everybody is happy. What is the problem then?<br />The potential problem is this: the demo is quite fast and the application CAN look good during the demo. Also the application might be created very well technical-wise but the problem is that the developers are usually much more "clever" than "normal" people. And developer's usually even can't think like a "normal" person. Normal person might do something totally "stupid" that a tester 1.0 noticed when he was testing the application."Sami Söderblomhttps://www.blogger.com/profile/06690577772285551526noreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-24658125986918792302012-01-31T23:30:54.638+02:002012-01-31T23:30:54.638+02:00@Nixon. Somehow I got your comments to my email, b...@Nixon. Somehow I got your comments to my email, but they are not here (too long message error, etc.) Seems that also Blogspot suffers from development-driven thinking... :)<br /><br />But I try to post them here. Here's the first part:<br /><br />"Few words about tester 2.0 and (fr)agile. Always, when I have doubts about anything agile-ish I always get the same unresponsive response from the agile-believers... "you can't say anything against agile! It solves all our problems... capiche?!"<br />Before I say anything else I have to emphasize the fact that I am not saying that being agile is crap and the good old V-model is the way to go. I like the idea of Scrum, for example, BUT I also accept the fact that sometimes the situation is such that you can't use Scrum that easily (those who beg to differ with me... welcome to insurance and banking where you have to deal with z/os mainframes, cobol-stuff that has been written in 70's and environments that are filled with dependencies to 1 000 000 million different services etc etc...).<br /><br />Back to tester 2.0 who is deployed to a (fr)agile project. Ok, this tester knows some java and other cool programming languages like python etc. He/She starts writing awesome test automation that will tackle all the defects that have been found during the sprint. Everything goes fine in the final demo and people are clapping their hands. Then this application is released to production. Some annoyed tester 1.0 wants to see the new application in production and tries a few tester tricks to it... and BANG! The application is broken. Why?<br />I tell you why... it's because "there are no roles in a Scrum-team" and when tester comes to the project he is just a developer who DEVELOPES automated tests by using JUnit, Selenium, Webdriver and maybe even Jmeter or grinder if he is a performance-oriented professional. So, it seems that tester 2.0 is not a tester but a automated test developer - a developer who mostly writes tests. :)<br /><br />In most places the thing is this. Developers want to go somewhere as fast as possible. A tester wants to take photos and see the places, explore and stuff. Like being a tourist (who doesn't just stay beside the hotel pool and get drunk :D). So, what is this tester 2.0... tester 2.0 is a developer in tester's clothing :D - OR it's kinda like developer's "plot" of getting rid of testers :D. Sorry if this sounds a bit sarcastic but this is just a "thought experiment"."Sami Söderblomhttps://www.blogger.com/profile/06690577772285551526noreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-6336266370940828282012-01-30T19:05:30.892+02:002012-01-30T19:05:30.892+02:00"Good god!" -James Brown :)
Niiiice com..."Good god!" -James Brown :)<br /><br />Niiiice comment! You should join in TestausOSY's seminar about agile testing on Thursday (http://testausosy.ttlry.fi/j%C3%A4senseminaari-testausta-ketter%C3%A4sti-helsinki-222012-klo-15). There this subject is taken from very confined and neat environment to gigantic pension insurance environment. If they really have pulled it off by applying pure Scrum and not Scrumbut, this show might be worth listening for. And by "pulling off" I mean taking real responsibility over quality.<br /><br />In the mean time, you should start a blog too and write about Tester 4.0. I think you might be the only one qualified to do so! :)Sami Söderblomhttps://www.blogger.com/profile/06690577772285551526noreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-50179657078352559022012-01-30T17:35:15.362+02:002012-01-30T17:35:15.362+02:00And sorry about the typos...
the previous rants w...And sorry about the typos...<br /><br />the previous rants were written in a very agile mode and the quality was not in the list. :PNiko Rättönoreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-24576602881225249832012-01-30T17:22:46.602+02:002012-01-30T17:22:46.602+02:00And about performance testing... I like the idea t...And about performance testing... I like the idea that performance tests are executed nightly when developing the application. But the fact is that this is often more like performance measurement with some amount of load. Proper performance testing (in my opinion) tries to find the potential bottlenecks in the application or the whole system running the application. This usually means that you have to execute different kinds of scenarios (stress, load, endurance) + have proper monitoring and analysis active while you do it. How do you fit all this in a Scrum project, for example?<br /><br />Oh yeah... if some project is a Scrum project and something is not good then no problem... since the sprints last only two weeks the new release will be out quite soon. This basically means that no one has to think of quality since it will just "happen" at some point. To me this sounds like sloppy busy-work and I hope they never build aeroplanes like this.<br /><br />One thing that also annoys me a bit is the fact that "there should be no quality sprints... because they are not needed!". If some application is done in agile way and it has severe performance bottlenecks when it is deployed to production (and when it actually interacts with some other applications and services that are not so agile) then how this problem is solved in an agile way? Just buy more hardware because it's cheap?<br /><br />---<br /><br />non-related example: band is making a record in the studio<br /><br />case 1: band has a producer who is never completely satisfied with the band's performance and squeezes everything from the band members. It's a hard work but finally the band makes an excellent record.<br /><br />case 2: the same band makes their second record. Now they have more money and freedom and they don't want the annoying producer anymore - they want to produce the new record by themselves! And the result is that the record is sloppy and it sucks<br /><br />case 3: the band accepts the fact the their 2nd record sucked and now they are prepared to work extra hard to make a good 3rd record. They hire the producer back who promises to communicate more with the band and be less of a party pooper. So the project starts again and everybody starts to work with a completely new level of artistic performance. The 3rd record is good again and the band is back on the top!<br /><br />So, what we have learned?<br />tester 1.0 was like the producer, maybe a bit of a stiff spoilsport but completed the work<br />tester 2.0 was the "a bit snooty" group of people who had a bit of a renaissance-spririt<br />tester 3.0 is kinda like tester 1.0 and tester 2.0 combined - a bit more agile than the good ol' tester 1.0 but less of a developer than tester 2.0 (= still thinks like a tester).<br /><br />---<br /><br />Probably I now get the "paskajätkä"-label from all the "tester 2.0"-testers but I still say that I have nothing against Scrum or agile BUT when it becomes like a religion it starts to sound a bit weird. I think that a good tester is supposed to question everything since - isn't that kinda of our core competence?!Niko Rättöhttp://www.linkedin.com/in/nikorattonoreply@blogger.com