The Latest
|
Validation vs. Testing in a Regulated Environment[presentation] When the FDA approved the use of electronic signatures for drug acceptance by medical professionals, the software systems that captured those signatures fell under FDA audit scrutiny. |
Andrew Oliver, Dendrite International, Inc.
|
|
|
Measuring Testing Effectiveness using Defect Detection Percentage[presentation] How good is your testing? Can you demonstrate the detrimental effect on testing if not enough time is allowed? |
Dorothy Graham, Grove Consultants UK
|
|
|
Building A Dynamic Test Automation Environment[presentation] Even in a perfect world, building an organization's test automation environment is a daunting task. |
Dave Kapelanski, Compuware Corporation
|
|
|
Testing Dialogues- Technical Issues[presentation] Test professionals face a myriad of issues with immature development technologies, changing systems environments, increasingly complex applications, and 24/7 reliability demands. |
Johanna Rothman, Rothman Consulting Group, Inc.
|
|
|
Testing Toolkit for J2EE Systems: A Case Study[presentation] Taking a test team from a client/server environment to J2EE-based Web technologies and implementing test automation at the same time is a challenge. |
Clay Coleman, CapTech Ventures
|
|
|
Test Driven Project Management[presentation] In Test-Driven Development (TDD), you write a test that fails before you write the code that makes the test pass. Expanding on that concept, Glenayre Technologies set up its test organization to drive project management issues, too. |
Scott Lazenby, Glenayre Technologies
|
|
|
Use of Inspections for Product and Process Improvement[presentation] It is widely known that software inspections are a cost-effective approach for finding defects in source code as well as other project documents such as requirements specifications. |
Lawrence Day, Boeing
|
|
|
Quality Assurance and .NET: How to Effectively Test Your New .NET Applications[presentation] If your organization is migrating to .NET, you need to be concerned about how .NET will impact your department's testing and quality assurance efforts. |
Dan Koloski, Empirix Software
|
|
|
Introducing Test Driven Development[presentation] You may ask, why would anyone write an automated unit test for code that has not yet been written? |
Matthew Heusser, Priority-Health
|
|
|
Test Automation: An Architected Solution[presentation] What does it take to produce automation "testware" that is efficient, effective, maintainable, and usable? |
Dan Young, Schwab Performance Technologies
|
|
|
Pair-Wise Testing: Moving from Theory to Practice[presentation] We've all heard the phrase, "You can't test everything." This axiom is particularly appropriate for testing multiple combinations of options, selections, and configurations. |
Gretchen Henrich, LexisNexis
|
|
|
Automation Tools and Exploratory Testing: Can The First Support the Second[presentation] As a tester you might wonder if automated testing tools are capable of supporting exploratory testing. |
Mieke Gevers, Segue Software Inc
|
|
|
The ROI of Test Automation[presentation] It is widely known that software inspections are a cost-effective approach for finding defects in source code as well as other project documents such as requirements specifications. |
Michael Kelly, Liberty Regional Agency Markets
|
|
|
How to Energize Your Test Team[article] You're waist deep in your third month of late nights, weekends, and shipping stress; you can see and feel your team's energy waning. The goal is in sight but still far off, and you need the very best from everyone to reach the goal. How are you going to motivate and energize your team to reach the finish line? This article explores the major issues test team leaders face: keeping a team motivated and knowing when it needs to be energized. |
Jamie Tischart
September 13, 2004 |
|
 |
Preventing Late Tasks from Creating Late Projects[article] We like to think that being late on one task isn't so bad because early and late completions will average out over the course of an entire project. If you flip a coin 1,000 times, it will land on heads about 500 times and on tails about 500 times. If your project has 1,000 tasks, about 500 will finish early and about 500 will finish late, right? Wrong--and many project plans are sunk by this common misperception. |
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.