Car Chargers at Best prices

 

Software Testing | Basics - 1

 Software testing can be stated as the process of verifying and validating that software or application is bug-free, meets the technical requirements as guided by its design and development, and meets the user requirements effectively and efficiently with handling all the exceptional and boundary cases. 

The process of software testing aims not only at finding faults in the existing software but also at finding measures to improve the software in terms of efficiency, accuracy, and usability. It mainly aims at measuring the specification, functionality, and performance of a software program or application. 

Software testing can be divided into two steps: 

1. Verification: it refers to the set of tasks that ensure that software correctly implements a specific function. 

2. Validation: it refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements. 

Verification: “Are we building the product right?” 

Validation: “Are we building the right product?” 

What are different types of software testing? 

Software Testing can be broadly classified into two types: 

1. Manual Testing: Manual testing includes testing software manually, i.e., without using any automated tool or any script. In this type, the tester takes over the role of an end-user and tests the software to identify any unexpected behavior or bug. There are different stages for manual testing such as unit testing, integration testing, system testing, and user acceptance testing. 

Testers use test plans, test cases, or test scenarios to test software to ensure the completeness of testing. Manual testing also includes exploratory testing, as testers explore the software to identify errors in it. 

2. Automation Testing: Automation testing, which is also known as Test Automation, is when the tester writes scripts and uses another software to test the product. This process involves the automation of a manual process. Automation Testing is used to re-run the test scenarios that were performed manually, quickly, and repeatedly. 

Apart from regression testing, automation testing is also used to test the application from a load, performance, and stress point of view. It increases the test coverage, improves accuracy, and saves time and money in comparison to manual testing. 

What are the different techniques of Software Testing? 

Software techniques can be majorly classified into two categories: 

1. Black Box Testing: The technique of testing in which the tester doesn’t have access to the source code of the software and is conducted at the software interface without concern with the internal logical structure of the software is known as black-box testing. 

2. White-Box Testing: The technique of testing in which the tester is aware of the internal workings of the product, has access to its source code, and is conducted by making sure that all internal operations are performed according to the specifications is known as white box testing. 

What are different levels of software testing? 

Software level testing can be majorly classified into 4 levels: 

1. Unit Testing: A level of the software testing process where individual units/components of a software/system are tested. The purpose is to validate that each unit of the software performs as designed. 

2. Integration Testing: A level of the software testing process where individual units are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. 

3. System Testing: A level of the software testing process where a complete, integrated system/software is tested. The purpose of this test is to evaluate the system’s compliance with the specified requirements. 

4. Acceptance Testing: A level of the software testing process where a system is tested for acceptability. The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery. 

Note: Software testing is a very broad and vast topic and is considered to be an integral and very important part of software development and hence should be given its due importance. 

Software Testing and Types - 2

 

Types of Software Testing

Introduction:-

Testing is the process of executing a program with the aim of finding errors. To make our software perform well it should be error-free. If testing is done successfully it will remove all the errors from the software. 

 

Principles of Testing:-

(i) All the test should meet the customer requirements 

(ii) To make our software testing should be performed by a third party 

(iii) Exhaustive testing is not possible. As we need the optimal amount of testing based on the risk assessment of the application. 

(iv) All the test to be conducted should be planned before implementing it 

(v) It follows the Pareto rule(80/20 rule) which states that 80% of errors come from 20% of program components. 

(vi) Start testing with small parts and extend it to large parts. 

 

Types of Testing:-

 

1. Unit Testing

It focuses on the smallest unit of software design. In this, we test an individual unit or group of interrelated units. It is often done by the programmer by using sample input and observing its corresponding outputs. 

Example: 

 

a) In a program we are checking if loop, method or 
   function is working fine
b) Misunderstood or incorrect, arithmetic precedence.
c) Incorrect initialization

 

2. Integration Testing

The objective is to take unit tested components and build a program structure that has been dictated by design. Integration testing is testing in which a group of components is combined to produce output. 

Integration testing is of four types: (i) Top-down (ii) Bottom-up (iii) Sandwich (iv) Big-Bang 

Example 

 

(a) Black Box testing:- It is used for validation. 
In this we ignore internal working mechanism and 
focuse on what is the output?.

(b) White Box testing:- It is used for verification. 
In this we focus on internal mechanism i.e.
how the output is achieved?

 

3. Regression Testing

Every time a new module is added leads to changes in the program. This type of testing makes sure that the whole component works properly even after adding components to the complete program. 

Example 

 

In school record suppose we have module staff, students 
and finance combining these modules and checking if on 
integration these module works fine is regression testing

 

4. Smoke Testing

This test is done to make sure that software under testing is ready or stable for further testing 

It is called a smoke test as the testing an initial pass is done to check if it did not catch the fire or smoke in the initial switch on. 

Example: 

 

If project has 2 modules so before going to module 
make sure that module 1 works properly

 

5. Alpha Testing

This is a type of validation testing. It is a type of acceptance testing which is done before the product is released to customers. It is typically done by QA people. 

Example: 

 

When software testing is performed internally within
the organization

 

6. Beta Testing

The beta test is conducted at one or more customer sites by the end-user of the software. This version is released for a limited number of users for testing in a real-time environment 

Example: 

 

When software testing is performed for the limited
number of people

 

7. System Testing

This software is tested such that it works fine for the different operating systems. It is covered under the black box testing technique. In this, we just focus on the required input and output without focusing on internal working. 

In this, we have security testing, recovery testing, stress testing, and performance testing 

Example: 

 

This include functional as well as non functional 
testing

 

8. Stress Testing

In this, we give unfavorable conditions to the system and check how they perform in those conditions. 

Example: 

 

(a) Test cases that require maximum memory or other
    resources are executed
(b) Test cases that may cause thrashing in a virtual 
    operating system
(c) Test cases that may cause excessive disk requirement

 

9. Performance Testing

It is designed to test the run-time performance of software within the context of an integrated system. It is used to test the speed and effectiveness of the program. It is also called load testing. In it we check, what is the performance of the system in the given load.

Example: 

 

Checking number of processor cycles.

 

10. Object-Oriented Testing

This testing is a combination of various testing techniques that help to verify and validate object-oriented software. This testing is done in the following manner: 

• Testing of Requirements,
• Design and Analysis of Testing,
• Testing of Code,
• Integration testing,
• System testing,
• User Testing.