Tester's dictionary [S-Z] | Testing terms Glossary

Safety Testing 

Software System Safety optimizes safety of the system in development, design, use and maintenance of software systems along with integration of hardware system in operational environment.

Sanity Testing

Sanity Testing is a process, when there are minor changes in the code and then testing is done to check for the bug fixed in the application. If it fails the test then build is rejected to save the time or costs involved in more rigorous testing.

The objective is "not" to verify thoroughly the new features, but to check that the developer has applied some rationality (sanity) while developing the software.  

Scalability Testing 

It is a type of software testing which testthe ability of a system, aprocess,a networkto continue to function well, when there is change in size or volume due growing need or demand. 

Scenario Testing 

Scenario testing is done to ensure the end to end functionality of software is working as expected and all the business process flows of the software is working fine.

Schedule 

It is directly correlated to the size of the project, costs and efforts involved.

Script 

A script is a set of instruction or command of a certain program or scripting engine used to evaluate and automate the process on the system it is been executed.

Security Testing 

To uncover vulnerability of the system and to determine the data and resource to be protected from possible intruders we go with Security Testing.

Simulation 

Simulation is the imitating the operation of a real-world process or system over time. Theprocess of simulating something first requires that a model be developed and this model represents the keybehaviors/functions or characteristics of the selected physical or abstract system or process. The model represents the system itself, whereas the simulation represents the operation of the system over time.

Smoke Testing 

Smoke testing is the initial testing process exercised to verify whether the software under test is stable/ready for further testing.

Soak Testing 

Soak Testing is the part of Performance Testing, which involves testing a system with expressive load extended over alarge period of time, to verify how the system and product react under repeated use. 

Software requirement specification 

Software requirements specification captures system behavior as opposed to non-functional requirements specifications which define attribute as not behavior. This 'functionality' refers to tasks, services or functions the user performs using the systems in question.

Stability Testing 

Stability testing verifies to see if the software can continuously function well in or above an acceptable period range.

State Transition 

State transition testing is used for systems where some aspect of the software system can be described in as ‘finite state machines’. This means that the system can be in a finite number of different stages, and the transitions from one stage to another are defined by the rules of the ‘machines’.

Static Testing 

Static testing is the form of software testing where you do not execute the code being examined. This technique can be called as non-execution technique method. It is primarily syntax checking of the code or reviewing the code, design documents,requirements documentsetc. to find errors.

Statistical Testing 

Statistical Testing makes use of statistical methods or tools to check the reliability of the program. Statistical testing focuses mainly on how faulty/defective programs can affect its operating conditions.

Storage Testing 

Storage testing is a part of the software development test cycle that ensures the software program stores data files in correct directories or destination and that it reserves more space to prevent failureof a system.

Stress Testing 

Stress testing is the process of determining the credibility of a computer, program, network or device to maintain a certain level of effectiveness under unfavorable conditions. These processes involve quantitative tests done in lab, such as measuring the frequency of errors or system crashes.

Structural Testing 

The structural testing is the testing of the structure of the system or components. Structural testing is often referred as ‘glass box’ or ‘white box’ or ‘clear-box testing’ because in structural testing user are interested in what is happening ‘inside the system/application’.

Structured Walkthrough 

It is a static testing technique performed in an organized manner between a group of peers to discuss and reviewthe technical aspects of software development. The main objective is to find defects in order to improve the quality of the product.

Stub 

A stub is used during Top-down integration testing method, in order to simulate or replicate the behavior of the lower-level modules that are not yet to be integrated or developed. Stubs are set of code that act as temporary replacement for a called module and give the same output as that of actual product.

Symbolic Execution 

Symbolic execution (also known as symbolic evaluation) is a means of analyzing a program to determine and check what inputs cause each part of a program to execute. An interpreter follows the program assuming symbolic values for inputs rather than obtaining actual inputs as normal executions of the programs would a case of abstract interpretation.

Syntax Testing 

Syntax Testing uses a model of the formally-defined syntax’s of the inputs to a component. The syntax’s is represented as a number of rules each of which define the possible means of productions of a symbol in terms ofiterations, sequencesor selections between other symbols.

System Integration Testing 

System integration testing is high-level software testing method in which tester verify that all related system maintains data integrity’s and can operate in coordination’s with all other systems in the same environment. This testing process ensures that all subcomponents are integrated successfully to provide results output expected.

System Testing 

System testing is actually a series of different tests whose main purpose is to exercise the full computer based systems. System testing’s falls under the black box testing method usually carried out by team which is independent of the development team. It also involves both

functional and Non-Functional testing.

System under Test 

System under test refers to systems that are being tested used for correct operation. A special case of a software system is an application which and when tested is called an application under test.