Skip to main content

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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...
66 comments
Read more

Endurance Testing with Example, Meaning and Definition

Endurance Testing is a type of Performance Testing which is usually used to determine how much a system can sustain the continuous expected load. During the period of Endurance Testing memory utilization is always monitored to detect any potential leaks. In short we can say that judging/studying the memory leak of a server under the period of stability is known as Endurance Testing . Due to its judgment and study on memory leak that is the reason why Endurance Testing is also known by the name Soak Testing . As you know in Endurance Testing memory utilization is monitored so it very important for us to know about memory leak means what it is all about. When memory allocated to objects are not being freed by the system/application than definitely the memory leak occurs. Endurance Testing Example – Real Time Below is given the real time example of Endurance Testing and hope after seen these real time example your knowledge on Endurance Testing should definitely b...
Post a Comment
Read more

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...
31 comments
Read more