Some key benefits of using this framework are listed below:

Moderate technical competency required for the use – The framework in itself is very easy to use and does not require special automation skills unless there is a need for modifications or enhancements

Re-usability– The framework with its existing set of scripts and keywords can be used for automating any set of applications

Low maintenance cost – The only cost involved is when there is any change in the framework or requires a new Keyword

Rapid Automation Suite Development – The framework is ready to use and has minimal efforts required in terms of setting up the automation bed. Thus one can quickly come up with an automation solution for any application that has been identified for automation

Custom Reporting – Apart from the report generated by the test automation tool the framework supports custom reporting based on the parameters defined during the requirements stage of automation. This helps the QA analysts to quickly know the behavior of the application after an execution which is easy to read and understand from the application perspective

Tool independent – The framework can be used with various Test Automation tools, giving the freedom to the organization to choose any tool

Customization - The framework can be customized for application specific needs

Test Automation is adopted in many projects with the objective of reduction in testing cycle times, reduction in efforts and resources and in turn attaining more focus on testing the critical and complex areas of application that need to be tested manually.

 Many people believe that test automation is record and play back, but it is not true. Test Automation Framework will be best approach to automate an application. Before I explain about Automation Framework, I want to illustrate few disadvantages of automation without Framework.

It worked when I recorded it!
This is a common problem across most of the Test Automation projects where the “Capture and Replay” method is used for automation. Scripts work perfectly when they are created while recording the test cases and stop working after a while with the same objects or after a few minor modifications to the application

 Skills required by the testers to use the tool
Since the scripts have to be changed frequently with the changes in the application, the testers necessarily have to know the scripting language and a level competency is required to support such changes

Reusability
Without frameworks it becomes difficult to apply any automation methodologies like keywords or functional decomposition. This reduces the chances of having any reusable scripts and leads to bulky scripts making it difficult to manage. This increases the script maintainability

Standardization
Automation engineers working on different automation projects tend to have their own set of the design, structuring, coding standards of scripts.

SendTo = "abc@abc.com
Attachment = "C:\abc.txt"
 Set ol=CreateObject("Outlook.Application")
     Set Mail=ol.CreateItem(0)
     Mail.to = SendTo
     Mail.Subject="Test Results "
     Mail.Body=" Test Results"
   '  If (Attachment <> "") Then
       Mail.Attachments.Add(Attachment)
    ' End If
     Mail.Send
     'ol.Quit
     Set Mail = Nothing
     Set ol = Nothing

         

MyTime = Now()
TimeStamp =  Year(MyTime) & Month(MyTime) &  Day(MyTime) &  "_" & Hour(MyTime) &  Minute(MyTime) & Second(MyTime)
MsgBox TimeStamp