Skip to main content

Task 3

 


1) Difference between system testing, integration testing and End to End  testing?

system testing :

System testing done by a professional testing agent on the completed software product before it is introduced to the market.

It is a black box technique

Different Types of System Testing:

usability testing
regression testing
load testing 
recovery testing 


Integration testing:

Integration Testing

INTEGRATION TESTING is a level of software testing where individual units / components are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. 

It is a white box testing technique.


End to End testing:

It test from beginning to ending 

End-to-End testing is also called Chain Testing.

End to End Testing is usually executed after functional and system testing

The following diagram gives an overview of the End to End testing process.

 END-To-END Testing Guide: Complete E2E Testing Tutorial


2)  Difference between regression, sanity and smoke tests?



Smoke testing :

The main intent of smoke testing is not to perform deep testing but to verify that the core or main functionalities of the program or the software are working fine.

Smoke testing is also called as Build Verification Test.

When to perform Smoke Testing

  • when the build has new changes made by the developers.
  • When a new module is added to the existing functionality.
Sanity testing :

Sanity testing is a kind of testing performed to check whether a software product is working correctly when a new module or functionality gets implemented to an existing product.

Why perform Sanity Testing:
  • To ensure that the introduced changes do not affect other existing functionalities of the product.
  • To decide further testing can be carried forward or not.

Regression Testing:

Tests whether a newly added functionality has affected the existing functionality.

When to perform Regression Testing

  • After some new features are added to the application
  • After some bug fixes are incorporated into the build

3)  Difference between Alpha and Beta tests?


Alpha Testing

Alpha Testing is a type of acceptance testing; performed to identify all possible issues and bugs before releasing the final product to the end users.


Alpha testing involves both white box and black box testing.


Alpha testing is to ensure the quality of the product before moving to Beta testing.


Alpha Testing performed by developer’s




Alpha Testing Vs Beta Testing

Beta Testing:

Beta testing is performed by Clients or End Users who are not employees of the organization

Reliability, Security, Robustness are checked during Beta Testing 

Beta testing also concentrates on the quality of the product

Beta Testing typically uses black box testing 





4) Difference between black box and white box testing?


Black box testing :

  • Does not require programming knowledge.
  • focuses on the behaviour of the software.
  • Testing done without the knowledge of the internal structure of the program or the application.
  • Black Box testing is a not time-consuming process

White box testing:

  • main goal to test the internal operation of the system.
  • Requires programming knowledge.
  • testing is done with knowledge of the internal structure of program.
  • white box testing is a time consuming process.



5)  Explain API testing with an example?



How An API Works





 Application Programming Interface acts as an interface between two software applications and allows the two software applications to communicate with each other.

 API is a collection of software functions that can be executed by another software program.


for example :

Assume an API as a Waiter at a Restaurant.


 restaurant ==> we order food from  menu==>  waiter gives my order to cook ==>Once the food  is ready==>the waiter picks up  food from the kitchen and serves it to my table.


so, the waiter’s role is similar to an API. As a waiter, the API takes a request from a source, takes that request to the database, fetches the requested data from the database, and returns a response to the source.



6) What are the different types of non-functional testing?




Non-functional testing


1. Recovery Testing

Recovery testing checks the system’s ability to recover from different failure situation. I

2. Performance Testing

 it checks if the system meets the expected response time.

3. Usability Testing

It usually takes place at the integration level.

4. Efficiency Testing

Efficiency testing is a kind of performance testing. It checks if the system utilizes its resources efficiently.

5. Maintainability Testing

 ensures the capability of the system for further upgradations and to meet growing user needs.

6. Portability Testing

Portability testing ensures that the system works well in different environments without affecting its functionality.

7. Reliability testing

Reliability testing checks if the system works effectively for a longer period of time. 



7) What is User Acceptance Testing and who does UAT?


UAT is a type of testing performed by the end user to provide approval for production release.

It is a kind of black box testing where two or more end users will be involved.

The client and end users performs UAT.




8) What is compatibility testing and how they are performed?

Compatibility Testing is a type of Software testing to check whether the software is capable of running on different hardware, operating systems, applications, network environments.
  • Compatibility testing is to check the application working in the same way for all platform













Comments