Quarta, 19 Dez 2018

Tutoriais

Terça-feira, 11 de outubro de 2011

Martin Pol Test Process Improvement using the TPI® NEXT model
Martin Pol, Polteq Test Services B.V.

What is the maturity of your testing process? How do you compare to other organizations and with industry standards? Join Martin Pol for an introduction to the Test Process Improvement (TPI® NEXT) model, an industry standard for test process maturity assessment. Many organizations want to focus on achieving the highest level of maturity without first creating the foundation required for success. Improving your testing requires understanding sixteen key test process areas, your current position in each of these areas, and the next steps to take for improvement. Rather than guessing what to do, use the TPI® NEXT model as a guide. Employing real world test process maturity assessments he has performed in a variety of organizations around the globe. Martin describes an assessment approach that is suitable for both smaller, informal organizations and larger, formal companies. After the tutorial you’re able to apply the model right away.

TPI® NEXT is a registered trademark of Sogeti



Gerard Numan A practical approach to Integration and E2E-testing
Gerard Numan, Polteq Test Services B.V.

The major test challenge nowadays is to handle the growing complexity of the application landscape and to validate business and customer processes (so called End to End processes) that depend on this landscape. This is why testing needs to extend the approach to risk analysis: we testers need to cover different and more difficult aspects to discover risks: to pursue high quality through the chain we need an effective E2E-risk analysis approach and an efficient, flexible E2E-test process.

This experience based tutorial shows the steps towards successful Integration and E2E-testing. It looks at additional testing and non-testing skills that are needed in your E2E-team. The tutorial explains a model for E2E-risk analysis and the subsequent test design: how to create cases that impact the application or business process chain, which are maintainable, fit for flexible regression testing and thereby enable you to mitigate the E2E-risks! Join me to make your E2E-testing vital for your organization by identifying E2E quality requirements and covering risks when moving towards the cloud.

Tutorial outline:

  1. Clarification of the subtle difference between interfacing, integration and E2E, enabling you to truly cover the major E2E-risks
  2. Detailed steps to make an inventory of E2E-processes, mapping these to the components in your application landscape, including the cloud
  3. How to perform an E2E-risk analysis, translating these into designing and setting up of test cases
  4. Managing test cases, test data and test environments in order to facilitate defect analysis, continuous integration, continuous acceptance and regression testing
  5. How to integrate technical, domain and process knowledge in your E2E-testteam

This tutorial will help you make E2E-testing understandable and manageable.





Ir para o topo

 

Quarta-feira, 12 de outubro de 2011

Lee Copeland Key Test Design Techniques
Lee Copeland, Software Quality Engineering

All testers know that we can identify many more test cases than we will ever have time to design and execute. The major problem in testing is choosing a small, “smart” subset from the almost infinite number of possibilities available. Join Lee Copeland to discover how to design test cases using formal black-box techniques, including equivalence class and boundary value testing, decision tables, state-transition diagrams, and all-pairs testing. Explore white-box techniques with their associated coverage metrics. Evaluate more informal approaches, such as random and hunch-based testing, and learn the importance of using exploratory testing to enhance your testing ability. Choose the right test case design approaches for your projects. Use the test results to evaluate the quality of both your products and your test designs.



Janet Gregory Successful Automation in an Agile Environment
Janet Gregory, DragonFire, Inc.

Agile teams deliver “potentially” shippable software at the end of every iteration (one to four weeks), or even possibly every day. This goal can't be achieved without automated tests and many teams struggle with test automation. The challenge of automating functional regression tests frightens many testers, who feel their skills aren’t up to the job. How do we deliver good quality when we have to release so often?

By combining a collaborative team approach with appropriate tools and design approaches, over time you can not only automate your regression tests, but also use automation to enhance exploratory testing. In this interactive tutorial, Janet Gregory describes how to use automation early and guide development; what tests should be automated; works through ways to overcome common barriers to automation. Janet will use examples to learn how to design automated tests for maximum effectiveness and ease of maintenance. Find out different approaches for evaluating and implementing automated test tools, shortening feedback cycles, creating realistic test data, and evaluating your automation efforts.

By the end of this session, you’ll understand how to fit automation activities within each iteration so testing “keeps up” with coding.

Janet Gregory Planning Your Agile Testing: A Practical Guide
Janet Gregory, DragonFire, Inc.

Traditional test plans are incompatible with agile software development because we don't know all the details about all the requirements up front. However, in an agile software release, you still must decide what types of testing activities will be required—and when you need to schedule them. Janet Gregory explains how to use the Agile Testing Quadrants, a model identifying the different purposes of testing, to help your team understand your testing needs as you plan the next release. Janet introduces you to alternative, lightweight test planning tools that allow you to plan and communicate your big picture testing needs and risks. Learn how to decide who does what testing—and when. Determine what types of testing to consider when planning an agile release, the infrastructure and environments needed for testing, what goes into an agile “test plan,” how to plan for acquiring test data, and lightweight approaches for documenting your tests and recording test results.





Ir para o topo