Abstract for PNSQC 2009
What topic sounds more interesting on the topic of the future of software?
Automating User Workflows-Strategies for identifying, prioritizing, and testing end to end user scenarios and then automating them.
Constant Beta-Testing to "good enough". More and more it seems that consumer software is expecting the end user to do most of the testing. How do we increase our smoke tests to cover what is important in order to get user feedback. How is the user feedback then verified and made actionable in an efficient way? What does it mean for testers when the new "good enough" doesn't have to be that good in some sectors?
Testing by Numbers-In this very difficult economic environment companies are looking for quick solutions. Any cost cutting measures can be the difference in a company surviving. For that reason, numbers are being considered more than ever. As test leaders and individual testers, how can we find the metrics that matter and present them to best show our value? What can we do to communicate the options to company leadership when they want to cut testing and quality or the schedule to ship a product sooner?
Reducing Test Case Bloat-See earlier blog about this, but I'd go into detail with examples about all of the ways to reduce bloat so that we can move on to testing future features.
Automating User Workflows-Strategies for identifying, prioritizing, and testing end to end user scenarios and then automating them.
Constant Beta-Testing to "good enough". More and more it seems that consumer software is expecting the end user to do most of the testing. How do we increase our smoke tests to cover what is important in order to get user feedback. How is the user feedback then verified and made actionable in an efficient way? What does it mean for testers when the new "good enough" doesn't have to be that good in some sectors?
Testing by Numbers-In this very difficult economic environment companies are looking for quick solutions. Any cost cutting measures can be the difference in a company surviving. For that reason, numbers are being considered more than ever. As test leaders and individual testers, how can we find the metrics that matter and present them to best show our value? What can we do to communicate the options to company leadership when they want to cut testing and quality or the schedule to ship a product sooner?
Reducing Test Case Bloat-See earlier blog about this, but I'd go into detail with examples about all of the ways to reduce bloat so that we can move on to testing future features.
As a tester, I would run, not walk to a seminar about test case bloat.
As an academic, I've noticed that there is not enough emphasis on metrics for testing, especially at the system test level. I've seen lots of papers about metrics for source code, much less for testing.
Good luck with your abstract. They are all great ideas.
Reply to this
Thanks Marlena! I just posted a draft abstract. It's exciting, but possibly far too casual. I'd love your feedback on it.
Reply to this