Testing and Types of Testing Scenarios

A testing where the tester tries to break the software by randomly trying functionality of software. Testing that determines if software will be usable by people with disabilities. The following characteristics determines the testable software.

a. observability b. simplicity c. stability

Types of Testing Scenarios:

Alpha Testing is conducted at the developer sites and in a controlled environment by the end user of the software

Beta Testing is testing the application after the installation at the client place. Black-box testing attempts to find errors in 1. incorrect or missing functions 2. interface errors 3. performance errors

The testing technique that requires devising test cases to demonstrate that each program function is operational is called Black Box Testing

Component Testing is testing of individual software components (Unit Testing).

Compatibility testing is to test whether software is compatible with other elements of system.

Concurrency Testing: Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

Conformance Testing: The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.

Context Driven Testing: The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.

Data Driven Testing: Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.

Conversion Testing: Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

Dependency Testing: Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

Depth Testing: A test that exercises a feature of a product in full detail.

Dynamic Testing: Testing software through executing it.

Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.

End to End Testing: Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Exhaustive Testing: Testing which covers all combinations of input values and preconditions for an element of the software under test.

Gorilla Testing: Testing one particular module, functionality heavily.

Installation Testing: Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

Loop Testing: A white box testing technique that exercises program loops.

Mutation testing is a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources

Monkey Testing: Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

Path Testing: Testing in which all paths in the program source code are tested at least once.

Performance Testing: Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

Ramp Testing: Continuously raising an input signal until the system breaks down.

Recovery Testing: Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

Retesting- Again testing the functionality of the application.

Regression- Check that change in code have not effected the working functionality

Sanity Testing: Brief test of major functional elements of a piece of software to determine if its basically operational.

Scalability Testing: Performance testing focused on ensuring the application under test gracefully handles increases in work load.

Security Testing: Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

Stress testing is a form of testing that is used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results.

Smoke Testing: A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

Soak Testing: Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

User Acceptance Testing: User acceptance testing is determining if software is satisfactory to an end-user or customer.

Volume Testing: We can perform the Volume testing, where the system is subjected to large volume of data.

The testing technique that requires devising test cases to exercise the internal logic of a software module is called White Box Testing

Popular posts from this blog

Connecting Claude to Pega Infinity 25.1.3 via MCP — Step-by-Step

Build Pega Applications with GitHub Copilot CLI, Pega Infinity AI Plugin & MCP — Branch-Based Agentic Authoring

itextpdf API to generate PDF doc from an image file using Pega PE