Latest Blog Posts for Software Testing

• What testing roles are standard on most testing projects?
  on Jan 10, 2013
  Depending on the organization, the following roles are more or less standard on most testing projects: Testers, Test Engineers, Test/QA Team Lead, Test/QA Manager, System Administrator, Database Administrator, Technical Analyst, Test Build Manager an...
• What is comparison testing?
  on Jan 10, 2013
  Comparison testing is testing that compares software weaknesses and strengths to those of competitors' products.
• What is recovery/error testing?
  on Jan 10, 2013
  Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
• What is security/penetration testing?
  on Jan 10, 2013
  Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage. This type of testing usually requires sophisticated testing techniques.
• What is installation testing?
  on Jan 10, 2013
  Installation testing is the testing of a full, partial, or upgrade install/uninstall process. The installation test is conducted with the objective of demonstrating production readiness. This test includes the inventory of configuration items, perfor...
• Why do you recommended that we test during the design phase?
  on Jan 10, 2013
  Because testing during the design phase can prevent defects later on. I recommend we verify three things...Verify the design is good, efficient, compact, testable and maintainable.Verify the design meets the requirements and is complete (specifies al...
• How can software QA processes be implemented without stifling productivity?
  on Jan 10, 2013
  Implement QA processes slowly over time. Use consensus to reach agreement on processes and adjust and experiment as an organization grows and matures. Productivity will be improved instead of stifled. Problem prevention will lessen the need for probl...
• What if the application has functionality that wasn't in the requirements?
  on Jan 10, 2013
  It may take serious effort to determine if an application has significant unexpected or hidden functionality, which it would indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the appl...
• What if the project isn't big enough to justify extensive testing?
  on Jan 10, 2013
  Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the considerations listed under "What if there isn't enough time for thorough testing?" do app...
• AGILE – A NEW APPROACH
  on Jan 10, 2013
  Iterative development, customer involvement, frequent delivery and other principles and values of the Agile Manifesto support the argument that agile is different from traditional heavyweight or plan-driven approaches. This section focuses on more de...

{pvComments::user_name}

{pvComments::date}

Delete 

{pvComments::comment}

Post a Comment