Home  >  Expertise  >  Quality Assurance  >  Automated Testing
Automated Testing

Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions. Commonly, test automation involves automating a manual process already in place that uses a formalized testing process.  Automated testing helps the QA team to speed up the testing process for long-term projects.

The advantages of using Automation in testing are:

  • Faster Execution
  • Reliable
  • Repeatable
  • Comprehensive
  • Reusable

Automated testing process is expensive but it can be made cost-effective:

  • Choose a test tool that best fits the testing requirements of your organization or company.
  • Realize that it does not make sense to automate some tests. Overly complex tests are often more trouble than they are worth to automate. Concentrate on automating the majority of your tests, which are probably straightforward. Leave the overly complex tests for manual testing.
  • Only automate tests that are going to be repeated. One-time tests are not worth automating.
  • Avoid using “Record/Playback” as a method of automating testing. This method is fraught with problems, and is the most costly (time consuming) of all methods over the long term. The record/playback feature of the test tool is useful for determining how the tool is trying to process or interact with this application under test, and can give you some ideas about how to develop your test scripts, but beyond that, its usefulness ends quickly.
  • Adopt a data-driven automated testing methodology. This allows you to develop automated test scripts that are more “generic,” requiring only that the input and expected results be updated.
TESTING METHODOLOGIES
 

1. Functional Testing

Testing of all features and functions of a system [software, hardware, etc.] to ensure requirements and specifications are met.

2. Smoke Testing

Smoke testing is normal health check up to a build of an application before taking it to testing in depth. It is scripted- either using a written set of tests or an automated test.

3. Regression Testing

Regression testing is done on adding or modifying functionality of application through by rerunning existing relevant tests to determine whether the changes break anything that worked prior to the change and by writing new tests where necessary.   Adequate coverage without wasting time should be a primary consideration when conducting regression tests.

4. Performance Testing

 Performance testing is used to simulate a heavy load on a server, network, or object to test its strength or to analyze overall performance under different load types or under heavy concurrent load.

 
QA PROCESS
  •     V-Model for QA testing process
  •     Two testing phases: Planning and Execution

 PLANNING

  • Create HLCM to extract the manual test cases that need to be automated.
  • Generate Automation scripts based on HLCM. HLCM covers all web screens, buttons, and links that will cover under the follow of application. HLCM covers all test cases for various functionalities on the basis of each web screen, button or link selected.
  • Review Scripts through QA based examination of the Test Plan using the most appropriate method (i.e. formal inspection, walkthrough, peer review etc.)
  • For regression testing, scripts are just modified as per new functionality added.

EXECUTION

  • Execute Scripts on different test browsers. Different browsers used are IE6, IE7 and Firefox.
  • Log and test bugs in case of deviation of application from BRS in bug tracking tools. And finally closes them to make application ready for release.
  • Daily Tracking of Bugs, Change Requests and Test Scripts Execution is done to track the testing progress.

TOOLS

 Test Management Tools:

Test Director: to execute automated scripts of QTP
VSTS: to execute automated scripts of TestComplete

 Functional Testing Tools:

TestComplete, QTP, Winrunner

 Open Source Tools:

OpenSTA: to test performance
JMeter: to load test functional behavior and measure performance

DbyDx In the News
Vinaora Nivo SliderVinaora Nivo Slider
© Copyrights SKAN DbyDX Software Pvt. Ltd. 2017. All Rights Reserved.
Disclaimer | Privacy Policy