Showing posts from December, 2016

Testing in Agile: roles merge but don't disappear

With current Agile approach there's a little bit of anxiety, especially among Software Testers, about "Roles merge" idea. Let me comfort you - roles do merge, but they do not disappear. Lets have a look at this in a little bit more details - first, let's discuss why roles do and should merge in Agile projects, then why they will never disappear.

Why roles merge Agile team is typically is a cross-functional team having shared goal (well, at least in theory ^_^ ). For instance, this goal may be paint a room, prepare a party, write the best ever software or anything else. This means that there will be situation where one needs to step in and help others do they job.

Test needs model - when test and test automation meets

So, you decide that your project needs test automation, because manual testing is too long or too costly to address your needs. How would you approach that? In essence, there’re two opposite approaches to test automation. Let’s call them “test first” and “automate first” Test first approach  In this realm, you have luxury of having somebody actually designing a test case for you, so you can automate it. Quite often, this is a place where many “test automation” engineers would like to be. These means they are actually being developers, because they have requirements (which is a test case) and a product (which is aautomated test case). They also have a clear goal (automate that) and they are not responsible for quality of the product under test. In contranst, they are responsible only for quality of their automated tests. All things considered, this approach is actually quite sustainable from quality control perspective. Provided automated tests are accurate, stable (which is test aut…

Say Hello

Hey everybody. My name is Alexander Pushkarev (feel free to call me Alex). I've been working in IT roughly since 2006, and most my work experience is about testing, automated testing and test automation.

Even though I do enjoy programming, I find task of testing that thing was programmed well more challenging and exciting. Besides, I would rather do little thing good, that big thing bad, if you know what I mean.

Currently I mostly using Java for my work, but I also worked with .Net framework (and have warm feelings about it) and also I adore languages like Python or Kotlin, so chances are I will post most examples in any of these languages or platforms.

A couple of words about my personality. Let me put it straight - I am not nice, I don't believe that team spirit is our best aim and I am not going to tell people what they want to hear (in a meaning I can tell people something they certainly don't want to hear).

My ultimate goal is to achieve effective and feasible quality…