Levels of Testing

Levels of Testing

1. Unit Testing.
   • Unit Testing is primarily carried out by the developers themselves.
   • Deals functional correctness and the completeness of individual program units.
   • White box testing methods are employed
   
   
   
2. Integration Testing.
   • Integration Testing: Deals with testing when several program units are integrated.
     
   • Regression testing : Change of behavior due to modification or addition is called ‘Regression’. Used to bring changes from worst to least.
   • Incremental Integration Testing : Checks out for bugs which encounter when a module has been integrated to the existing.
   • Smoke Testing : It is the battery of test which checks the basic functionality of program. If fails then the program is not sent for further testing.
     
   
   
   
3. System Testing.
   • System Testing - Deals with testing the whole program system for its intended purpose.
   • Recovery testing : System is forced to fail and is checked out how well the system recovers the failure.
   • Security Testing : Checks the capability of system to defend itself from hostile attack on programs and data.
   • Load & Stress Testing : The system is tested for max load and extreme stress points are figured out.
   • Performance Testing : Used to determine the processing speed.
   • Installation Testing : Installation & uninstallation is checked out in the target platform.
   
   
   
4. Acceptance Testing.
   • UAT ensures that the project satisfies the customer requirements.
   • Alpha Testing : It is the test done by the client at the developer’s site.
   • Beta Testing : This is the test done by the end-users at the client’s site.
   • Long Term Testing : Checks out for faults occurrence in a long term usage of the product.
   • Compatibility Testing : Determines how well the product is substantial to product transition.

Interview Questions..

What is the testing that a tester performs at the end of unit testing?

Integration Testing is performed after unit testing and it tests the integrity of the modules in the application.

what is positive and negative testing with example?

Positive Testing: Testing the build with permitted
values,i.e values as per the requirement specification.

Negative Testing: Testing the build with wrong inputs,i.e
non permitted values as per the requirement specification.

What is Compatibility Testing?

In Compatibility testing we will test the application with wide variety of OSs, browsers, databases, servers, clients,
and hardware as per the client requirement/specification.

what are your strengths?(in testing)

Test to break attitude.
Motivation towards quality.
Continuous process improvement.
Good test case developement and testscript execution skills.
Every tester thinks always negative sense in that situation.

Difference between Test Plan & Test Strategy?

1. Test Plann : The Test plan is the document where it contains the elements like

1.Items to be tested
2.Items need not be tested
3.test Schedule,test case design and execution
4.Roles and responsibilities of the test team
5.Defect Management

2. Test Strategy : The approach of test execution is called test strategy .

what is validation and verification of a bug?

Validation: Does the system satisfy the requirements of the software?

Verification: Are we developing the system correctly?

After receiving the bug as fixed , what types of tests we will continue...

We will go for both Retesting and Regression testing.

In Retesting we are going to check whether the bug is fixed or not

In Regression testing we are going to check due to the fixation we are getting any problems due to the fixation ..

Functional & Non Functional Testing

Functional Testing : Testing the application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.

Functional Testing covers :

Unit Testing
Smoke testing / Sanity testing
Integration Testing (Top Down,Bottom up Testing)
Interface & Usability Testing
System Testing
Regression Testing
Pre User Acceptance Testing(Alpha & Beta)
User Acceptance Testing
White Box & Black Box Testing
Globalization & LocalizationTesting

Non-Functional Testing : Testing the application against client's and performance requirement. Non-Functioning testing is done based on the requirements and test scenarios defined by the client.

Non-Functional Testing covers :

Load and Performance Testing
Ergonomics Testing
Stress & Volume Testing
Compatibility & Migration Testing
Data Conversion Testing
Security / Penetration Testing
Operational Readiness Testing
Installation Testing
Security Testing (ApplicationSecurity, Network Security, System Security)