The software project written in accordance with the object-oriented approach will have the graph models (GM), which differ from the traditional GM of a procedural program. The development of the project is based on another principle – the definition of the classes used in the program, the construction of a […] Read More
There are two types of classes in terms of their interaction with other classes: primitive classes; non-primitive classes. Primitive class can generate instances, and these instances can be used without having to create copies of any other classes, including that of this class. These objects are the simplest components of […] Read More
It is worth knowing that classes are tested using special drivers. Drivers are regarded as dummy modules that emulate behavior of software components that a module under test is dependent on. Therefore, they are mostly used in module testing. There are several ways to implement the test driver: The test […] Read More
Interaction diagram describes the sequence of events that occur with respect to a set of objects (a system of interconnected components). In addition, each system is considered to be open, i.e., this implies the existence of some system environment that the system interacts with. The environment can also be specified […] Read More
The interaction of objects is the process when one object (sender) requests another object (receiver) to perform one of the operations assigned to the receiver, and all kinds of data processing required to complete this request. In situations where testing of object interaction is based only on public operations specifications, […] Read More
The code coverage based methods are really beneficial because they ensure that a chosen test set will preserve a required degree of coverage for <P> elements with respect to a criterion of structural coverage C used to create the initial set of tests. This does not mean that if the […] Read More
Manual testing Manual testing consists in performing a documented procedure which describes a test execution method specifying the sequence of test run, and for each test – the list of parameters, which are input data, and a list of expected results at the output. Since the procedure is designed to […] Read More
Test development process based on the use of scenarios involves performing the following steps: Determination of the use case model, including the operational environment of the product and the “actors”. An actor can be a user, a different product, hardware component, and the like, namely everything that the product interacts […] Read More
A test cycle is a test execution cycle comprising phases 4 and 5 of the test process. The test cycle includes series of developed tests to be run on some uniquely determined slice of the system (the state of a developed system’s code). Typically, such slice of the system which […] Read More
The quality of a software product can be estimated by some set of characteristics that determine how “good” the product is according to all potentially interested parties. These parties are: Product customer. Sponsor. End user. Product developers. Product testers. Support engineers. Training Department. Sales Department, etc. Each of the participants […] Read More
System testing is qualitatively different from integration and unit testing types. System testing focuses on investigating the entire system and operates at the level of user interfaces, as opposed to the last phases of integration testing, which operates at the level of modules interfaces. Purposes of these testing levels are […] Read More
The process of building a test suite in the structured testing is determined by the principle used to design Program Graph Models (PGM). This affects many test paths and generation of tests corresponding to the relevant test paths. The first approach to software development is a procedural (modular) programming. Traditional […] Read More
Integration testing involves examining the system consisting of two or more modules. The main objective of integration testing is to find defects resulting from errors in the implementation and interpretation of interaction between the interfaces of the modules. Service quality assurance is meant to ensure quality, functionality and usability of […] Read More
Unit testing is a testing of the program at the level of individual modules, functions or classes. The purpose of unit testing is to identify module errors occurring in the implementation of the algorithms, as well as determine the degree of preparedness for the transition of the system to the […] Read More
Functional test is a key testing criterion for the software industry. It first of all provides the control over compliance with requirements established by the customer for the software product. As the requirements are formulated to the product as a whole, they reflect the interaction of the application under test […] Read More
The criterion should be sufficient, i.e., show when a finite set of tests is sufficient to test the program. The criterion must be complete, i.e., in case of an error there must be a test available among a plurality of tests to satisfy the criterion which discloses an error. The […] Read More
