What is Software Testing ?

What is Software Testing ?

What is software Testing ? 

Software testing is the process of finding errors in a product, whether it be a mobile or web application. Errors include bugs in the code, missing requirements, glitches, and more. Software testing can also determine whether the outcome when engaging with the application differs from the expectation.

Different Types of Testing?

Let us explore some of the most common testing types:

1.Accessibility testing

2.Acceptance testing

3.Black box testing

4.End to end testing

5.Functional testing

6.Interactive testing

7.Integration testing

8.Load testing

9.Non functional testing

10.Performance testing

11.Regression testing

12.Sanity testing

13.Security testing

14.Single user performance testing

15.Smoke testing

16.Stress testing

17.Unit testing

18.White-box testing

This is just a sample of different methods of testing, but there are many others. Many of these types of testing can be done manually — or they can be automated.

1. Accessibility Testing 

Accessibility testing is the practice of ensuring your mobile and web apps are working and usable for users without and with disabilities such as vision impairment, hearing disabilities, and other physical or cognitive conditions. 

2. Acceptance Testing 

Acceptance testing ensures that the end-user (customers) can achieve the goals set in the business requirements, which determines whether the software is acceptable for delivery or not. It is also known as user acceptance testing (UAT).  

3. Black Box Testing : It is used for validation. In this, we ignore internal working mechanisms and focus on what is the output?.

4. End to End Testing 

End to end testing is a technique that tests the application’s workflow from beginning to end to make sure everything functions as expected. 

5. Functional Testing 

Functional testing checks an application, website, or system to ensure it’s doing exactly what it’s supposed to be doing. 

6. Interactive Testing 

Also known as manual testing, interactive testing enables testers to create and facilitate manual tests for those who do not use automation and collect results from external tests.  

7. Integration Testing 

It is performed in an integrated hardware and software environment to ensure that the entire system functions properly.

8. Load Testing 

This type of non-functional software testing process determines how the software application behaves while being accessed by multiple users simultaneously. 

9. Non Functional Testing 

Non functional testing verifies the readiness of a system according to nonfunctional parameters (performance, accessibility, UX, etc.) which are never addressed by functional testing. 

10. Performance Testing 

Performance testing examines the speed, stability, reliability, scalability, and resource usage of a software application under a specified workload. 

11. Regression Testing 

Software regression testing is performed to determine if code modifications break an application or consume resources. 

12. Sanity Testing 

Performed after bug fixes, sanity testing determines that the bugs are fixed and that no further issues are introduced to these changes.  

13. Security Testing 

Security testing unveils the vulnerabilities of the system to ensure that the software system and application are free from any threats or risks.

14. Single User Performance Testing 

Single user performance testing checks that the application under test performs fine according to specified threshold without any system load.

15. Smoke Testing 

validates the stability of a software application, it is performed on the initial software build to ensure that the critical functions of the program are working. 

16. Stress Testing 

Activity that tests beyond normal operational capacity to test the results. 

17. Unit Testing 

checking small pieces of code to ensure that the individual parts of a program work properly on their own, speeding up testing strategies and reducing wasted tests. 

18. White Box Testing 

It is used for verification. In this, we focus on internal mechanisms i.e. how the output is achieved?



To view or add a comment, sign in

Others also viewed

Explore content categories