The Conference presentation days are:
For Conference Registration
First Conference Day Presentations
Psychology behind Test Management
Mr. Yaron Tsubery
· Be able to understand additional aspects of our profession,
· Be able to identify the keys for successful communication with your
colleagues through well known psychology theory and practice,
· Be able to raise productivity in your daily work.
Testing managers, team leaders and senior test engineers that would like to improve their communications skills.
Method of Learning
· Presentation, case study, examples, class discussions.
· The audience will learn theory, and participate in answering questions and sharing their experience.
· Excel tools that were used will be presented.
· Identifying the communication problems and expectations that are raised by colleagues
· Dealing with expectations:
o Map your colleagues and their expectations
· Interpersonal conversation model:
o Present a psychology theory developed by Eric Berne
o Understanding the connection between theory and daily practice
o How to break the trust?
o Good and Bad experiences
o Preventive, corrective and maintenance steps
o Review of method and process
o Present advice for the road
Multidisciplinary Test Engineer – Is That a Future Necessity?
Ms. Dakar Shalom
consulting and training services
What is the best way to discover as many defects as possible from the client's business point of view?
These questions are being asked often by testing and development managers who are looking for methods to improve the testing coverage and reduce escaping defects.
I will present a case study in which good common test design techniques were used with limited success, and resulted poor quality and customer dissatisfaction. As a result, the test design techniques were changed to business process testing technique which improved the quality and customer satisfaction significantly.
• The logic behind business process testing
• What is business process testing and how it is integrated in the project and testing life cycle
• Key elements for design & analyze business process tests
• Execution highlights
• considerations for managing and control of the testing effort using BP
• Case study example project ( statistics results will be presented)
I will analyze the increasing need and best ways for implementing BP methodology in testing project life cycle
Regression Test Methodology
Mr. Motti Avrahami
In today world when software new releases are occurring very often the QA manger standing in a dilemma in the regression test phasing.
In my presentation I would like to present the DSM Table this is a software development matrix, which defined connection between different Software modules
By using the DSM table the QA manger can easily identify the modules that need to be tested.
He also can perform accurate time effort to perform the regression testing.
Test Planning Efficacy:
Using the Right Amount of the Right Planning to Produce the Right Results
Ms. Hedy Rashba
This presentation describes a case study about how the creative use of test planning, analysis and design methodologies helped an overwhelmed System Integration and Test group successfully meet its objectives.
The techniques presented and implemented are textbook methodologies .
At the end of the presentation, you will be familiar with successful test planning methodologies that were implemented by an NDS System I&T group to make an impossibly large testing project more attainable.
Surviving “crunch time” :
Dealing with constant change, high work load and communication issues
Ms. Katy Podolner-Rotman
Have you ever had a crunch period at work? Sure you did!
Did you manage to survive it ? Obviously so, or you wouldn’t be here to tell …
This presentation aims at those who want not only to survive but to perform at their and their teams’ best during crunch times, while retaining most of their wit and sense –as well as dealing with high expectations, ongoing change, and ..people, of course!
Root Cause Analysis: Dealing with Problems, Not With Symptoms
Mr. Alon Linetzki
In many cases, managers pick solutions to problems without sufficient analysis. This results in implementing a cover-up of the symptom rather than a solution to the ‘real problem underneath’. When this is done, the problem will surface again in one disguise or another, and we may mishandle it, just as we mishandled it initially. Alon Linetzki describes a simple process you can use to identify the underlying cause of the problem and create an appropriate solution. Alon demonstrates how he enhanced the classic root cause analysis method to create an approach to finding problems underneath. The presentation includes a method for identification of symptoms and problems, the connection between them, the strength and direction of that connection and presents some tips on how to think in the process of achieving those. Alon illustrates this method with data from his experience in projects.
· A simple, robust method for determining underlying problems
· Differentiating symptoms and problems
· Solve problems rather than cover symptoms
Beta Testing - The Secrets of Success
Mr. Lonny Baskin
I will be presenting a case study of a successful internal beta testing program, which will include what went right as well as what went wrong. I will describe the lessons learned and improvements made. The attendees will be able to use the information to initiate and manage similar projects, and avoid the pitfalls we encountered. In addition , I will demo a tool we developed to make bug data collection fast and simple. The tool allows users to report on defects that normally would go unreported.
Application security testing in the distributed world
The SOA concept is becoming popular and thus, more and more applications are designed as a composition of services. This creates agility, promote reuse but brings many new challenges in the security arena.
In this talk we will discuss those challenges and focus on testing procedures that should be a part of any distributed composite application test plan.
Distributed composite applications demands attention in application security design implementation and testing.
We will cover all the main issues a tester should cover when building a test plan for these kinds of applications
Advanced Testing- The gateway to Software Quality
Ms. Mieke Gevers
An analytic and septic view on where we came from, standing now regarding testing in general, the testing methodologies, testing technique, testing tools and automation or non-automation.
The presentation starts with a brief overview of the evolution of testing and its different aspects concerning testing methodologies, techniques and tools – a view on where we come from, where we are standing now and focusing, elaborating on where we are going to.
• Does the actual know-how and tools give us the means to support the current and future need of testing?
• Trying to look at what is really needed for QA managers/ QA testers / Development in order to support our testing/QA efforts. For Example “Are models, patterns and tools (open and non-open source) providing us a gateway to the 21st century?” Open discussion is welcome.
• Are the current testing approaches/techniques/methodologies really successful and can we continue on this path or are changes needed in order to support future testing needs.
• Awareness of the pro & contra's of current testing methodologies, techniques & tools.
• The Impact of introducing "Advanced Testing" into an organisation.
• Awareness of the pro & contra's of current testing techniques.
• What are CBD & CBT?
• The today’s usage of Models and patterns. Is this effective?
Mr. Shlomi Amar
Did you ever imagine how software testing will look like in the year of 2015?
In what way does software engineering differs from other mature conservative engineering expertise?
While thinking about the two questions, do you think there will be any gap closing in the sense that experts will reach recognition?
How will it affect the future testing ?
Battle for the Mouse: The Art of ATP
Dr. Avi Ofer
Getting the formal acceptance of your customer, inshore and offshore, is probably the most important milestone in the life cycle of a software project. This is NOT a task for amateurs: one needs specific skills and experience in various domains, including deep knowledge of software life cycle and quality, customer-oriented approach, broad cultural horizon for offshore missions, and high flexibility toward the changing conditions during this process, which is commonly (and somewhat wrongly) known as performing ATP (Acceptance Test Plan). More than a technical challenge, performing successful ATP is a complicated art.
If you want to taste some of this art, accompanied with slides, funny anecdotes and hopefully useful tips from software quality travels around the globe, and if you want to know what the Battle for the Mouse is and how to win it, you are welcome to this presentation
Developing Test Cases from UML diagrams
Mr. Ofer Prat
Model-driven development practices give us testers access to the flows and structures of the tested product design.
Learning to "read" UML diagrams, and extract test cases from them can give us extra power when testing the actual product.
In this presentation, we will discuss a few of the UML diagrams and learn how to extract test cases from them.
Second Conference Day Presentations
Testing and Configuration Management Serve Each Other
Ms. Anne Mette Jonassen Hass
Configuration management is a support process that can add value to all the processes in development and testing. For companies striving to get to CMMI level 2, configuration management is a must.
It is however a process many people love to hate – mostly because it seems cumbersome and unnecessary. This presentation will describe the basic principles of configuration management and take the mystery away from it. It will go on to describe how testers can benefit from configuration management, and how they can add value to others in the organization by placing their artifacts under proper configuration management
Where We Are? Status and Progress Indicators
Dr. Avi Ofer
It is a general truth that if you do not know where we are, it means that we are practically lost.
To avoid this situation during project life cycle and testing, we should have a reliable, understandable, visually clear, concise indicator. An essential issue is the right definition of the data on which the indicator is based.
A good reference for the status is the project set of test cases. If well defined, they cover the entire project scope. A careful and accepted weighting of test cases and project components is to be done, to avoid mechanical count of test cases disregarding the differences in their importance.
Once weighted and counted, the status of test cases may indicate at one glance the percentage of integration (comparing to plans), readiness, test progress and maturity of the project. When recording these results along project timeline, progress and tendencies also become clear.
In this lecture, the entire process and actual resulting indicators will be presented and discussed
Catching those Requirements Bugs Easily
Ms. Debi Zylbermann
Debi'Z Consulting Ltd.
There are many preachers for finding bugs as early as possible. We all know that finding and fixing a bug in requirements is much cheaper than finding it and fixing it during testing, or (perish the thought) after deployment to the customer.
The question is how to find those bugs in requirements?
This interactive session will give you some simple tools to distinguish between "problem space" and "solution space", and to easily find requirements bugs before they proliferate throughout the code.
Assessing the Test Process Effectiveness
Ms. Michal Tal
Testing and QA consultant
How can we ensure the effectiveness of the Testing Process?
How can we be sure we are testing the right thing, investing our resources in the most efficient way to make sure we will detect most of the defects?
Measurements can help us collect measurable data about the testing process, asses its effectiveness and improve it.
Presenting several metrics with examples and analyze them:
1. Defects detection distribution
2. Defect Distribution XX vs. client
3. Defects Root Cause Analysis
Development and Testing Process metrics:
1. Development and Testing Activities – plan vs. actual
2. Percentage of cancelled defects
3. Cancel Defects Root Cause Analysis
Bug Hunt Testing
Mr. Amos Uzan
Testing is a positive and creative effort of destruction. It takes imagination, persistence and a strong sense of mission to systematically locate the weaknesses in a complex system and to demonstrate its failures.
When we use scripted testing we lose a big part of the creativeness, motivation and the joy of creation.
Bug Hunt sessions are a fun and competitive chase of faults, going for the big prize. This ""Happening"" atmosphere increases motivation and effectiveness, and fosters creativity.
We work in pairs, combining people from different backgrounds - QC, Development, marketing, support, software consultants and managers. Working in pairs is enriching and stimulating.
We work in a happening atmosphere, recognize the owners and give them very nice prizes.
The guidance we give to the participants is:
Play with the products – try to destroy this thing if you can. Find the defects that you know are there. If you come across something that even remotely looks like a defect, ring the bell and write up a defect report. I want to share with you our experience with bug hunt sessions, the unexpected challenges, how to manage the session, how to get a happening atmosphere, how to setup large scale environments for participants around the world, the benefit that we gain when development is involved in system testing, and other things.
..And You Didn’t Report It?! -Roadblocks to Bug Reports
Mr. Michael Stahl
• A list of 10 behaviors in situations every tester encounters, that cause us to miss, ignore or not report bugs – even when we know they are there.
• Cases will be accompanied by an example or a story from real life
What will the attendees learn?
• The problems presented are general – they affect many testers in many projects. Attendees will be able to recognize and identify with the described situations as something they have experienced.
• The presentation will provide testers with the tools to recognize and deal with the described problems.
• Knowing that the problems are general in nature (""it's not only me"") will help testers to avoid these problems, or defend their position when challenged
Designing a Performance test
Mr. Omri Lapidot
Performance tests are needed when we believe that the amount of factors in the application will affect its functionality.
In the presentation I will discuss the proper way of designing performance tests in order for them to properly reflect anticipated application usage, follow the steps from design to execution and advise which pitfalls to avoid.
• Performance Testing Phases
• Designing a Usage Model
• Tests and environments creation
• Load and tune
• The Politics of Performance Tests
• Use Case presentation
SQA on-line dashboard
Mr. Shiri Gal
SQA departments are ultimately decision making enablers for management when it comes to projects maturity and delivery readiness.
It is our job to deliver real-time, accurate and reliable information to the projects we are engaged with so our managers would know where we are and what next actions should be taken in order to succeed in delivering the product on time, on budget and with adequate qualit .
We have came into a decision to develop our own on-line dashboard after years of exprience and stuggles with dozens of projects.
This dashboard goal is to provide on-line measurements to each and every project and department when it comes to defects data, project progress, testing status, maturity levels and other quality related data. By combining our defect management data, test management data and additional back office information we are succeeding to become real decision enablers.
This discussion will present you with our development, walkthrough the different aspects of quality related data and help you to develop your own dashboard tomorrow!
Scrum & QA - Friends or foe?
Mr. Danny Kovatch (Danko)
Scrum is an agile framework to organize teams and get work done more productively with higher quality. It provides what the customer wants at the time of delivery (improving customer satisfaction) while eliminating waste (work that is not highly valued by the customer) and high quality. In this lecture, I will go over the roles and responsibilities of the QA within the Scrum teams and describe the importance and uniqueness of this role.
Fault Injection and Fuzz Techniques
Mr. Shmuel Gershon
Fuzzing and Fault Injection are techniques used to simulate and reach worst-case and extreme scenarios that are normally hard to reach. Both techniques are valuable when assessing security and robustness of software and systems.
The presentation will include:
• Description of the techniques and principles behind the methods
• Pros and cons of Fault Injection/Fuzz
• Practical examples of tools in action on real-world applications, with analysis of negative and positive cases, aiming to provide the attendees with understandings and suggestions to start utilizing these testing methods.
Grouping Parameters in Testing Environment
Mr. Ran Luzzatto
In the testing world a common problem arises, there are simply too many tests cases to handle.
This problem in most cases forces a partial coverage testing, in other words – risk management.
Risks that lean on proven theories will reduce the chance of missing bugs.
One of those theories is Pair-Wise parameters which theoretically detects 95% of the bugs (where Pair Wise testing fits the tested object).
● Understand Pair-Wise and automatic test case generation
● Understand where Pair-Wise can miss fundamental test cases
● Generalize Pair–Wise algorithm to various Order of Combinations
● Asking the right questions according to testing limitations.
Beyond the theory
Lessons learned in BMC, conclusions and solutions from past attempts.
Founding sponsors :
Platinum sponsors :
Gold sponsors :
Supporting organization :