Skip to content

Latest commit

 

History

History
46 lines (45 loc) · 4.83 KB

File metadata and controls

46 lines (45 loc) · 4.83 KB

Introduction To Automated Testing

What is automated testing

It is a Software Testing Technique to test and compare software's actual outcome with the expected outcome, which can be achieved by writing test scripts or using any automation testing tool.

Why do we need automated testing

  • Preventing bugs, reducing development costs and improving performance
  • Coorperate with Manual Testing to achieve best performance

Advantages Compared to Manual Testing

  • The biggest pro of automation testing over manual testing is that it allows you to do more testing in less time. It increases productivity and expands how much you can test.
  • Automated testing reduces repetitive manual tasks during the testing phase
  • Automated testing can actually deliver better results because of its ability for increased test coverage.
  • More content in this link

Disadvantages of automated testing

  • Less flexible to handle complex and nuanced test scenarios
  • Can't and shouldn't be used to test cases that occur infrequently, are high risk, or are subject to change

There are many automated testing methods like unit testing, functional testing, smoke testing, regression testing and integration testing. We will look more into unit testing and integration testing in this article.

Unit Testing:

  • Unit testing contains tests that focus on testing on individual components or functions in "isolation" at the most foundational level.
  • Used to show if a single function or component of the application will produce the desired outputs or perform the way as expected.
  • Benefits: safe, clear, efficient and reliable.
  • Mostly first type of automated testing done for an application. And usually before integration testing.
  • Consult this link for more information

Integration Testing:

  • Usually takes place after Unit Testing.
  • Software modules are integrated logically and tested as a group within integration testing.
  • Because different modules could be developed by different people, its purpose is to expose defects in the interaction between these software modules when they are integrated.
  • Integration Testing focuses mainly on the interfaces & flow of data/information between the modules. Its priority is to be given for the integrating "links".
  • Consult this link for more information

More Article And Video Links

Watch the video

Watch the video

Watch the video

Watch the video

Watch the video

Watch the video

Watch the video

Watch the video