Skip to main content

When Is Automation Necessary?

Since not all projects require automation, you need to consider the efficiency of manual tests and see how much coverage the project entails. For instance, if the project is a small one, automation testing should not be a requirement since you may not have the money or resources needed to complete the project and hire an automation specialist. However, for larger projects, bringing in an automation expert is a necessary step in testing, even if it may be a little costly. Using simple automated scripts instead of manual tests with certain projects that use websites could be both cost and time effective. This would ultimately reduce the time spent on testing as a whole.

  1. Can reduce the time and cost of software testing
  2. Can improve software quality
  3. Can enhance manual testing efforts via increased testing coverage and replaces the manually mundane and labor intensive tasks
  4. Can achieve what manual testing can hardly accomplish, such as memory leak detection under specific conditions; concurrency testing and performance testing, and more.

Comments

Popular posts from this blog

What is the difference between Selenium and QTP?

Feature QTP(UFT) Selenium Language Support VB Script Java, C#, Ruby, Python, Perl, PHP Windows (Non-browser) based Application support Yes No Browser support Google Chrome (uptill ver 23) Internet Explorer , Firefox ( ver 21) Google Chrome , Internet Explorer , Firefox , Opera , HtmlUnit, Safari Environment Support Only Windows Windows , Linux , Solaris OS X , iOS, Android, Others (If brower & JVM or Javascript support exists) Mobile (Phones & Tablets) Support Different commercial product i.e. HP UFT Mobile (formerly known as MobileCloud for QTP) Android , iPhone & iPad , Blackberry , Headless WebKit Framework Easily integrated with HP Quality Center or HP ALM (separate commercial products) Selenium + Eclipse + Maven / ANT + Jenkins...

How to create package inside a project?

What Is a Package? A package is a namespace that organizes a set of related classes and interfaces. Conceptually you can think of packages as being similar to different folders on your computer. You might keep HTML pages in one folder, images in another, and scripts or applications in yet another. Because software written in the Java programming language can be composed of hundreds or thousands of individual classes, it makes sense to keep things organized by placing related classes and interfaces into packages. -> Right click on the Project (Make sure you should right click on project, because you are creating package inside the project). -> Go to New. -> Click on Package. -> In New Java Package window, enter package name in Name text box. -> Now click on Finish . -> Now you can see the package inside the project at Project Explorer area. Now your package is ready.