Six years ago, I was still a student at the University of Geneva, I decided to host myself a blog in order to be able to share my ideas and views with other people. It was also a convenient way for me to be able to remember some random ideas I would have read or learnt.  

I quickly realized that nobody was reading my blog :)! So I changed the switched the main language to English instead of French, this helped quite a bit to increase the number of visitors. I remember that I was really proud when around 30 people per day would visit my blog.

With time my focus and the focus of this blog sharpened on web design and web development (mostly Macromedia/Adobe Flash). Being actively focused drive this blog high in page rank and I had a decent amount of daily visitors (for a personal blog, that said).

Since my professional focus shifted from web design and development to software engineering and testing, the focus on this blog has been lost. Frankly, I am writing about too much random stuff to be able to capture someone attention.

In computer science there is a known paradigm, called divide and conquer, that state that to fix a complex problem a solution is to divide it in simpler problems. Starting today I will apply this paradigm to my online presence.

I am a software tester by profession and I am passionate about software testing knowledge and theories. I have opened a blog dedicated to software testing: testingpatterns.info where I will be blogging about software testing whenever I have something to write. Join me there if you are interested by software testing :).

I work at Microsoft, on Lync server and I own the testing for Response Group Service and Call Park Service. I have opened a while ago a blog on MSDN dedicated to this topic. Join me there if you are interested by Lync server response group service and call park service :).

What about metah.ch / ahmetgyger.com blog? Well I am going to use this blog only for more personal related blogging, giving my point of view on technologies and sharing some information about my life in the US.

Thanks for reading!
A.

 

A few weeks ago I had the chance to win at a tombola organized at SASQAG (Seattle Area Software Quality Assurance Group) an entry ticket for the PNSQC (Pacific Northwest Software Quality Conference).

With this ticket in my pocket, we decided (with my wife and kids) to have a trip to Portland, OR. I haven’t had time to visit Portland too much but I understood from my wife that there is no state taxes in Oregon :).

The conferences lasted two days (+ workshops that I did not attend) and was really interesting I must say.

Day 1:

The keynote was given by Julian Harty about the future of quality. The main idea is that software testing needs to focus much more on the users than on the functionality, testing needs to take into account more parameters than just a functionality.  

Following the keynote I went to a talk from Wayne Roseberry about software reliability. The reliability, he claims, can be achieved by good metrics and measure, development of tools to help improving the investigation in case of issue.  After this talk focused in process improvement I jumped to the testing track of the conference.

The test talk was an introduction to customer focused test design by Alan Page. The main takeaway of this talk, as already mentioned during the keynote, is that the focus in testing needs to shift to the customers. The testers should focus on the main scenarios from the customers and thus help increase the perception of quality. This could be done by increasing testers’ awareness on security, privacy, usability, reliability, performance, interoperability and globalization. Another tool to increase the coverage of customers’ scenarios is live testing or test in production.

This was actually the topic of the next talk I attended, presented by Keith Stobie. He went through a lot of technics to control and monitor test in production, from A/B testing to fault injection.

I then went to a talk by Jim Sartain about inspiring, enabling and driving quality improvement. As the title reveal, he focused on how to give the test teams the environment and the resources they need to make their job. Some technics he promoted were peer review, scrum and unit testing.

Finally, I went to a presentation about application security for QA – Pain or Gain, the emphasis was on modifying the perception about testing and giving some tips on how to make security testing.

Day 2:

Next morning was rainy and I was really tired because my 9 month old son teeth were piercing so I did not have much sleep. At least the first talk was really entertaining so all that did not really matter. The keynote topic was Value Sync, presented by Robert Sabourin. His presentation went through the logic of understanding and synchronizing the value between stakeholders and testers.

After the keynote, it was time for Michael Bolton talk. I was quite looking forward for this one actually. Topic was about standards and deviations. I felt a bit uncomfortable as the talk was really oriented against the drafts proposed for ISO 29119 (software testing). I mostly agree with his points but it did not deserve two hours of talk in my opinion.   

I then attended a presentation under the soft skills track: the ladder of unmanaged conflict by Jean Richardson. The presentation was about how to deal with conflict in your organization.

After that I went to a presentation about playback testing by Vijaya Upadya, a very interesting presentation about using application logs to reproduce bugs (in short the tests parameters are extracted from the logs and allows to reproduce issue found on customers side or during live production testing).

It was time for a talk by Marlena Compton about understanding the psyche of the software tester. I was a really entertaining talk but I did not really agree with the content. I think the presentation missed a very important point on the interaction between developers, testers and project managers. She analyzed the conflict from the tester point of view, without taking into accounts the context of these conflicts.

To finish the conference, I decided to listen to Bj Rollison about parameterized random test generation. This was an excellent talk, I really liked how he presented an intelligent framework to have a great test coverage with realistic random data.

Overall, these two days were really refreshing and introduced a lot of new ideas in my perception of software testing. It sounds like we are in the middle of a profound change in software testing and the great news is that the users trends to the top priority in the testers mind.

If you are interested about the topics presented at PNSQC, they share all the content of previous events. You can head to the past conferences part of their site and you should soon be able to read / watch the presentations yourself!

 

Last Sunday, my family and I landed in Seattle airport after more than ten hours traveling.  We then settled in a temporary housing in Kirkland, with a breathtaking view on Washington Lake. So far, we are all excited and happy to be here!

On Monday morning, I was at Microsoft for the New Employee Orientation (employee that relocate have to attend the NEO). It was a pretty good way to adjust my jet lag and understand what I needed to do in order to get my administrative work done. Main blocker for us is still the social security number. In the US without a SSN you cannot get credit. Without credit you cannot get a phone, a car or a house. So our temporary situation is going to last for a few more weeks, not bad considering the current view on the LakeJ.

Being at Microsoft mothership is quite impressive, around 60’000 employees dispatched in numerous building all around the area. This is a radical change from my experience in Zurich (Switzerland) where we were “only” 30 employees.  When I learned that the Dev Center in Zurich was about to close, I decided to stay in the same group (Lync) while extending my responsibilities. This means that I am now testing Lync Response Group and Xmpp Gateway.

The Seattle area is very promising, close to mountains, forest and the Pacific Ocean. I am really looking forward to discovering this area.

 

 

There have been quite a lot going on in my life the past months, following the timeline of the events:
Most importantly, my wife gave birth to a healthy and beautiful son, named Baptiste. He is already quite tall and is wearing 3 month cloth after only 1 month of life :).
Few weeks before, I learned that my office in Zurich was shutting down and that my job was relocated in Redmond / Washington.
My wife and I planned to move to Redmond in a few years but with the unexpected closure of the Zurich development center we decided to take a shortcut in our plan and to accept the relocation offer. The decision was not too hard to take and I must say that I am super existed to be working in the mothership of Microsoft. Although Zurich is a beautiful city that offers incredible life quality I was never able to get myself to the Swiss German culture, probably because I am so Swiss Frenchy :).
The most annoying part of this move will be to get so far away of my family and friends but as I learned from previous experience friendship is not a link that can be broken by long distance.
The current plan is to have my family and me moving to Redmond in end of June 2011. So until then I will enjoy having team meeting in the middle of the night with my new team :).

 

Since I moved to Zurich, two years ago, I sadly did not have the time to see most of my friends I have in Geneva. This post will hopefully explain you what I am doing in Zurich as an Engineer in Test at Microsoft. I know that even the people who know me well do not really understand what my role is and what testing is about.  Defining testing is not quite easy so let me start by quoting Wikipedia’s definition of software testing:

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs.

To resume, I bring information about quality and objective view of the software I work on (the next generation of Office Communication ServerResponse Group Service). I own the testing of some feature of RGS for this feature I should always be able to answer the question: ‘Can we ship it?’.
To answer this question I have two main approaches:

  1. Develop automated test that will run scenario at a code level, this test being automated I can make sure that no regression would be added these feature and related area.
  2. Do some manual testing on complex scenarios representing the customers most important scenarios.

 

Finding ‘bugs’ effort is only the half of my work. The other half is dedicated at understanding the defects and drive to their resolution. To do so I am helped by developers (fixing the bug) and project managers (to give clear vision on how a feature should work in every details).

As the goal of this post is to be as clear as possible in won’t go further in my explanation :-)

I hope you know understand better what software testing is how I spent my time at work.

Jan 022009
 

I wish you all the best for 2009!!!

Good health, happiness and success : )

Ahmet

 

as3 video tutorial: updating air applicationIt tooks me more than six month to create a fresh new tutorial, but finally here it is!
This tutorial shows how to automatically update an AIR application when a more recent AIR file is on Internet.

I hope it is easy to follow and clear :)

You can watch it here.

You can see all my AS3 video tutorial here.

This tutorial use the côdeazur Class available here.

Ahmet