|
Juggling Can Improve Productivity At the 2000 Amplifying Your Effectiveness (AYE) conference I attended a class called "Being a Change Leader." One of the instructors, Sheila Smith, selected five volunteers from the audience. She told these volunteers that for this role-playing demonstration they were now her employees and she was their manager. Their company had studied and researched ways to improve productivity, and had determined that they could obtain a 50 percent increase in productivity by learning to juggle. The company was now making it mandatory for all employees to learn how to juggle. |
Todd Berbert
November 27, 2000 |
|
|
A Risk-Based Test Strategy The development of a test strategy is a means of communication with the customer commissioning the test on such matters as the organization of testing and the strategic choices that go with it. The test strategy indicates how testing is to be carried out. In order to make the best possible use of resources and time, it is decided on which parts and aspects of the system the emphasis should fall. The test strategy forms an important basis for a structured approach to testing and makes a major contribution to a manageable test process. |
||
|
Equilibrium in Managing Outsourced Testing This paper details some of the lessons I learned in my first assignment managing outsourced testing. It explains how we can find equilibrium between managers and testers and between internal and external people, what we can do to ensure that the product maintains our high standard of quality, and how we can prepare for and respond when things go wrong. |
||
|
High Speed Testing Cycles Testing has never been easy, but when it comes to large institutions, things can get terribly complex. Take large banks for example. For years they developed their own solutions, building applications and bringing in all kinds of hardware and software available, in order to provide their customers with better products and services. Most of the times buying decisions were taken on the go, following no architectural model or plan, which, unfortunately, led them to rely on modern Frankensteins (a.k.a. automated beasts ) to take care of their most valued asset: their customers. |
||
|
API Testing Method with Markov Models This paper presents a technique to test APIs that combines aspects of two published software testing methods, namely Markov modeling and category partitioning. Markov modeling provides a basis for model based testing and establishes the context for generating API calls and call sequences within a single test case. |
||
|
Mutating Automated Tests Most automated tests are used as regression tests - doing the same exercises each time the test is run. This paper and talk describe a powerful type of automated test - one that does something different each time it runs. |
Douglas Hoffman
November 21, 2000 |
|
|
Automated Testing of Embedded Software There are no silver bullets for automating embedded system testing to guarantee success. Based on the specific type of embedded system, there are many different ways to succeed or potentially fail. This paper gives an overview of what needs to be done for automated embedded systems testing, the similarities between the GUI testing and the Embedded Systems, and a successful approach used for more than one application. |
Jim Kandler
November 21, 2000 |
|
 |
Integrated Development/Test Project Teams This article describes a real-life situation where the test organization participated as part of the development team and was included in all phases of the development lifecycle for a highly successful software project. The project was an upgrade of the software and hardware for a mission critical communications system in the aerospace industry. |
David Petrella
November 20, 2000 |
|
Testing Component-Based Software Today component engineering is gaining substantial interest in the software engineering community. Although a lot of research effort has been devoted to analysis methods and design strategies of component-based software, few papers address the testing of component-based software. The paper identifies and classifies the testing issues of software components and component-based software according to working experience. |
||
|
Maximizing the Value of Your Test Environmnt The objective of this paper is to provide insight to the integrated processes, financial and resource requirements, and technical components necessary to achieve a robust end-to-end test environment. A fully integrated environment will enable end-to-end testing, quality improvement and pre-production certification for your suite of applications. The presentation further examines the vision, components, approach and methodology, and business processes that are critical to a successful test environment. |
Pages
Upcoming Events
| Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
| Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |
