At each level of integration (class, component, subsystem, and system), there are possible interactions between the pieces that are being integrated. John McGregor presents two techniquest to use consistently at each of the levels of integration to locate faults due to incorrect interactions. Learn how an interaction matrix and a statistical sampling technique provide a complement to the standard functional and structural test case design strategies.
STARWEST 1999 - Software Testing Conference
The Java Virtual Machine (JVM) relies on a large and complex software base for its security and integrity, making it difficult to test and verify. Traditional testing techniques are time consuming, expensive, and imprecise. Emin Gun Sirer discusses his experiences with automatically testing JVMs. Learn three practical and effective automated techniques for testing. Observe the security flaws uncovered by each technique with examples from commercial JVMs.
This presentation covers conditions and expressions; truth tables; normal form patterns; modified condition/decision coverage; constructing an MC/DC test set; tools for checking MC/DC coverage; unique cause coverage; basic unique cause design; and logic coverage references.
Many of us have worked in test groups where we felt as if we didn't have enough time, staff, or computer resources to do the work. We may not even know precisely what we need to test. Consequently, we feel that while development may be in control, we certainly are not. Johanna Rothman contends that testers do not have to work this way. Learn effective ways to develop and use your influence within your organization to help your test group-and project-succeed.
Since the subjective aspects of software quality do not lend themselves to being put into numbers or graphs, they are often overlooked. Using a model referred to as "ICED T," Andy Roth discusses what these subjective aspects are, why they are important, and how to test for them. New testers and seasoned veterans alike can use this model to gain a broader perspective of software quality.
This presentation identifies ways to use available or inexpensive tools to develop test scripts, organize test data, and produce test reports. Discover why word processors are not the best tools for test scripts and how spreadsheets can enhance test scripts and automate test execution. Learn to use your best tools early: your eyes and your brain!
This presentation examines steps you should take before attempting to implement automated testing in a production environment. Learn through real-life examples how to establish standards, develop a procedure library, and develop your automated test environment. Discover how to handle management and personnel issues before automated testing begins.
Testers know all too well that software fails. If we can understand the fundamental reasons why this happens, we can become more efficient and effective at finding bugs. James Whittaker explains the reasons why software fails and demonstrates how this knowledge can be used to break real software. The technology described has emerged from three years of contract testing at Florida Tech in which teams of students test (and break) post-release commercial software.
To most software developers, testers and QA managers, time is one of the most precious commodities they have. Greg Pope takes a look at negotiation tactics and other tricks of the trade that help test engineers and QA managers find more time to do their job better. Learn how realistic software process scheduling and adequate testing can increase product quality.