QA on remote control

A few years ago I had the great pleasure and challenge to be remotely employed as a QA engineer in a startup company, and it has its fair share of challenges.
Try to imagine:
The center of activity is miles away, you are short of information, mostly you don't get updated online when a change in requirements is made.You can't give your input in design reviews and at times you will be updated last on a change that in your opinion doesn't make any sense. In fact, you will probably have no say in most of the design issues. As a QA Engineer, I can tell you that pressing the "Off button" on your criticism is not as simple as changing a channel. You are updated last about changes in deadline and priority. At times you can spend an hour testing a module, while the developers are working on changing it.Sometimes you receive a short message to deliver X result in Y time, change your testing priorities or switch to testing another module ASAP, without even knowing what stood…

Why I joined

After reading our President's article about why he joined, I was so inspired that I have decided to continue this tradition!
Today, I'm joining as a QA Automation engineer. applies a high accent to “The human material”. They are very picky about who joins the team, and I can understand why. Dedication, professionalism, and productiveness are highly important for a fast-growing, cutting-edge technological company.
How I met Oren Rubin
For as far as I can remember, I always tried to be active in QA and Automation forums. It is a good opportunity to acquire knowledge for myself and to advise those who need help. As a highly experienced professional Oren always stood out in these forums with his helpful tips and advice, it was fascinating to see how much knowledge he has. Fast enough we started having long discussions and became friends. We finally met in person at a conference and he seemed to be one of the nicest and talented guys I had ever met. Immedi…

Teach more - lecture less

Recently I had the great pleasure of teaching and lecturing to QA students. It was an amazing chance to challenge myself, learn about myself and get a positive sense of meaningful activity.
The First few minutes I have to admit that teaching is harder that it seems. It has it’s fair share of challenges that I will try to cover in this article, and it all starts with the first minute you enter the classroom. “There is no second chance to make a first impression” applies here, because as you enter the room, the first few minutes are critical for the student’s perception of you. Imagine, you enter a room with 20-30 strangers, they are staring at you and examining you. They try to understand, do they like you? Can they connect with you? Are you clear and accessible to them? At this point it is best to just take a deep breath, smile and start talking to break the ice.
The great challenge of capturing their attention Keeping 20 young students focused on you and attentive to your idea for 6 hours …

"A bug in comprehension" - reviews as a part of the testing process

A bug in comprehension
reviews as a part of the testing process
"It's not a bug, it's a bug in comprehension..." A perfectly amusing phrase from the head of the development team in an organization I worked in during a discussion with the project manager. But, what it's all about? The organizational culture varies from company to company, as are the types of tests required by the QA team. There are quite a few companies in which the tester is required to examine the quality of the characterization documents (Specs, FD's and User stories) prior to transferring it to development. In the organizations in which I have worked, no Change Request, User Story, is being transferred to development without the approval of the tester assigned to the project, who is a key figure in the "life cycle" of the product. Lack of coordination and Inadequate characteristics, means that the final product may be different from the poet's intention, delay in time, features tha…

Role-playing - not a dirty word

Role-playing - not a dirty word
"Testing Personas" or "User Personas" are a common tool in the "Testing world". Each character represents a certain percentage of the product's users. Using this method, we are able to create possible realistic usage scenarios, and "edge scenarios", Considering the habits and Uniqueness of the characters we will adopt. Testing Personas are used by Testers and product managers while writing specification documents/User stories.

About a month ago I had the honor to participate in an interesting panel of Testers. During the meeting a conversation occurred between two team leaders. It caught my full attention. They talked about a testing method called "Testing Personas". I found myself totally fascinated by the conversation, because it was one of the things that makes me love this profession so much. The privilege to use my imagination, to question, to explore, to think of "the unexpected" that i…