When to be system automated
2
When to be system automated? Big(long term) and Critical projects. System(Projects) that require testing the same functions frequently. Requirement not changing frequently Accessing the application for more load and performance with many users Study software with respect to manual testing Time availability What system should be automated? Unit Testing : Unit testing is in many projects a task which is performed occasionally by programmers during development of system. (Regression Testing) Anything that we need to do repeatedly, if we are repeating something a more than about 5 times and the elements in it are stable. We are automating web applications at the moment and automating the regression tests for end to end functionality has saved a lot of time. Stress testing is great to automate. It is often needed right at the end of a release cycle so saving a few hours has a big benefit. Functional Testing: Functional testing is the testing of how system or application functions, or, in other words, its relation to the users and especially to the rest of the system. Functional testing is implemented by a team of testers and Business analyst, independent of the developers. Another way of saying that functional testing is "the customer test" What should not be automated? Well usability testing is mostly done by clients so there is no need to automate that. It’s difficult to automate any tests with qualities or subjective results. The more binary the result the easier something is to automate. The functionality testing of the early releases of new products is difficult to automate effectively because the applications change so quickly. When moving across in to a new technology I like to tests manually as we learn about the technology and the application. This produces results quickly and makes it easier to automate later on if needed.
description
Day 1-Introduction & QTP Test Process Day 2-Key Elements of QTP , Recording & Running Day 3- Object Repository Day 4 Object Identification Configuration Day 5 -Descriptive Programming Day 6-Checkpoints & Output Values Day 7-Parameterization , Synchronization Day 8- Actions , Environment Variables Day 9 Transaction Points , Adding Comments Day 10- Debugging Tests , Batch Testing Day 11- Recovery Scenarios , Quality Center Day 12 –Quality Center Day 13 –Introduction , Variables Day 14 –Comments , Constants , Operators Day 15 –Flow Control (Conditional Statements) Day 16 –Flow Control (Looping through the Code ) Day 17 –User Defined Functions Day 18–Built-In Functions Day 19 –File System Operations Day 20 –Excel Object Model Day 21–Database Object Model Day 22 –Regular Expressions Day 23–Error Handling Day 24 –GUI Scripting Day 25 –Web Scripting Day 26 –Introduction , Basic Framework Day 27 –Data Driven Framework Day 28 –Keyword Driven Framework Day 29 –Hybrid Framework
Transcript of When to be system automated
When to be system automated?
Big(long term) and Critical projects. System(Projects) that require testing the same functions frequently. Requirement not changing frequently Accessing the application for more load and performance with many users Study software with respect to manual testing Time availability
What system should be automated?
Unit Testing: Unit testing is in many projects a task which is performed occasionally by programmers during development of system.
(Regression Testing)
Anything that we need to do repeatedly, if we are repeating something a more than about 5 times and the elements in it are stable. We are automating web applications at the moment and automating the regression tests for end to end functionality has saved a lot of time.
Stress testing is great to automate. It is often needed right at the end of a release cycle so saving a few hours has a big benefit.
Functional Testing:Functional testing is the testing of how system or application functions, or, in other words, its relation to the users and especially to the rest of the system. Functional testing is implemented by a team of testers and Business analyst, independent of the developers. Another way of saying that functional testing is "the customer test"
What should not be automated?Well usability testing is mostly done by clients so there is no need to automate that. It’s difficult to automate any tests with qualities or subjective results. The more binary the result the easier something is to automate.
The functionality testing of the early releases of new products is difficult to automate effectively because the applications change so quickly.
When moving across in to a new technology I like to tests manually as we learn about the technology and the application. This produces results quickly and makes it easier to automate later on if needed.
How to system Automated?
Identifying functional areas within a software for automation
Identifying of appropriate tool for Test Automation Prepare Test Scripts Prepare of Test Suits Execution of scripts Create result reports Recognize any potential bugs or performance issues
Some of Software Testing Tools
HP Quick Test Professional Selenium
IBM Rational Functional Tester
SilkTest
TestComplete
Testing Anywhere
WinRunner
LaodRunner
Visual Studio Test Professional
WATIR
