|
|
|
Better Software Conference & EXPO 2006 Concurrent Sessions
Go To: Agile Development | Managing Projects and Teams | Measurement | Outsourcing | Plan-Driven Development |
Process Improvement | Quality Assurance | Security | Special Topics | System Requirements | Testing
View by Date
| Testing | | | Thursday, June 29, 2006 9:45 AM |
Testing the Nth Release
Susan McVey, IBM Rational Software
Congratulations! Your team is entrusted with testing the next release of an excellent product, one your customers have depended on for years. How do you make sure the fifth, tenth, or even the fiftieth update release is as good or better than the first version? Mature products have their own testing issues, different from those faced with new products. Susan McVey discusses the issues many testers face with legacy systems: what to test and what to trust, dwindling resources, handling known problems, aging test cases, inadequate time to maintain infrastructure, and more. Susan shares the promises and the traps of automated regression testing suites and discusses ways to keep your tests and testware up-to-date and clean. Learn to iterate toward higher quality and keep up the enthusiasm of your team�even when they�re testing the Nth release.
� The technical debt that builds up in mature systems
• How to automate and optimize tests over time
• What to do when resources shrink but the workload doesn�t |
| | | Thursday, June 29, 2006 11:15 AM |
Smoke Tests to Signal Test Readiness
Aditya Dada, Sun Microsystems Inc
Plumbers use �smoke tests� to find leaks in pipes when it is impractical to completely seal a plumbing system. We use this term as a metaphor to define a small set of software tests designed to expose big problems instead of committing the resources to run a large suite of tests. Building a powerful smoke test suite is not trivial and not intuitive, requiring an understanding of the product, the test base, and test automation techniques. Join Aditya Dada to learn the attributes of a high quality smoke test suite and what it takes to build and, most importantly, maintain a small set of effective smoke tests. Improve nightly builds, speed up pre-integration testing, and catch huge defects quickly and efficiently with a new smoke test strategy for your software under test.
� Benefits and attributes of smoke tests
• How to manage a smoke test suite with minimum effort
• Real world examples of smoke tests |
| | | Thursday, June 29, 2006 1:30 PM |
Testing SOA Middleware: Automating What You Can�t See
Jon Howarth, Wells Fargo
SOA projects employing Web services have multiple back-end integration points, volatile data, and no direct, visible user interface. Together, these factors make SOA applications complicated to test. Most companies opt for indirect manual testing because they see no other option. However, there is a light at the end of the tunnel. Using real-world case studies as examples, Jon Howarth reveals step-by-step the data driven model Wells Fargo employs to automate its SOA regression testing. Learn about the problems their QA groups encountered and the solution that drove down costs and cycle times while increasing quality. Find out how to staff and train your team to support the solution and see example metrics to measure its effectiveness. Learn how to combine vendor tools to optimize your SOA automated testing into an integrated test framework.
� An automated testing strategy for SOA applications
• Ways to automate test data setup, tear down, and post-test condition validation
• A test framework integrating multiple tools |
| | | Thursday, June 29, 2006 3:00 PM |
The Power of Continuous Integration with Automated Unit Tests
Jeffrey Fredrick, Agitar Software Inc
Better, faster, cheaper�the mantra of many software methodologies and tools. Can it ever be true? Illustrated with examples from Agitar Software's internal development process, Jeffrey Fredrick describes the psychological impact of rapid feedback and how it unleashes the best in people. Find out what continuous integration means in the real world and how it can be coupled with automated developer (unit) tests to reduce the number and cost of failures. Learn about the psychological impact of lava lamps, email notifications, and Web applications as feedback mechanisms and why feedback is not only for developers. Instead of expecting people to act like machines, you can use continuous integration and automated tests to leverage the complementary strengths of each. See how automating integration maximizes the return on your developer testing investment.
� The impact of continuous integration
• How to use automated developer tests with continuous integration
• The differences between lots of tests and code under continuous tests |
| |
|
|
