Software quality assurance best practices

Software quality best practices

 

 

    Requires Free Membership to View

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

We recently offered our readers the opportunity to blog about software quality and software testing. Several of you have started your own blogs and are off to a great start. If you haven't been reading our IT blogs, you're missing out on some great content. We've gathered a few selections below. Enjoy.

Software Quality Assurance

Sometimes it isn't clear when designing a new application just which of a multitude of possible approaches to the design represents the "best" approach. Sometimes it may not just be the application design, but also choosing the "right" tool to accomplish the task(s) to be executed.
Choosing the best application design approach

Any software development or quality assurance manager wants to see the maximum of software defects avoided at the earlier stages of the SDLC. I guess service engineering managers are among the happiest software managers in the world. That's because detecting FI situations is done at the feature design time. So, the process is part of the SDLC.
Software quality assurance at design time

Like other living things, software QA processes evolve over time. From its humble beginnings, test automation has undergone a similar transformation. Here's an overview.
Automated software testing: In the beginning

How are frameworks being implemented today by various QA organizations? Here's a basic summary of the types of test automation currently in use.
Types of test automation frameworks

To ensure complete coverage of software testing, testing teams must be careful about certain activities that are part of the process. If the software testing is not complete as per the business and customer requirements, it could have a severe adverse effect during or post implementation of the software at the customer site. The greater the coverage, the less chance of any bugs passing to the implementation phase.
Twenty ways to ensure complete coverage of software testing

Testing is a process of facilitating development team/project teams in improving the quality of software before it is released to the customer for use. Testers must always follow some essential steps during software testing to streamline the process. In my opinion, here are the most important checkpoints for testers during software testing.
Eight checkpoints for testers during software testing

   Got Software Quality questions? Get answers from your peers

IT Knowledge Exchange is a community of IT pros that share and pool their knowledge. You can browse answers, ask your own question or share your expertise by answering a question. Do you have an IT problem that's driving you crazy? Come ask your peers and colleagues on IT Knowledge Exchange. Or request your own blog and share your knowledge.

This was first published in August 2008