mail site 5 reasons
Home | Program | Speakers | Key-notes | Registration | Supporting Org. | Sponsors
Tutorials: 26-27 July


Presentation: 28-29 July



Mieke Gevers

Performance & load in action

  • Instructing to use a testing methodology for Performance testing
  • Setting up testable objectives for performance on web and non web environments
  • Using performance work load models and fine-tune them
  • Highlights and pitfalls about performance testing
  • Overview of the current performance testing tools
  • Root cause analysis and results evaluation
  • Hands-on to put the theory in practice.
  • Attendees should be familiar with 3-tier environments, incl. Web server and Internet/Intranet technologies.

Pablo Garcia Munos

Effective testing in Agile life cycles

Many organizations introduce Agile methods thinking that all problems will be solved. Many times the product quality is seriously injured and it will take a long time to get back. This tutorial helps you to pick the best things about Agile and what things to keep. This tutorial helps you to pick the best things about Agile and what things to keep.
  • Introduction to Agile
  • Direct impact to the test effort using Agile.
  • Different ways of organizing test.
  • How to communicate.
  • Metrics and control
  • Keep your ground, show results.
  • Metrics and control
  • Keep your ground, show results.
  • Summary

Lior Fridman

Redefining QA Roles in an Agile environment

Agile methodologies has revolutionized the development cycle. Short release cycles has forced development to adopt new and better engineering practices to improve quality on the development side. QA is also affected by such a transformation, in an agile environment QA and R&D departments can no longer afford to work in semi-isolation. In order to achieve high quality products, QA and R&D must join force and share the effort and responsibility, while collaborating on the processes and tools. This Workshop will help show team leaders and QA engineers how testing groups fit into an agile development process. It will show several organizations structures commonly used in companies undergoing an agile transformation
  • Introduction to TDD and developer tests
  • Maintaining Quality in a short release cycle
  • The tester role in a Self Managed agile team
  • Structuring the QA as part of the development cycle
  • Leveraging development tools in the QA environment
  • Summary

Alon Linetzki
Best Testing

Practical Test Process Improvement Using the TPI Model

This workshop is designed for QA/Test Managers who would like to learn how to apply the TPI (test process improvement) model in their own organization. The TPI model is a well known method published in 1999 by Tim Koomen & Martin Pol which identifies 20 key areas of the testing process that need to be considered for potential improvement. It offers a step-by-step, structured approach to improvement of the testing process so that small, gradual changes are made which have a positive and measurable impact and are within budgetary and resource constraints. This workshop involves some presentations and lots of interactive discussion and practical exercises. Actual examples from the software industry are also utilized to bring the model to life and make the information relevant.

Upon successful completion of this workshop participants will be able to:
  • Understand the major principles of the TPI Model for test process improvement
  • Make a basic assessment of their own testing processes
  • Understand how to apply the TPI model.
TPI is a registered trademark of Soqgeti.


Alon Linetzki

Test Management under Crisis

In today's market demands, we are facing bigger testing challenges. The demand for increasing ROI, decreasing costs and getting a better product quality - is stronger than ever from upper management. We have no time for making mistakes – we must do things right the first time. We must move from a detection mode into a prevention mode, manage our testing processes better and make them stronger than ever, and manage our testing risks on a more professional level, in order to be able to add value to the business. We will have to face a few major challenges:
  • Improving testing processes and the quality maturity of our products
  • Manage risks and respond quickly to market needs (preventive and corrective actions)
  • Manage our professional team better – building an efficient and effective testing team that can handle the workload with advanced methods and tools
We shall have to do all of that in the most pragmatic/practical way we can. My presentation will focus in raising the awareness to the challenges, and discussing a few tips of how to deal with them in the short and long terms.

Avi Amon

Customer Facing: The wisdom behind testing

Getting the final approval from your customers is probably the most important milestone in any project lifecycle. Now days, dealing with a turbulent financial environment were customers are demanding more quality for less money, it is becoming an even greater challenge. As systems get more complex, the people who are facing the customer in relation to testing need to expand their technical and quality knowledge. This presentation is dealing with the extra skills that are needed from the test engineers. Customer oriented approach, the ability to adjust to different cultures and working environments, working under tight and predefined time frame and the diplomacy skills needed, are put to test at an even larger scale. Organizational mind set change, regarding the roll of test managers and the importance of testing, is a must in order to meet those challenges. So, if you wish to take an hour break from the technical bits and bytes and would like to embark on a fascinating journey around the world with stories from customers at the most unlikely places and Get some tips regarding the challenges and the way to face it, you are most welcome to join this presentation.

Andy Redwood

Sourcing – alternative sourcing strategies for testing services

I would also like to do a specific presentation on 'Sourcing Strategies' - the four stages of delivering and offshore solution and how to evaluate and select options. Objective Work through the 4 stages to evaluate and decide upon the correct sourcing option; Provide detailed Costing and ROI metrics from a real case study. Agenda - Examine the global sourcing market; Work through the 4 stages to deliver a sourcing strategy and select a partner
  • Sourcing Strategy - alignment to corporate strategy, setting the baseline, risk assessment, service bundling, financial assessment and CBA, governance, principles
  • Evaluation of Candidates - identification of providers, development criteria, organisational fit, selection process, partnerships, shared services
  • Contract Criteria - Value proposition, Governance model, performance criteria, terms and conditions, financial criteria, change tolerances, due diligence
  • Sourcing Management - Transitional change, Assessments, Management of resources, performance, measurement, change and innovation
Look at the top 6 alternative solutions and examine to pros and cons Examine the potential costs and savings for the most popular 2 alternative solutions. References – A large retail and investment bank looking at sourcing alternatives from multiple global suppliers. What people will learn – The 4 stages to undertake to make the best selection for an organisation; What alternatives they may wish to consider?,Who are the suppliers and where are they?,What are the major costs?,What is the ROI and timescales to return this investment?,Who needs to be involved? Who should attend? Heads of Testing Service,Test Managers,Development Managers, Governance Managers,Sourcing and Resource Managers,Offshore Suppliers

Dr. Avi Ofer

Improving Product Quality by 100% - a Case Study

The first step to improve the quality of any product is to know what the current quality is. The method to do so will be first shown, briefly. Then, a real case study will be presented in which the quality of legacy features in a product was first really poor: 43% at pre-alpha. Although it was later improved up to goals, the process was painful and expensive. The quality status was detected and analyzed using the above mentioned method, root causes were identified, and remedies were offered and implemented. Main remedies were improvement of documentation in crucial points, and strong focus on backward compatibility for the successive product, as well as improvement in development and testing methods. In the successive product, where the above remedies were implemented, the quality was monitored again according to same method. This time, the quality toward pre-alpha was 87%: an improvement of 100% (!) comparing to the previous 43%. In the lecture, this entire process will be presented, with emphasis on discussion with the audience.

Boaz Armoza

What does it takes to build a top testing team?

I have been a manager of software testing teams and departments for many years. Over the last year, I have had an eye-opener of what it takes to build a top testing team and in my presentation; I will share that revelation with you. I will take you on a short journey, not teaching you new concepts, but taking the things that you already know or have been exposed to and helping you to make sense of them, to put them in order, to build a top and vital testing team. I will cover building pride in your organization, the characteristics it takes to be a tester and changing emphasis in the way you and your team view their roles.

Dakar Shalom

From saving to making money to the organization by producing good testware

Lately we are all facing the consequences of the world wide economic crises; we are all being request to perform a long list of cut downs and steps for decreasing the expenses. "But of curse never on the expense of quality". I guess you are all thinking "I am not a magician" I can not guarantee that cutting personal and reducing time and effort will still preserve my quality level". Join me for an hour of good advice on how to not only save money to your organization by discovering major defects but to earn money for your organization with the testware you are producing.

Debi Zylbermann

Test Engineers - Adding Value in Tough Economic Times

The Global economy has been suffering tough times for almost a year. Many companies have been downsizing, and letting good employees go. In the area of software development, often the first teams to suffer layoffs are the testing teams. Senior management have a hard time measuring the ROI (return on investment) of the testing teams, whereas they believe they can measure the ROI of the development teams. Lack of quality is usually blamed on the test teams, who didn't catch the defects, rather than on the teams that "developed" the defects in the first place. In this talk, we will examine some practices and tactics that can be used by test teams to increase their value to the organization, thus hopefully enabling senior management to realize that these are just the people the company cannot do without.

Ester Zabar

Employing Autistic people in software testing – experience sharing

Social innovation
Social innovation refers to new strategies, concepts, ideas and organizations that meet social needs of all kinds - from working conditions and education to community development and health - and that extend and strengthen civil society.
Autistic people
People diagnosed within the Autism Spectrum might have high cognitive abilities but low level of social skills. In addition, they have special advantages: eye for details, finding inconstancy, very precise, attention & patience in repetitive tasks.
Special advantage in S/W testing
These abilities might provide special advantages in S/W testing tasks – specifically for regression tests
Experience sharing
The project is base on a Danish company named SPECIALISTERNE which already gained 5 years of experience in employment of 50 people. Similar activity was started in Israel about a year ago. The presentation will share experience in candidates' selection & training process, assigning them to projects, & coaching the people on the job site. It will also report on obstacles and limitations as well as success stories.

Joel Montvelisky

Providing the correct information for your specific Product, Process & Company

We all generate reports but many times they go un-read or completely un-noticed by our stakeholders, other times they are reviewed but then we are asked to provide more or even different information. All these are signs that the reports we are generating are not the right ones. Correct reports are not only a function of the way you present the information, they are the result of a complex process that starts with the analysis of the needs of all the stakeholders, gathering the accurate and timely data from your project sources, and then presenting this information the correct format, at the right time, and to the proper audience. The presentation is based on real-world experience and case studies the author has taken part of or supervised over the last couple of years. During this session we will cover:
  • Ways on how to assess the required reports for your project.
  • Methodologies that help to collect the data that is already been inserted into your system. and that you can leverage in order to gain visibility into the process and product.
  • Different mechanisms and ways to present the information in order to cover all the spectrum of stakeholders that need your timely information in order to execute their tasks correctly.

Michael Stahl

Right and Wrong when Writing Test Cases

While a lot of material exists regarding Test Case design – from Techniques to Configuration Coverage and more, very little attention is paid to the actual style used when writing test cases. It is not uncommon to find: Actions that are presented as Expected Results… Things that don't need to be checked are spelled out in detail… Different language is used to say the same thing… As a result, many test cases are hard to read, just because they are written badly – not because they are wrong. This presentation will point out this issue, show examples, and propose idea regarding writing styles. The writing style is tightly related to other test case aspects – such as detailed VS simple test cases etc., and this is covered as well.
  • Why Writing Skills are relevant to Testers?
  • Consistent language
  • Expected Result – language style; when to add it
  • Parameters, permutations and built-in randomness
  • Simple tests VS complicated tests
  • Thread testing VS Stand-alone tests
  • How much can I trust my Oracle?
  • Added coverage as a side-effect – Good or Bad?
  • The test-case writing flow (when and how to review test cases)
  • Test Case organization
  • Is this important at all?

Mieke Gevers

Can we justify the choice "open source tools versus commercial tools"?

During recent times, analysts are predicting a economic downturn which will have an impact on many industries and companies. Quality Assurance will not be immune from these effects. It is more important than ever to make sure that our testing is as effective and efficient as possible in real life. In testing, we are constantly challenged to increase coverage and quality in our products & testing efforts, adding more automation, managing our professionals more efficient and this in a time where resources are being and do provide a world of choice in which individuals and organizations can pursue their goals based on what uniquely drives them. Whether you are a developer or a tester who wants to learn new skills, connect with the community, help to build a business-application, dealing with complex interoperability or you want to setup a quality management platform including proprietary and new open source testing tools, a lot of decisions need to be made. Needless to say that decisions should be based on data and much of the data we collect today in testing finds itself on the table of business analysts and upper management, tasked with making decisions. Can enterprises take advantage of open source software? Is it an option for organisations to make the transition towards open source software? Which choices need to be made and why? These are just a few questions which Mieke, based on her experience with testing tools will try to answer during her talk.

Ram Yonish

Overview of testing tools for times of crisis

During the last 6 months I have found my self trying to answer the same question again and again: "can you recommend of a low price/freeware testing tool". As days passing by and the economic storm seem to grow larger and larger, I thought it will be a good service to try and answer this question. I’m not considering my self as an automation expert (far from that), but in my presentation I have tried to collect relevant testing tools/ vendors and to present an overview of all kind of tools based on my experience and more important on others. Those of you that will decide to participate in my presentation will receive basic information that should be very helpful as the first step of selecting the right testing tool. I will present tools for test management, test automation and special freeware tools for accessibility and compatibility testing. Most important – as always in such presentations the most valuable and extended knowledge is buried in each one and one of the participants them self. I guarantee I will use this knowledge so we can all benefit from this meeting the most.

Shmuel Knishinsky

Successful Near Shore Testing – Part II

After that I presented the previous part of our near shore testing project on March 2008, we have the opportunity to look at the next stage of the project and learn from it. In part I was focused on defining the major requirements, learning and analyzing the market offerings, defining the critical criteria for decisions making, operative preparations, project initiation, and the actual life by data from the real life of the project. After more than 1.5 years, in part II I will focus on the “routine” of the next stage of such projects – How do we prevent or minimize the impact of changes in order to keep and enable the flexibility and modularity. Infrastructure growth, existing and new people, new projects to cover, etc., are part of this “routine”, so how do we succeed and what should be done to able to organization to move forward?

Shmuel Gershon

Law & Order: Bugs that can cost you your business

Legal obligations penetrate all areas of our life and work, including software development and software trade. Bugs that have legal implications cost money, reputation and time in the best scenario; in the worst cases, they can take a company out of business completely or even send people to jail... But while we strive to educate our development team in all areas pertaining to software by giving them tools to understand the functions and uses of software, the legal point-of-view is often neglected -- by testers and programmers as one, and sometimes their managers too. Shmuel is an engineer and not a lawyer, and his lecture aims to increase in testers the awareness about liability, privacy, intellectual property and more; with examples from real life cases and useful tools.

  • Legal aspects of Software Development and Test
  • Examples from software applications and from court-cases
  • Suggestion of tools and aids to establish a legal-conscious process

Yaron Tsubery

ATP – The Factors behind Success

The dream of the field engineer and the project manager is to deliver the required project to their customer and gain the customer’s satisfaction. Many ways can lead to a successful ATP which most of them speak about the technical aspects. I would like to take you to a tour that will expose you to the fact that the ATP is not only a technical driven subject, in most of the cases it is required a mix of robust process, strong management control, diplomatic skills and technical aspects. You will be able to view how in Comverse we handled a successful ATP stories, what are the process stages that we decided to take care in the product life-cycle and how we lead together with the project manager and the customer to a successful Acceptance Test. I’ll show how your test organization will gain additional credit points, in-front of the project manager and the customer. The practice is focused on complex systems that part of them delivered to telecommunication companies under restricted rules and stiff exit criteria elements – which made this more complex to handle among with tense delivery timelines.