Difference between Unit testing and functional testing

Unit testing:

Unit testing means It tested single peace of code or module which was changed by deverloper.

This test is conducted or white box test engineer.white-box test engineer should have internal skills

Functionality Testing:

Functionality testing Means it tested all the module and functionality is working or not according to the customer requirement . this is called Functionality testing 

Difference between Usability & User Interface testing

User Interface testing

1) verify the perticular module communicating properly among another as per the specification. Its mainly used for user interface of GUI application.
2) User Interface Testing comes under  "Functional Testing".

Usability Testing 

1) verifies is there any pain to use particular option for the user .
2) Usability Testing is part of System Testing.

Examples:

User Interface Testing:  Verifying the colors, graphics, allignments, sizes of Screens or forms

Usability Testing: Let us take one drop down which has 500 values in it. While using it it is very hard to select particular record out of 500 values in that drop down. So instead of using drop down field , as a tester we need to ask developer to use text box like in google site. If you enter first 3 or 4 letters autocatically it displays all the values which has these letters as first three letters.

Difference between Regression testing and Re-Testing

Regression Testing:

Regression testing means to re-execute the pass test cases again of older version of build on the modified version of build. to ensure that there is no any side effect of this change on another module or other part of the application.

Testing conducted to ensure application doesn't break post progression testing.

Re-Testing

Re-Testing: After a defect is detected and fixed, the software should be retested to confirm that the original defect has been successfully removed. This is called Confirmation Testing or Re-Testing

Regression testing:  Testing your software application when it undergoes a code change to ensure that the new code has not affected other parts of the software.


Re-Testing : The defect logged by tester while testing application and same fixed by developer. In Retesting we check same defect whether fixed or not using steps to reproduce mentioned in the defect.

Regression testing : we check same defect fixes are not impacted other unchanged part of the application, not breaking the functionality working previously and break due to fixing defect.

TEST EXECUTION

Level 0- Sanity, Smoke testing
Level 1- Real time testing
Level 2- Retesting and Regression testing
Level 3-Final testing
Objective of sanity and smoke testing is same as we can proceed for real time testing means all functional and non functional testing(system testing) based on priority. if bug is occured and reported then after modification we have to re execute the fail test cases(retesting, may be pass now) and pass test cases(Regression to ensure no side effect on another part).

Difference between Smoke Testing and sanity testing :

1) Smoke : this is done to verify to check if we are in a position to start Testing:

1. Able to  Access to the Applications

2. Login to the application

3. Click on links to verify that we are not getting any errors/page crashes.


Sanity:

This is performed to check if the application performing the required functions correctly

like adding A+B should be C,  all the major links are working perfectly as per the requirement.that means if your scientific calculator gives the result of 2 + 2 =5! Then, there is no point testing the advanced functionalities like sin 30 + cos 50.


2) Smoke testing and sanity testing is performed after software build and before any functional testing, Regression testing and any other testing executed on the software build.


3) Smoke test is testing whether the build is working fine or not

whereas the Sanity is testing whether major functionalities are working fine or not before test execution...


4) Smoke can be done by testers and developers and Sanity by Testers.


5) Example for Smoke testing:
Taking a test ride to test the basic features (functionalities) of the bike can be compared to Smoke testing a product

Example for Sanity testing:
Testing the bike performance in detail after bringing it home can be compared to Sanity testing a product

Functional Testing Type

What is Functional Testing?

Functional Testing is the type of testing done against the business requirements of application. It is a black box type of testing.


It involves the complete integration system to evaluate the system’s compliance with its specified requirements. Based on the functional specification document this type of testing is to be carried out. In actual testing, testers need to verify a specific action or function of the code. For functional testing either manual testing or automation tools can be used but functionality testing would be easier using manual testing only. Prior to non Functional testing the Functional testing would be executed first.

Five steps need to be keeping in mind in the Functional testing:

   1. Preparation of test data based on the specifications of functions
   2. Business requirements are the inputs to functional testing
   3. Based on functional specifications find out of output of the functions
   4. The execution of test cases
   5. Observe the actual and expected outputs


In the types of functional testing following testing types should be cover:

    * Unit Testing
    * Smoke testing
    * Sanity testing
    * Integration Testing
    * Interface Testing
    * System Testing
    * Regression Testing
    * UAT

System Testing

System testing is the testing of a complete and fully integrated software product.

System testing is nothing but testing the whole application
which was integrated all the modules. The system testing have two types:

1.Fuctionality testing'
2.Non-functionality testing

System testing falls under the black box testing category of software testing.

What do you verify in System Testing ?

-> Testing the fully integrated software and verfiy the how componanet interact with one another and with the system as whole. This is also called End to End testing.

-> Verify thorough testing of every input in the application to check for desired outputs.

-> Testing with hardware and software requirements according to that project  requirements.

End to End Testing:

-> The End to End testing the system from Rewuirement base to delivery base is working peroperly or not.

-> The purpose of end-to-end tests is make ensure that the right information is passed between various system components and systems.

-> End-to-end testing involves ensuring that that integrated components of an application function as expected. The entire application is tested in a real-world scenario such as communicating with the database, network, hardware and other applications.

For example, a simplified end-to-end testing of an email application might involve logging in to the application, getting into the inbox, opening and closing the mail box, composing, forwarding or replying to email, checking in the sent items and logging out of the application.

Type of System Testing :

1.Fuctionality testing'
2.Non-functionality testing

Difference between Batch Processing and Interactive Processing

Batch Processing - If we want to run bulk of mainframe files more than one time

The huge volume set of input file running bulk with out user interation. Those input data are saved in Mainframe files and executed by Batch Process.

The jobs are setup made up without any ineractions, The operators specify the below inforamtion correctly in batch job

1) collection of input files
2) And specify the ouput files where we get the output.

While the user submit (SUB) the job, the system Automatically takes the bulk of input data from files and prcessed and saved those result in output file without any manual interaction.

Example :

he way credit card companies process billing is a very good example of batch processing. The credit card owner does not receive a bill for each separate credit card purchase. Instead the bill is created using a batch process and the data are stored there. At the end of the month or the billing cycle, the data are collected as a batch process and the card holder gets the bill for the whole months transaction.

Interactive Processing - Here they ask the input files and ouput files information each an everytime. 

Here user give the input and submit the job and get the ouput files. we get the ouput immediately. Then user specify the some other input and submit the job and get the ouput. So the  input-output-input cycle continue still we get the expected result with user interactions.

This is called Interactive Processing

Example:

An example of an interactive processing system is where an insurance company can make changes to a customer's household insurance, e.g. while the customer is on the phone. The insurance clerk simply calls up details of the customer's policy on the screen, and types in any required changes which immediately update the customer's records. A report of the change would be automatically generated and a copy sent to the customer.