Identifying the failure points in complex eBusiness systems is becoming increasingly difficult. These systems may integrate business-to-business components, support e-commerce, and facilitate the delivery of electronic content. Learn how to evaluate the hardware, communications, and software architectures to design a successful test strategy to validate functional and structural requirements.
How do you know when you're finished testing? How do you know when the product is ready to ship? Sometimes the decision to stop testing and release a product seems as if someone's making deals in a smoke-filled room, or that there are rules of the game of which we are unaware. At times, these rules seem completely arbitrary. Instead of arbitrary decisions, it is possible to come to an agreement about when the product is ready to release, and even when it's time to stop testing. In this presentation, learn how to define release criteria, and then use those criteria to decide when to release the product.
Balancing testing against risk in eBusiness and e-commerce applications is essential because we never have the time to test everything. But it's tough to "get it right" with limited resources and the pressures to release software quickly. Paul Gerrard explains how to talk to the eBusiness risk-takers in their language to get the testing budget approved and the right amount of testing planned. Find out how to identify failure modes and translate these into consequences to the sponsors of the project. Using risk factors to plan tests means that testers can concentrate on designing effective tests to find faults and not worry about doing "too little" testing.
How often have you wished that you knew what your customers really thought of your Web site? You can extract a gold mine of information from your Web server's log to reveal how your site is used. Learn ways for your team to use this information to organize browser testing based on user statistics, improve testing coverage of your Web site, and plan more realistic load testing.
Putting the Web on cellular phones, PDAs, and other wireless devices is all the rage. Still in its infancy, the idea of doing online transactions via mobile devices has created a new buzzword: "M-Commerce." However, some companies in their quest to be first-to-market have overlooked the fact that this new technology is still in need of basic testing for quality, performance under load, and usability. Discover the importance of testing wireless applications, and learn how to identify common bottlenecks and problems.
In many ways, development of scripts for automated testing is similar to software development. It involves requirements, design, code, test, and use. So why not use proven improvement activities to enhance the test script development process? This presentation discusses how one software test team adjusted and applied inspections to test script development. Learn the results of these inspections and how you might use this technique to improve the test script development activity in your organization.
Once development reaches "code complete," the testing team takes over and drives the project to an acceptable quality level and stability. This is accomplished by weekly build cycles or dress rehearsals. The software is graded based on found, fixed, and outstanding errors. Development strives to increase the grades in each build--improving the quality and stability of the software. Learn how to use this "dress rehearsal" process to build team morale, develop ownership by the entire development team, and ensure success on opening night.
You've purchased the tools. Now you're ready to start Web load testing. Learn how one company developed a process that supports-in a repeatable manner-the planning, coordination, results analysis, and results reporting that are necessary to make a Web load test cost-efficient and effective. Using information gained from lessons learned, documentation templates, and planning templates, get a jump start on your process.
The Extensible Markup Language (XML) provides a standards-based approach for defining and exchanging data. Gain an overview of XML concepts and terminology, XML conformance testing, validation, well-formedness checking, and performance testing. Learn how to create and implement XML specific test strategy, test plans, test cases, and test data based upon the instructor's real-world experiences.
In this presentation, John Peraza describes how to use white-box testing to discover those defects that would otherwise remain undetected if you only conducted black-box testing. Learn various techniques-including test coverage, run-time memory leak detection, dynamic bounds checking, and code assessment for internationalization-that you can use to conduct white-box testing. Discover how BMC Software has benefited from including white-box testing in its quality assurance efforts.