Google Tech TalksMarch, 6 2008ABSTRACTThe extensive use of automated testing has been a breakthrough practice in improving the quality of software produced by developers. By now, many companies have experimented with the use of automated functional tests and unit tests. Those that have had good experiences with it rave about it and cannot imagine having been successful without their automated tests. But for every success story there are many (often untold) stories of disappointment. What separates the success stories from these disappointments?In this presentation Gerard describes a number of common problems encountered when writing and running automated unit and functional tests. He characterizes the problems in the form of "test smells", describes their root causes, and suggests possible solutions expressed in the form of patterns. Although these patterns and smells originated from the developer community's use of xUnit for automated unit testing, many of these smells and patterns are equally applicable to automated functional/acceptance tests using tools such as Watir and some even apply to Recorded Test tools such as Mercury's QuickTest. While many of the practices he describes are directly actionable by developers or testers, many also require action from a supportive manager and/or system architect to be achievable.Speaker: Gerard MeszarosGerard Meszaros is a Calgary-based consultant specializing is agile development processes. Gerard started his career in Ottawa working at Bell Northern Research building telephone switching software. He left Ottawa in 1995 to join ClearStream Consulting where he built his first unit testing framework in 1996 and has been doing automated unit testing ever since. He is an expert in test automation patterns, refactoring of software and tests, and design for testability. Gerard has applied automated unit and acceptance testing on projects ranging from full-on eXtreme Programming to traditional waterfall development and technologies ranging from Java, Smalltalk and Ruby to PLSQL stored procedures and SAP's ABAP. He is the author of the book xUnit Test Patterns -- Refactoring Test Code published by Addison Wesley Professional in the Martin Fowler Signature Series. [More] [Less]

This videos presents how we are managing tests while developping the Qualinnove Extensions based on the opensource soft Egroupware for managing project in an agile and collaborative way.

Google TechTalksJune 13, 2006James BachI work with project teams and individual engineers to help them plan SQA, change control, and testing processes that allow them to understand and control the risks of product failure. Most of my experience is with market-driven Silicon Valley software companies like Apple Computer and Borland, so the techniques I've gathered and developed are designed for use under conditions of compressed schedules, high rates of change, component-based technology, and poor specification. ABSTRACTYou're already an experienced tester. You know how to design tests and report bugs. Now what? Do you feel like an expert? Unfortunately, if you want to become very good at... [More] [Less]

Spend an hour with Oracle PL/SQL expert Steven Feuerstein and explore the code-testing challenges facing PL/SQL developers. He will demonstrate how the new Quest Code Tester for Oracle dramatically simplifies testing because it: - Automates the unit testing process to greatly increase the number of tests defined and running on the application code base - Executes tests with the press of a button and visually presents the automatically generated results - Enables deep insight on test results and the development process through an in-depth repository and a rich reporting interface - Generates numerous test cases using pre-defined test data groups and quick-build scenarios, leaving more time to write application code - Improves the quality of code by finding more bugs, faster than ever. [More] [Less]

Google Tech TalksAugust 27, 2007ABSTRACTModel-based testing can help to reduce the cost of testing and increase its effectiveness. Instead of designing test cases by hand, model-based testing allows a test engineer to automatically generate test cases from a model of the system under test.After a brief overview of model-based testing, this talk will compare two different kinds of test model: black-box models and white-box models. Black-box models are easier for programmers to write and tools to use, while white-box models require more sophisticated notations and modelling skills, but can allow more sophisticated test generation.These two styles of models will be illustrated by using... [More] [Less]

Google Tech TalksNovember, 16 2007This talk describes techniques that use model checking and symbolicexecution for test input generation. Abstract state matching is usedto avoid generation of redundant inputs. The techniques handle complexdata structures, arrays, as well as multithreading, and generateoptimized test suites that satisfy user-specified testing coveragecriteria. The techniques are applicable to both (executable) modelsand to code, and can be used in black box or white box fashion. Wehave applied the techniques to generate test sequences forobject-oriented code and to generate test vectors for NASA software.Speaker: Corina PasareanuCorina is a Research Scientist at NASA Ames Research Center, in the Robust Software Engineering Group, employed by Perot Systems Government Services. She received her Ph.D. in Computer Science from Kansas State University. She is currently investigating the use of abstraction and symbolic execution in the context of the Java PathFinder model checker, with applications in test input generation and error detection. She is also working on using learning techniques for automating assume-guarantee compositional verification. Her other research interests involve the design of a command execution language and the verification of the associated execution system (PLEXIL). [More] [Less]

Spend an hour with Oracle PL/SQL expert Steven Feuerstein and explore the code-testing challenges facing PL/SQL developers. He will demonstrate how the new Quest Code Tester for Oracle dramatically simplifies testing because it: - Automates the unit testing process to greatly increase the number of tests defined and running on the application code base - Executes tests with the press of a button and visually presents the automatically generated results - Enables deep insight on test results and the development process through an in-depth repository and a rich reporting interface - Generates numerous test cases using pre-defined test data groups and quick-build scenarios, leaving more time to write application code - Improves the quality of code by finding more bugs, faster than ever. [More] [Less]

Google Tech TalksMarch, 6 2008ABSTRACTThe extensive use of automated testing has been a breakthrough practice in improving the quality of software produced by developers. By now, many companies have experimented with the use of automated functional tests and unit tests. Those that have had good experiences with it rave about it and cannot imagine having been successful without their automated tests. But for every success story there are many (often untold) stories of disappointment. What separates the success stories from these disappointments?In this presentation Gerard describes a number of common problems encountered when writing and running automated unit and functional tests. He characterizes the problems in the form of "test smells", describes their root causes, and suggests possible solutions expressed in the form of patterns. Although these patterns and smells originated from the developer community's use of xUnit for automated unit testing, many of these smells and patterns are equally applicable to automated functional/acceptance tests using tools such as Watir and some even apply to Recorded Test tools such as Mercury's QuickTest. While many of the practices he describes are directly actionable by developers or testers, many also require action from a supportive manager and/or system architect to be achievable.Speaker: Gerard MeszarosGerard Meszaros is a Calgary-based consultant specializing is agile development processes. Gerard started his career in Ottawa working at Bell Northern Research building telephone switching software. He left Ottawa in 1995 to join ClearStream Consulting where he built his first unit testing framework in 1996 and has been doing automated unit testing ever since. He is an expert in test automation patterns, refactoring of software and tests, and design for testability. Gerard has applied automated unit and acceptance testing on projects ranging from full-on eXtreme Programming to traditional waterfall development and technologies ranging from Java, Smalltalk and Ruby to PLSQL stored procedures and SAP's ABAP. He is the author of the book xUnit Test Patterns -- Refactoring Test Code published by Addison Wesley Professional in the Martin Fowler Signature Series. [More] [Less]

Google Tech TalksAugust 27, 2007ABSTRACTModel-based testing can help to reduce the cost of testing and increase its effectiveness. Instead of designing test cases by hand, model-based testing allows a test engineer to automatically generate test cases from a model of the system under test.After a brief overview of model-based testing, this talk will compare two different kinds of test model: black-box models and white-box models. Black-box models are easier for programmers to write and tools to use, while white-box models require more sophisticated notations and modelling skills, but can allow more sophisticated test generation.These two styles of models will be illustrated by using... [More] [Less]

This series of videos will go through building a KPI that reports on code coverage in a Visual Studio Team System project. This first video will illustrate the basic project, data source and cube setup.

This videos presents how we are managing tests while developping the Qualinnove Extensions based on the opensource soft Egroupware for managing project in an agile and collaborative way.

Google TechTalksJune 13, 2006James BachI work with project teams and individual engineers to help them plan SQA, change control, and testing processes that allow them to understand and control the risks of product failure. Most of my experience is with market-driven Silicon Valley software companies like Apple Computer and Borland, so the techniques I've gathered and developed are designed for use under conditions of compressed schedules, high rates of change, component-based technology, and poor specification. ABSTRACTYou're already an experienced tester. You know how to design tests and report bugs. Now what? Do you feel like an expert? Unfortunately, if you want to become very good at... [More] [Less]

Google Tech TalksNovember, 16 2007This talk describes techniques that use model checking and symbolicexecution for test input generation. Abstract state matching is usedto avoid generation of redundant inputs. The techniques handle complexdata structures, arrays, as well as multithreading, and generateoptimized test suites that satisfy user-specified testing coveragecriteria. The techniques are applicable to both (executable) modelsand to code, and can be used in black box or white box fashion. Wehave applied the techniques to generate test sequences forobject-oriented code and to generate test vectors for NASA software.Speaker: Corina PasareanuCorina is a Research Scientist at NASA Ames Research Center, in the Robust Software Engineering Group, employed by Perot Systems Government Services. She received her Ph.D. in Computer Science from Kansas State University. She is currently investigating the use of abstraction and symbolic execution in the context of the Java PathFinder model checker, with applications in test input generation and error detection. She is also working on using learning techniques for automating assume-guarantee compositional verification. Her other research interests involve the design of a command execution language and the verification of the associated execution system (PLEXIL). [More] [Less]