You Are Browsing ‘Software Testing Blogs’ Category

Posted on Aug 9 2009 - 2:25pm by Raj
#0

Performance testingNot all software systems have specifications on performance explicitly. But every system will have implicit performance requirements. The software should not take infinite time or infinite resource to execute. “Performance bugs” sometimes are used to refer to those design problems in software that cause the system performance to degrade. Performance has always been a great concern and a driving force of computer evolution. Performance evaluation of a software system usually includes: resource usage,...

Posted on Aug 6 2009 - 6:30pm by Raj
#0

Black-box testing The black-box approach is a testing method in which test data are derived from the specified functional requirements without regard to the final program structure. It is also termed data-driven, input/output driven, or requirements-based testing. Because only the functionality of the software module is of concern, black-box testing also mainly refers to functional testing – a testing method emphasized on executing the functions and examination of their input and output data. The tester treats the software under...

Qualification testing Qualification testing checks the system behavior against the customer’s requirements, however these may have been expressed; the customers undertake, or specify, typical tasks to check that their requirements have been met or that the organization has identified these for the target market for the software. This testing activity may or may not involve the developers of the system. Installation testing Usually after completion of software and acceptance testing, the software can be verified upon installation...

Posted on Aug 4 2009 - 6:30pm by Raj
#0

Objectives of TestingTesting is conducted in view of a specific objective, which is stated more or less explicitly, and with varying degrees of precision. Stating the objective in precise, quantitative terms allows control to be established over the test process.Testing can be aimed at verifying different properties. Test cases can be designed to check that the functional specifications are correctly implemented, which is variously referred to in the literature as conformance testing, correctness testing, or functional testing. However,...

Posted on Aug 3 2009 - 6:30pm by Raj
#0

Test Levels Software testing is usually performed at different levels along the development and maintenance processes. That is to say, the target of the test can vary: a single module, a group of such modules (related by purpose, use, behavior, or structure), or a whole system. Three big test stages can be conceptually distinguished, namely Unit, Integration, and System. No process model is implied, nor are any of those three stages assumed to have greater importance than the other two. Unit testing Unit testing verifies the functioning...

Posted on Aug 2 2009 - 6:30pm by Raj
#0

For reliability estimationSoftware reliability has important relations with many aspects of software, including the structure, and the amount of testing it has been subjected to. Based on an operational profile (an estimate of the relative frequency of use of various inputs to the program), testing can serve as a statistical sampling method to gain failure data for reliability estimation. Software testing is not mature. It still remains an art, because we still cannot make it a science. We are still using the same testing techniques invented...

Summary: This module provides an introduction to software testing. Topics covered include basic definitions of testing, validation and verification; the levels of testing from unit testing through to acceptance testing; the relationship with requirements and design specifications; and test documentation. IntroductionSoftware Testing is the process of executing a program...

Posted on Aug 1 2009 - 2:26pm by Raj
#0

Security testing Software quality, reliability and security are tightly coupled. Flaws in software can be exploited by intruders to open security holes. With the development of the Internet, software security problems are becoming even more severe. Many critical software applications and services have integrated security measures against malicious attacks. The purpose of security testing of these systems include identifying and removing software flaws that may potentially lead to security violations, and validating the effectiveness of...

Written by:Tatyana Kit, QA Specialist; Natalya Novotnaya, Team Leader of Testing Team, ApriorIT Inc. In this article we will talk about the file systems and files, but the most attention will be focused on the moments of testing of software which works with NTFS and FAT. At the end we will give our check list for testing of software, working with the FAT and NTFS...

Posted on Jul 7 2009 - 9:10am by Raj
#0

Written by: Elena Osadchaya, Junior QA Specialist of  QA Team, Apriorit Inc . Introduction This article will be useful for those specialists who are not indifferent to the GUI problems and are interested in getting good GUI. It’s hard to give clear and full definition for the good GUI. So let’s at the moment agree that we’ll understand good GUI as the GUI which helps user to perform his tasks effectively and provide software product with commercial success. Further in this article we’ll extend this...