Software Testing Practices, Test Methodologies and Test Competency Services


Welcome to the world of Software Testing & Best Test Practices.

All you wanted to know about Software Testing, Test Practices, Test Methodologies and building the Test Competency Services !!


Showing posts with label What is ...???. Show all posts
Showing posts with label What is ...???. Show all posts

Monday, May 19, 2008

Software Testing

Software testing is a process used to identify the correctness, completeness and quality of developed computer software. Actually, testing can never establish the correctness of computer software, as this can only be done by formal verification (and only when there is no mistake in the formal verification process). It can be used to show the presence of defects, but never their absence. Software testing is a trade-off between budget, time and quality.

Testing is a process of technical investigation that is intended to reveal quality-related information about the product. It is oriented to detection.

The goal of the testing activity is to find as many errors as possible before the user of the software finds them. We can use testing to determine whether a program component meets its requirements. To accomplish its primary goal (finding errors) or any of its secondary purposes (meeting requirements), software testing must be applied in a systematic fashion.

An important point is that software testing should be distinguished from the separate discipline of software quality assurance, which encompasses all business process areas, not just testing.

Testing in other words, is nothing but CRITICISM or COMPARISION. Here comparison means comparing the actual value with expected one.There are many approaches to software testing, but effective testing of complex products is essentially a process of investigation, not merely a matter of creating and following rote procedure. One definition of testing is "the process of questioning a product in order to evaluate it", where the "questions" are things the tester tries to do with the product, and the product answers with its behavior in reaction to the probing of the tester. Although most of the intellectual processes of testing are nearly identical to that of review or inspection, the word testing is connoted to mean the dynamic analysis of the product—putting the product through its paces.

The quality of the application can and normally does vary widely from system to system but some of the common quality attributes include reliability, stability, portability, maintainability and usability.No matter the program, the beta testers find something that they feel needs to get fixed before the disc goes gold. Alas, there's never time to fix all the bugs, and the program gets shipped, warts and all. In a triage scenario, veteran software testers know that it's inevitable that something has to slip through. They just hope that the most heinous nasties are squashed before the final release candidate.

Once the program ships, it doesn't take long for the user base to find the bugs. The unwitting and most vocal can tend to blame the Quality Assurance team and the beta software testing effort. "Why didn't you find and fix this?" they ask, without having the insight to consider the forces that come to bear.When it's gotta ship, it's gotta ship. Ready-or-not, here it goes ...By the time the shrink wrap hits the street, those last minute bugs may actually be fixed ... but the fixes won't be on the CD that shipped in the first boxes. They may be slipstreamed into subsequent releases, with patches made available over the Internet.As a user (and a grizzled software tester), I've learned not to immediately jump on and install a release the day it comes out, when possible. I usually wait for the first round of fixes to ship before I roll the dice...

Requirements Analysis

After the project has been acquired and the contract has been signed, one of the first functions of the Analysis team is the process of Requirement Definition. Lets explore this now :)

Requirements analysis encompasses those tasks that go into determining the requirements of a new or altered system, taking account of the possibly conflicting requirements of the various stakeholders, such as users. Requirements analysis is the stage where client requirements are gathered & is critical to the success of a project. This is done on the basis of information provided by the client in the form of documents, existing systems and process specs, on-site analysis interviews with end-users, market research and competitor analysis. This stage has the following steps:

Requirements Elicitation: It is the process of gathering customer needs. This involves asking the customers, users and others about the objectives of the system, what is to be accomplished, how the system fits into the business needs and finally how the system will be used.


Analyzing requirements: Once the requirements have been gathered, they become the basis for “Requirements Analysis”. Analysis categorizes requirements and organizes them into related subsets, explores each requirement in relationship to others, examines requirement for consistency, omissions and ambiguity, and prioritizes requirements based on the needs of the customer. Rough estimates of development are made and used to assess the impact of each requirement on project cost and delivery time. Using an iterative approach, requirements are eliminated, combined and modified so that each party achieves some measure of satisfaction. The requirements are used to generate Business Process Flows, Use Cases Modeling and Data Flow diagrams which facilitates a clearer understanding of the requirements and its solution, for both the customer and the developer.

Requirements Specification: It is the process of describing what a system will do. It involves scoping the requirements so that it meets the customer’s vision. Requirements Specification serves as a foundation software, hardware and database design. It describes the function (Functional and Non-Functional) and performance of the system and the constraints that will govern its development. It specifies the inputs and also describes the outputs. These specifications need to be

(i) Complete, Comprehensive, Consistent, Modifiable, Measurable
(ii) Unambiguous ,Testable, Writable, Implementable

Requirements Management: It is the process that helps the project team identify, control, and track changes to the requirements at any time as the project proceeds. Requirements Verification, Validation and Traceability examines the specification to ensure that all system requirements have been stated unambiguously and that inconsistencies, omissions and errors have been detected and corrected.
Recording requirements: Requirements may be documented in various forms, such as natural-language documents, use cases, user stories, or process specifications.