QA
Articles
How to Squeeze the Most Out of Your Automated Testing Jonathan Lindo describes examples of automated test infrastructure utilizing both open source and traditional, independent-software-vendor-sourced software. In addition, he discusses new techniques for extending the value of automated testing by transforming the process from defect finding to defect resolution by reducing the effort required to document, reproduce, and troubleshoot the defects generated from automated tests. |
Jonathan Lindo
July 25, 2011 |
|
Why Testers and QA Engineers Need to Learn Continuously Information technology changes fast, and none of us knows what our future holds. It’s hard to keep up with new programming languages, patterns, tools, frameworks, design techniques, and practices. If you’re a programmer who doesn’t keep her skills up to date, you won’t get the best job opportunities—in fact, you might not get any. Yet, we observe many people who call themselves testers or quality assurance professionals but don’t make much effort to learn new things. |
||
Picking SCM Standards or Frameworks There are many things to consider when picking an SCM standard or framework for your organization. Taking the time to explore compliance, politics, experience, and driving forces before making a selection will increase acceptance and smooth the transition. |
||
Database Compare and Synchronize Methods as a Part of the Software Release Management Process By testing migration processes between environments, bugs are able to be found earlier, and before the migration to production. Using automatic packages, and well-thought out staging areas, migration can be a less painful, and more informative process than it may have been for you in the past. |
||
Small Teams in a Large Organization Ben Weatherall writes that the need to tailor existing SCM tools should be kept to a minimum and the solutions be implemented is such a way as to be reused in the future. Additional SCM requirements for these teams over and above those already in place are generally modest. |
||
What Project Managers Need to Know About Testing What happens when project managers of cross-organizational teams don't have all the cross-functional team knowledge, such as testing, they need to manage all the teams? Johanna Rothman explains that managers in this situation might have a recipe for disaster. But with careful planning, any project manager can quickly turn it around and create an efficient team and a career development opportunity for everyone. |
||
Testing's Role in the Software Configuration Management Process In this article, the authors cover how testing can support any SCM environment and how testing can be part of the SCM process. They outline at patterns, roles, automation, and the never-ending search for simplicity. |
||
Using Quality Function Deployment for Process Improvement Organizations are recognizing the need for strong process architecture to manage their operations. Increasing acceptance of International models and practices like CMMI, ITIL, Six Sigma stands testimony to the fact., In such a scenario, it becomes imperative that organizations have a clear strategy when they put in place a process improvement program. In other words, the process for implementing a process improvement program also needs a proper structure. Using Quality Function Deployment (QFD) as a tool for initiating a process improvement program could come in handy. |
||
Making Business Sense of CMMI Level 4 For some reason, the mystique of CMMI Level 4 seems to be wrapped around control charts—one of the methods used for statistical analysis of data. While use of control charts is almost always present in statistical analysis of software processes, Ed Weller all too often sees the reason for using statistical methods—and the reasoning behind the superficial analysis—lost in the concern for "building control charts to show that Company X is CMMI Level 4." Ed Weller offers valuable insight on CMMI Level 4 and what it really signifies. |
||
Cases Against Applying Schedule Pressure Do you think that by removing deadlines from a project a team will have enough time to create perfect software? Theoretically, it's possible, but in this column Mike Cohn explains that this theory might not hold against ingrained behavior. He recalls how several teams reacted when deadlines were lifted from the projects they were working on. Their only goal: to produce perfect software. But that goal inadvertently brought something to the surface, that old habits die hard. |
Pages
Recommended Web Seminars
May 23 | How Generative AI Boosts Speed and Quality in Software Testing |
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |