|
|
Implementing a Final Regression Test Process After applications move into production, it is vital that subsequent additions or modifications are thoroughly tested and that the entire system is re-tested to ensure that it still functions after these changes. This process, called final regression testing, should be repeated for every new release. Many organizations that have attempted to implement a final regression test process have discovered that it isn't as easy as it sounds. In Jeff Tatleman's presentation you will learn a step-by-step approach to ensure successful implementation of a process that meets your technical needs and is attractive to your management.
These steps include documenting manual test cases, creating a dedicated testing environment, standardizing test data, and using automation.
- Analyze risk to ensure proper regression test coverage
- Use manual tests to drive test automation
|
Jeff Tatelman, Avaya
|
|
|
Quantifying the Value of Your Testing to Management Congratulations, you're a true testing expert. You know all there is to know about test planning, design, execution and reporting, performance tests, usability tests, regression tests, agile, SCRUM, and all the rest. But it’s still
possible that your IT executives and business stakeholders do not fully understand the value of your work. It's time to communicate with them in a language they understand: Return on Investment (ROI). Arya Barirani will show you how to calculate the ROI of common test activities including test
automation, defect reduction, and downtime prevention; how to create reports for maximum effect; and how to evangelize the value of your testing efforts. You will learn how to make better decisions about investments like strategic
sourcing, lab infrastructure, and staffing through better quantification of their business value.
- Learn how to use ROI as a metric to demonstrate the value of testing
|
Arya Barirani, Mercury
|
|
|
STARWEST 2006: Positioning your Test Automation Team as a Product Test automation teams are typically created with the expectation of facilitating faster testing and higher product quality. To achieve these goals, the test
automation team must overcome many challenges--stale test data, burdensome test script maintenance, too-frequent product upgrades, insufficient resources, and unfamiliarity with the systems under test. Satya Mantena describes a creative approach to test automation that overcomes
these challenges. The first step is implementing keyword-driven testing. Satya demonstrates how the keyword testing approach is implemented proving this approach is not just theory but has been "proven in action." Satya concludes
by showing how positioning the test automation team as a "product" rather than as a central service, or embedded within each testing team, results in better testing.
- Examine the difference between a service and a product
|
Satya Mantena, Nielsen Media Research
|
|
|
Back to the Beginning: Testing Principles Revisited In 1976, Glenford Myers listed a set of testing principles in his book Software Reliability. Computing has changed dramatically since those days! iPods have more computing power than the Apollo spacecraft. Testing has even been
recognized as a profession-but testing approaches have not changed substantially since Myers' book. Erik Petersen examines classic testing principles to help us understand what still works and what doesn't. He compares some of
the originals with newer principles, including those from the international ISTQB™ testing syllabus. Along the way, Erik takes a light-hearted look at the state of software reliability today.
- Review old testing principles that are still applicable
- Consider new principles that the first generation of testers missed
- Evaluate the quality of software testing today
|
Erik Petersen, Emprove
|
|
|
The Nine "Forgettings" People forget things. Simple things like keys, passwords, and the names of friends long ago. People forget more important things like passports, anniversaries, and backing up data. But Lee Copeland is concerned with things
that the testing community is forgetting--forgetting our beginnings. We forget the grandfathers of formal testing and the contributions they made. We forget organizational context, the reason we exist and where we fit in our company. We forget to grow, to learn, and to practice the latest testing techniques. And we forget process context, the reason that a process was first created but which
may no longer exist. Join Lee for an explanation of these nine "forgettings", the negative effects of each, and how we can use them to improve our testing, our organization, and ourselves.
- Learn how we must constantly rediscover
|
Lee Copeland, Software Quality Engineering
|
|
|
A Bug's Life The quality of software is directly related to the number and severity of bugs in software when it goes into production. Inspired by the Disney® film of the same name, Lloyd Roden offers a light-hearted, humorous presentation with a serious message-neglect the bugs and they will take over! Learn about novel strategies to detect and fix bugs before they bite you. Find out ways to change your environment to make it less likely to attract bugs and easier to exterminate the ones that do invade your software. Explore the people issues that can cause unnecessary stress and concern for everyone involved in dealing with bugs in the development process. Take back a new attitude about bugs and a new energy to eradicate them in your house.
- How to find the different types of software bugs
- The environment where bugs are most likely to live
- People issues surrounding bugs
|
Lloyd Roden, Grove Consultants
|
|
|
The Power of Continous Integration with Automated Unit Tests 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
|
Jeffrey Fredrick, Agitar Software Inc
|
|
|
Software Metrics to Improve Release Management In large organizations with multiple groups or multiple projects, developing consistent and useful metrics for release management is highly challenging. However, when targeted at specific release goals, metrics can help monitor the development schedule and provide both managers and developers with the data needed to improve quality. With nearly eighty products that must be released on the same date, Mathworks has developed a release metrics program with a consistent method to categorize and prioritize bugs based on severity and frequency. Learn how they track progress toward bug fix targets for each category of bugs and monitor them consistently across their product line throughout the release cycle. See examples of metrics reports designed for management and daily use by teams, including historical trending analysis of overall and customer-reported bug counts.
|
Nirmala Ramarathnam, The MathWorks Inc
|
|
|
Agile Offshore Development: An Oxymoron? Companies that master Agile development in a multi-shore environment can benefit from reduced calendar time to implement new features, early development feedback to make course corrections, and increased development team responsiveness to changing market requirements. Multi-shore Agile development teams face unique challenges compared with co-located teams-large time zone differences, lack of proximity, cultural differences, and more. With experience driving multi-shore Agile development with several enterprise software companies, Roger Nessier describes ways that he has addressed these challenges. He discusses sprint planning with distributed teams, how to structure and assign work, and tools for communicating in real-time to create an Agile global development environment. Learn about the benefits and limitations of using Scrum management practices for offshore development and what it takes to be successful.
|
Roger Nessier, Symphony Services
|
|
|
Successful Software Managment: Fifteen Lessons Learned We normally think about process improvement as something applied to projects. But process improvement is also for people-and even for managers. Join Johanna Rothman as she shares lessons she's learned and management improvements she's made during her years in management. Like many other technical managers, Johanna became a manager by rising through the technical ranks. And, like many other managers, she had plenty of technical training and mentoring but had to learn management skills the hard way-through trial and error. Johanna describes fifteen lessons she has learned as a manager and offers tips and techniques to help you avoid difficult situations. Learn how to motivate your team and raise their level of work-and how to manage yourself.
- What is the software manager's real job
- How to create an effective work environment
- How to help people do their best work
|
Johanna Rothman, Rothman Consulting Group, Inc.
|
