Difference between Manual Testing and Automation Testing

Manual Testing	Automation Testing
1. Manual Testing is a process which is done manually.	1. Automation Testing is a process which is done by the help of automated tools.
2. All the famous phases of STLC like test planning, test deployment, result analysis, test execution, bug tracking and reporting tools are obviously comes under the category of Manual Testing and done successfully by human efforts.	2. In Automation Testing all the popular phases of STLC are done by various open sources and purchased tools like Selenium, J meter, QTP, Load Runner, Win Runner and so on.
3. Manual Testing is a start of Testing, without this testing we can’t start Automation Testing.	3. Automation Testing is a continuous part of Manual Testing.
4. In Manual Testing testers are allowed to do Random Testing to find the Bugs.	4. In Automation Testing we always test through Running Scripts.
5. In Manual Testing we find more bugs than automation by Error Guessing.	5. In Automation Testing we test the repetitive functionalities of the application.
6. It takes lot of time.	6. It takes less time.
7. Manual Testing would be run sequentially.	7. Automation Testing is done on different machines at same time.
8. Regression Testing process is tough in Manual Testing	8. Regression Testing process is easy in Automation Testing by Tools.
9. It is not expensive.	9. It is expensive.
10. More testers are required in Manual Testing because in this testing test cases need to be executed manually.	10. Few testers are required in Automation Testing because in this testing test cases need to be executed by using Automation Tools.
11. It gives low accuracy result.	12. It gives high accuracy result.
12. It is considered as low quality.	12. It is considered as high quality.
13. In this Testing we cannot do batch testing.	13. In this Testing we can do multiple types of batch testing.
14. It is considered as less reliable.	14. It is considered as more reliable.
15. No need of programming in Manual Testing.	15. Need of programming is must in Automation Testing.
16. It is done without interaction of any Tool.	16. It is always done using tools.

Difference between Use Case and Test Case in Table

	Use Case	Test Case
1	Use Case is prepared by business analyst.	Test case is prepared by test engineer and in small companies sometimes it is prepared by quality analyst too.
2	Based on test cases use cases cannot be prepared means it is not derived from test cases.	Based on use cases test cases can be prepared means it is derived from use cases.
3	Use case describes step by step instructions means how to use functionality.	Test case verifies the functionality means it is as per the instructions mentioned in use case or not.
4	Use case cannot be executed means it is only designed.	We design the test cases and later execute them.
5	It is derived from the BRS (Business requirement specification.)	It is derived from the use case.
6	It is a pictorial representation of client requirements or you can say customer requirements.	It is not represented diagrammatically it is only documented in excel sheet and in big companies it is also documented in some test case management tools.
7	It is a document which always describes the flow of events of an application.	It is a document which always contains an action, event and an expected result of particular feature of an application.
8	Use Cases can be written by BA (business analyst.) on the basis of client requirements or customer requirements.	Test cases are written by test engineer or quality analyst on the basis of use case document.
9	It always tells us about the story of how people interact with a software system to achieve a goal.	It verifies the goal to see it is as per the instructions of use case or not.

Exact Difference between Unit Testing and Integration Testing

		Unit Testing	Integration Testing
	1	It do not occurs after and before of anything.	It occurs after Unit Testing and before System Testing.
	2	It is not abbreviated by any name.	It is abbreviated as “I&T” that is why sometimes also called Integration and Testing.
	3	It is not further divided into any.	It is further divided into Top-down Integration, Bottom-Up Integration and so on.
	4	It may not catch integration errors, or other system-wide issues because unit testing only tests the functionality of the units themselves.	Integration testing uncovers an error that arises when modules are integrated to build the overall system.
	5	The goal of unit testing is to isolate each part of the program and show that the individual parts are correct.	The goal of Integration Testing is to combined modules in the application and tested as a group to see that they are working fine.
	6	It does not follow anything.	It follows unit testing and precedes system testing.
	7	It obviously starts from the module specification.	It obviously starts from the interface specification.
	8	Unit testing always tests the visibility of code in details.	Integration testing always tests the visibility of the integration structure.
	9	It requires complex scaffolding means frame.	It requires some scaffolding means frame.
	10	It definitely pays attention to the behavior of single modules.	It definitely pays attention to the integration among modules.
11		It is only the kind of White Box Testing.	It is both the kind of Black Box and White Box Testing.

Exact Difference between GUI Testing and Usability Testing

GUI Testing	Usability testing
1. In GUI Testing tester tests the application front end design to see whether its meets the client requirements or not.	1. In Usability Testing tester tests that whether the application is user friendly or not by checking how easily user can access the application.
2. In GUI Testing we check whether the design and layout of application as per the standards and client requirements or not.	2. In Usability Testing we check whether the design and layout of application is easy to use or not means it is user friendly or not.
3. GUI Testing is more concerned with look and feel of the application means how people react and feel after look in to the application so its testing is done accordingly that.	3. Usability Testing is more concerned with easiness and user friendliness of the application means how people react after using the application means application is easy to use or not so it’s testing is done accordingly that.
4. In GUI Testing tester tests the appearance of the software.	4. In Usability Testing tester tests the easiness to use the software.
5. GUI Testing is done to ensure it meets the design specifications like links, colors, fonts, font sizes, fields etc are displayed as specified in SRS or as specified in client requirements.	5. Usability Testing is done to ensure that the GUI is well designed and easy to use like links and buttons are easily clickable and leaving any of the mandatory field blank gives the proper message that please enter the xyz in mandatory field.
6. GUI Testing is done by keeping in mind the look and feel of application means how application looks.	6. Usability Testing is done by keeping the end user in mind.
7. It stands for Graphical User Interface. It is nothing its only confirm the design specifications with the application.	7. It is done to ensure that the GUI is well designed and easy to use.
8. It is done on different platforms to verify the Look and Feel Testing. (Look and Feel of the application).	8. It is done to verify how much the application is user friendly to an end user.
9. In GUI Testing, tester test whether the front end design of the system is meeting with project standards or not.	9. In Usability Testing, tester tests whether the control flow of the system is convenient for end user or not.
10. In this testing we just test the appearance of the application.	10. In this testing we test the interaction of functionality with the user is effective or not.
11. Example: Example includes colors, fonts, font sizes, buttons, links, icons, placement of data labels and fields etc. are displayed as specified or not.	11. Example: Example includes firstly displayed all mandatory fields, cursor positioning for enter the data into the right field, tab button should work easily etc.
12. In GUI Testing we only focus on the interface of the application.	12. Quality of product is depending on Usability Testing.
13. In this testing we test only the front end of the application.	13. In this Testing we test the overall working of application according to a non-technical user’s point of view.