Testing information systems should be based on the business risks to the organization using these information systems. In practice, test managers often take an intuitive approach to test coverage for risks. In this double-track presentation, discover how a "stepwise" definition of test strategy can be used for any test level as well as the overall strategy-providing better insight and a sound basis for negotiating testing depth.
STAREAST 2000 - Software Testing Conference
Automating testing for embedded systems has been a real problem in the past. The only option was a customized approach, which is expensive and very risky. There are now mature catalogued hardware interfaces available that can be assembled with a mature scripting language complete with a rich tool set to drive these interfaces. Learn of one successful approach using this "off-the-shelf" system. Discover the important characteristics of a testing system for embedded processes.
The battle lines are drawn, it seems, between programmers and testers. Do you wonder what makes some programmers so opposed to process control? Why do programmers seem to resent testers? And, more importantly, what can we do to bridge the gap? Learn how to identify different types of developer personalities and development styles and deal with them to your advantage. Susan Joslyn explores ways to inspire quality (recovery) in coding cowboys while minimizing clashes.
Brian Lawrence begins his presentation with a brief overview of what a review is and how it works in software organizations. Although testers may or may not understand source code, they can still contribute considerable value in reviews. Learn how to devise tests as a review preparation technique that can identify potential defects and serve as a basis for test planning and design.
Fast development cycles, distributed architectures, code reuse, and developer productivity suites make it imperative that we improve our software test methods and efficiency. What process assessments are available? How do you conduct an assessment? How do you guard against incorrect information? How do you know what to improve first? And how can you make successful improvements without negatively impacting your current work?
Each generation of technology-mainframe to client/server to Internet-creates opportunity. It also creates increased risks. Improving the development and testing infrastructure can be a significant investment. Tools need to be required; staff needs to be trained; and outside guidance in the tools and processes may be necessary. This presentation will address ten major areas of opportunity which underscore why this investment is critical to the success of an organization.
From this presentation's summary:
- Re-Design Testing to Provide Information to Manage Risks
- Use Risk Analysis to Determine What & When to Test (Knowledge)
- Design Test Activities to Provide Feedback about Risks (Information)
- Use a Hierarchical Test Approach with Feedback
- Remember The Business Goal (Wisdom)
Although management supervision is a critical factor to a test program's success, it is often entrusted to people with minimal experience and training in these areas. Based on the real-life experience of a fifteen year veteran, this presentation is a crash course in the keys to successful test team supervision and management. Discover how to jump start your test management career and improve your chances of success.
The profile of testing has been raised significantly in the last few years, largely due to Year 2000 issues. Organizations accept that they need to systematically and thoroughly test software, and they are demanding the same levels of efficiency that are expected from all other areas of their businesses. Now it is necessary to provide evidence that the activities of the test team are an effective and efficient use of staff. Learn how such evidence can be obtained and reported with minimal overhead on testing resources.
Test engineers are often asked to create a test plan for a product. Once the goals of the test project are defined, a test strategy needs to be developed. The second step is to create a test project plan to implement this strategy. A third and final step is to create the actual test case according to the test project plan and test strategy. Learn how these three components-both singularly and collectively-can contribute to a successful test project.