Patricia A. McQuaid
President: ASTQB, California Polytechnic State University
Before executing a test, we need to know what we are trying to test, know what inputs we plan to use, and know what the results should be that were produced by those inputs. These factors determine how we are to prepare the tests and then run them. We need to choose the test conditions and prioritize them. Test conditions can be rather vague, yet our test cases need to be specifi c. We need to create specifi c input data, so we know the exact expected output. One of the most important aspects of testing is to assess that the system does what it is supposed to do. This session deals with Test Design Techniques and will cover fi ve specifi cation-based techniques, including: equivalence partitioning, boundary value analysis, decision table testing, state transition testing, and use case testing. It will be a “hands on” session where we will apply the principles learned and design test cases according to the various test design techniques.
Yaron Tsubery, Efi Bruker
Load and performance belong to the top ten list of most frightening words in software development especially when it comes to the point of sale of your product in an extremely competitive market. One other word that is really frightening is the word ... STRESS (doesn‘t it give you shivers just hearing it?). This tutorial will get you acquainted with the terms of the subject and will contribute to your understanding of the whole desired process stages from sales meetings to design and architecture, ways of implementation, testing aspects and fi nally presenting results and reports. A part of the process you‘ll be advised about are ways to become aligned with your customer‘s expectations – means that you need to know and control the required lingo of the load profession, whether you are a sales person, developer or test engineer (e.g. ‚usage and traffi c model‘, ‚throughput‘ etc.). The tutorial will present design and architecture solutions along with special guidelines for code writing and implementation. The load test engineers will understand better what the required information to initiate load and performance testing is, what to search for and how to improve their testing coverage as well as how and what is to be reported and presented in order to give an added value to those who make the decisions. This practice is focused on projects of complex systems, delivered to telecommunication companies under restricted rules and stiff exit criteria elements in combination with tense delivery timelines.
The tutorial explains the concept of re-use with regards to test cases and talks about specifi cation reuse as well. It goes on to explain the problems of reuse questioning the possibility of reuse. An innovative concept, Q-Patterns, for creation and reuse of test cases is explained in this tutorial. You can think of Q-Patterns as a structured set of questions (tests) about the different aspects of a software application under test. They are questions about the system that are categorized, grouped, sorted, and saved for reuse. These Q-Pattern questions can be written ahead of time and stored in a repository of test cases, developed for requirements and design reviews or built in real-time as a way to both guide and document exploratory testing sessions. See examples of Q-Patterns that have been developed for error messages, combo boxes, login screens, and list handling. Learn how to associate related Q-Patterns and aggregate them into hierarchical and Web models. Take back the beginnings of Q-Patterns for your test team and organization. • Sharable and reusable test case designs • Templates to organize requirements and design reviews • A tool for capturing exploratory testing experience.
Over the last ten years, professionals working in software and system development have learned how to apply the powerful techniques of risk analysis and risk management to their projects. In this class you‘ll learn: • How to apply risk analysis techniques ranging from informal discussions to ISO 9126 to Failure Mode and Effect Analysis. • How risk prioritization can tell system development professionals where to focus development and test resources. • How the project team can improve the accuracy of the risk analysis – and thus the effectiveness and efficiency of testing – throughout the system development lifecycle. The fi rst half of the class will discuss the various techniques, and illustrate them through real case studies. The second half of the class will include a hands-on exercise to prepare you to apply these powerful techniques on your next project.
What are the key things that make the management of a test project successful? This half day tutorial will cover: 1. Managing people 2. Test Documentation 3. Testing Models and their impact on management 4. Test approach based upon Risk 5. Information provision The tutorial will be part lecture and part practical and will leave the attendees with a greater insight into what makes a good Test Manager great. In fact what makes a Test Manager the programmes Trusted Advisor.
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 identifi es 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, interactive discussion and a practical exercise. 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 very basic assessment of their own testing processes • Understand how to apply the TPI™ model TPI™ is a registered trademark of Sogeti