Your are here: Home // // Software Testing: Part 1

Software Testing: Part 1

The other day a friend asked me what the tester. In other words, what is software testing? What is the bug? What are the key terms associated with the test? To resolve these questions in a world of humility is an attempt to begin to test the novice.

Software analysis and software testing is the process of detecting faults. It is faulty and they are art (pun intended) is to be resolved as much as possible to make sure is that Defects (bugs) or functional requirements specification, is irrelevant. It is not described in the product requirements and expectations of our customers can not be equal, but the assumption is something.

Will participate in the testing process, in order to develop a test plan that describes the test administrator and the project manager will be. This testing strategy, such as the default document type budget, quality standards and testing, resource and test test test test components as a graph describes a list of risk

Exercise a particular program path or test inputs, execution conditions, and expected results developed for a specific purpose, such as to comply with specific requirements to ensure that, by default, lead / senior test engineers to test is a set of test cases to that can be developed.

Kind of test types:

Production processes, requirements, functional specification, high-level architecture and design documents, static detection of defects in the early stages of product testing is used to verify that the static test code, all the work from the point of view of the process is one of the most effective ways to .

Dynamic tests Dynamic tests have been run, and all of the features of the user interface module, execute, compare the expected behavior of the product consists of.

Black-box testing. The internal structure and program of operational and business requirements, without the knowledge of the source code of the function start and test the software. As the product of the tester to test the market and end-users to work during operation. All features and functions of regulatory compliance requirements are two ways to check the correct operation.

White-box testing (glass-box testing). Code to access the development and execution of test cases that are used to understand the source code of their testers. The architecture of the system is tested. It is a building system design and programming test. White-box testing is applied to the application is common, but completely, components, modules and assembly procedures, and functions of each child is required to determine

Unit testing. This level of testing is usually performed by software developers test the other modules in the system is to perform. In a particular part of the test code (classes) can be

Integration testing. They test the various components of the application (in the form of their integration) together to work well. In addition, the application of a large system, the interactions between these types of tests can be found. This test is known as the cross-product testing. After performing unit and functional testing was performed in general.

Check the operation of the entire system, the test system to indicate the type of test. It generally functions of the system, as well as non-functional requirements are associated with the test.

Program and its features and specifications of the functional test requirements, and the process is trying to find a discrepancy between. Its goal is

1. Define and document defects in software products

Two. Software Requirements Specification (SRS) and to ensure that it meets the requirements defined in the software documentation.

Three. About the possibility of the target software product delivered to the customer to make a decision, the decision shall be recorded in the test report.

filed under:

Leave a reply

Copyright © 2013 Computers & Technology.
Designed by imesh maduvantha.