Software Testing Methodologies news, help and research - SearchSoftwareQuality.com

Software Testing Methodologies

  • static verification

    Static verification is the set of processes that analyzes code to ensure defined coding practices are being followed, without executing the application itself. 

  • load testing

    Load testing is the process of subjecting a computer, peripheral, server, network or application to a work level approaching the limits of its specifications... (Continued) 

  • context-driven testing

    Context-driven testing is a paradigm for developing and debugging computer software that takes into account the ways in which the programs will be used or are expected to be used in the real world... (Continued) 

  • black box

    A black box is any device whose workings are not understood by or accessible to its user. According to Edward Tenner, writing in The Washington Post, the first black box was a gun sight carried on World War II Flying Fortresses, with hidden component... 

  • Software Testing with Matt Sullivan and Scott Barber

    Matt Sullivan and Scott Barber discuss their presentation at STPCon 2011, which addressed software testing and software systems testing, among other topics. 

  • Carl Shaulis on Kanban at STPCon2011

    Carl Shaulis from HomeAway.com gave a presentation at STPCon 2011 on how testing can work in the world of kanban. Watch this video for a brief overview of the processes his company identified for expediting testing in an Agile setting using kanban. 

  • Tester's role in Agile environment with Rob Walsh

    Rob Walsh from Excalibur discusses the tester's role in the Agile environment at STPCon 2011. 

  • Sam Charrington, Appistry CloudIO

    Appistry CloudIO Manager is the enhanced management arm of CloudIO Platform v4.0 for public and private clouds. In this video, Sam Charrington talks about the new product's deployment and operational features. He is product management vice president ... 

  • Software Testing: Assessing risk and scope

    During a software project, there will always be more features to test than time you have to test them. So, how do you determine how much testing you'll do and how much risk is involved in setting limits? 

About Software Testing Methodologies

Software testing is used to determine whether a software application is producing the expected results. Depending on the methodology used and the type of testing that's being done, it can happen at any time in the software development process. Agile methodologies use test-driven development (TDD), in which tests are written before the code is written. Using this type of model, developers and testers are often paired and work together organizationally, throughout the software development lifecycle. However, in traditional methodologies such as a waterfall model, testing occurs after coding has been completed. Some methodologies further define phases of test, such as unit, integration, system, system integration, regression, and acceptance test.