|
Continuous Integration—Your Project's Unlikely Hero Code sandboxes of the world, unite behind a new leader: Continuous Integration (CI). Automated and customizable, CI gives you the ability to know at the push of a button whether your application is working or whether it needs a tweak. It brings together the disparate code of countless developers and provides a real-time gauge of your application's health. Never fear nightly (or, egads! weekly) builds again. Rely on the strength of CI.
|
|
|
Fault Injection to Stress Test Windows Applications Testing an application's robustness and tolerance for failures in its natural environment can be difficult or impossible. Developers and testers buy tool suites to simulate load, write programs that fill memory, and create large files on disk, all to determine the behavior of their application under test in a hostile and unpredictable environment. Herbert Thompson describes and demonstrates new, cutting edge methods for simulating stress that are more efficient and reliable than current industry practices. Using Windows Media Player and Winamp as examples, he demonstrates how new methods of fault injection can be used to simulate stress on Windows applications.
- Runtime fault injection as a testing and assessment tool
- Cutting edge stress-testing techniques
- An in-depth case study on runtime fault injection
|
Herbert Thompson, Security Innovation
|
|
A Study of Myers-Briggs Types Relative to CM Professionals (2003) What makes configuration management (CM) professionals so unique? Is it the way we can view a complex task and break it down into meaningful activities? Is it the way we can bring some level of order to chaos? Is it that we not only want to understand the details on how things work, but we also like to understand the big picture? Is it our need to improve our environment? Or is it the way we persevere at difficult tasks in trying to bring together the pieces that comprise our deliverables?
|
|
|
Re-Engineering the Testing Organization: Get Into the Future This article discusses how updating current processes will make your test team better able to accomplish project goals. Change is good when it is implemented the right way.
|
Clyneice Chaney, Application Services
|
|
Software Testing Turnovers This paper was originally presented at an SQE STAR conference. It is offered here unedited in its original format.
|
Jeffrey S. Davis
|
|
Software Configuration Management Guidelines (template) This template describes recommended guidelines for implementing configuration management for software project artifacts and deliverables.
|
|
|
Agile Codeline Management Software developers often view version management tools and techniques as a necessary evil. This is particularly true of developers practicing agile techniques. However, version management, can be an aid to agility rather than something that gets in the way.
|
|
|
The Need for Agility in SCM What is agility? Summarizing from last month's article agility is “The ability to both create and respond to change in order to profit in a turbulent business environment…. What is new about agile methods is not the practices they use, but their recognition of people as the primary drivers of project success, coupled with an intense focus on effectiveness and maneuverability.” [2]
|
|
|
Software Configuration Management Resources It is essential that team members embrace SCM practices because coordination is necessary to achieve a reliable, productive product. After you determine which practices are appropriate, you can choose the right tool based on your needs and budget.
|
|
|
The Awful Truth About Logic-Testing This presentation covers conditions and expressions; truth tables; normal form patterns; modified condition/decision coverage; constructing an MC/DC test set; tools for checking MC/DC coverage; unique cause coverage; basic unique cause design; and logic coverage references.
|
Dave Gelperin, Software Quality Engineering
|